Open GoogleCodeExporter opened 9 years ago
I have the same problems with a Netgear wpn824v3 worked perfectly with my old
router
but doesn't work with my new router. I downgraded to .75 and no longer have an
issue,
so it is a software issue. I just don't know if it is a problem with cios or
Mplayer.
Original comment by JWhittak...@gmail.com
on 3 Jan 2010 at 10:19
I have looked a bit more into this, but even after downgrade, it still gives
the same
issues...
So figured a packet sniffer would give me some clues and interestingly I found
that
Mplayer crashed right after my router sent a DHCP NAK broadcast.. Googling this
message got me to the following: "A NAK is a negative acknowledgment from DHCP.
This
can be done when an address renewal is refused by the DHCP server, or a
duplicate IP
address exists when requesting an offered IP address, among other reasons."
Of course, I figured it might be something related to my Wii internet settings.
So I
removed my settings to ensure nothing from my old router remained. Then, when I
setup
my new connection, the problem still remains (with DHCP NAK messages right
before
failure) :-(...
Any thoughts?
Original comment by marinusb...@gmail.com
on 15 Jan 2010 at 3:01
uhmm, The DHCP protocol utilizes UDP ports 67 and 68 and we are using only tcp
connections, so it's a problem with ios network stuff. I have the same problem
if I use
a belkin repetear, seems that wii doesn't handle dchp nak packet in the rigth
way and
cut the network connection, because I need to restart mplayer to get network
working
again. Maybe I can try to detect a disconnection and reconnect but probably the
film
stop before I can reconnect again, what I've done is save restore point on
error to
continue watching the film at the same point.
Original comment by rodries@gmail.com
on 15 Jan 2010 at 6:56
Yeah, I was afraid of that, though it remains weird to me that there is a
difference
between routers. Nevertheless, I worked out a workaround by just entering a
static
IP-address within Wii internet settings (which just avoids DHCP communication).
No
crashes this time.. All in all not the most neat solution, but at least my
problem is
resolved..
Thanks for the help
Original comment by marinusb...@gmail.com
on 15 Jan 2010 at 7:59
Original issue reported on code.google.com by
marinusb...@gmail.com
on 1 Jan 2010 at 11:53