*** This bug is a duplicate of bug 61989 ***
** This bug has been marked a duplicate of bug 61989
[Edgy dhclient regression] error: Message too long
--
Network unreachable with Edgy
https://launchpad.net/bugs/58927
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
I confirm the fact that I have two DHCP computers on the same router. The one
has the bug while the orther has not.
However the proposed solution works.
Thanks you. Without your help, I would still be on Dapper ;)
Laurent
--
Network unreachable with Edgy
https://launchpad.net/bugs/58927
Right, we have the bug confirmed by multiple people, and we have a
solution confirmed by multiple people, we should people to get a patch
committed for this now!
--
[EMAIL PROTECTED]
SDF Public Access UNIX System - http://sdf.lonestar.org
--
Network unreachable with Edgy
https://launchpad.ne
It is definitely a router dependent problem which happens when DHCP asks
for interface-mtu and the router reports some too low value (which is 64
in all ifconfig outputs attached to this report). A simple way to check
if this is the problem, and not something else, is to check what
"ifconfig" says
I think it is not a router problem. On the same router at home, Edgy works on
my computer while it doesn't works on my laptop.
But the same laptop that has the bug at home has no problem at university.
It should be a combination of the router and the internal network card.
--
Network unrea
I got this exact same problem with another machine after upgrading to
edgy, when connecting via the same modem. The same solution works. I'm
guessing from Jarmo's comments that it's the router, not the machine,
that matters, so I won't post any details about this machine.
--
Network unreachable w
I can confirm this bug with the Edgy beta release. I upgraded a Dapper
box to Edgy on the day of the beta release, and lost wired Internet
connectivity. The fix of manually editing dhclient.conf worked for me.
Some info:
Before applying the dhclient.conf fix, if I set the network card to
connect
** Changed in: Ubuntu
Sourcepackagename: None => dhcp3
--
Network unreachable with Edgy
https://launchpad.net/bugs/58927
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Manually changing mtu works for me too.
--
Network unreachable with Edgy
https://launchpad.net/bugs/58927
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
A bit of additional data about the "interface mtu" request and
debian/ubuntu dhcp3 packages:
The setting was disabled during hoary (from changelog):
dhcp3 (3.0.1-1ubuntu4) hoary; urgency=low
* Revert changes to debian/dhclient.conf, apparently at least some DHCP
servers supply broken interfac
I have the same problem now with edgy (upgraded from dapper around
knot3), in dapper this used to work fine. On my home network dhcp fails
with "Message too long".
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
send_packet: Message too long
I tried to look at the traffic with wireshar
eth0 is fine to get IP while booted from a live CD I have (5.04), and
piece of info, during "sudo dhclient eth0" I can't see "sent packet
count" increased with Gnome Network Monitor so seems no packets are sent
for dhcp, because of the "send_packet: Message too long" message ? Only
ping packets wer
Confirm this problem with Edgy knot3 upgraded from Dapper. Can't get an
IP for eth0, message is same as "send_packet: Message too long".
$lspci | grep Ethernet
00:12.0 Ethernet controller: National Semiconductor Corporation DP83815
(MacPhyter) Ethernet Controller
$lsmod | grep nat*
natsemi 30112
13 matches
Mail list logo
