Ubuntu
dhcp3 package

Network is unreachable

Bug #284807 reported by Major Andras
This bug report is a duplicate of:  Bug #274069: error send_packet:message too long. Edit Remove
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
dhcp3 (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Description: Ubuntu intrepid (development branch)
Release: 8.10 (Updated 2008.10.17)

I have a SMC Barricade SOHO router at home. If I want to use Intrepid at home, the wired network not working anymore.
After boot, the network-manager-applet is online and dhcp get works succesfully.
But if I want to ping my router, the ping said network is unreachable.

andras@andras-laptop:~$ ping 192.168.2.1
connect: Network is unreachable

In nm-tool's output, the eth0 is configured properly, but the ifconfig said eth0 isn't configured.

andras@andras-laptop:~$ nm-tool

NetworkManager Tool

State: connected

- Device: eth0 ----------------------------------------------------------------
  Type: Wired
  Driver: tg3
  State: connected
  Default: yes
  HW Address: 00:1A:4B:58:FA:C9

  Capabilities:
    Supported: yes
    Carrier Detect: yes
    Speed: 100 Mb/s

  Wired Settings

  IPv4 Settings:
    Address: 192.168.2.18
    Prefix: 24 (255.255.255.0)
    Gateway: 192.168.2.1

    DNS: 192.168.2.1

- Device: wlan0 ----------------------------------------------------------------
  Type: 802.11 WiFi
  Driver: iwl3945
  State: disconnected
  Default: no
  HW Address: 00:1B:77:50:1B:25

  Capabilities:
    Supported: yes

  Wireless Settings
    WEP Encryption: yes
    WPA Encryption: yes
    WPA2 Encryption: yes

  Wireless Access Points
    FOLEY: Infra, 00:1E:2A:06:0D:48, Freq 2462 MHz, Rate 54 Mb/s, Strength 45 WPA
    TP-LINK: Infra, 00:14:78:8E:90:04, Freq 2437 MHz, Rate 54 Mb/s, Strength 35 WPA
    SpeedTouchA2FA1F:Infra, 00:14:7F:8C:CF:CB, Freq 2412 MHz, Rate 54 Mb/s, Strength 28 WPA WPA2
    Tamaslak: Infra, 00:19:5B:B2:27:5F, Freq 2437 MHz, Rate 54 Mb/s, Strength 38 WEP
    STULLER: Infra, 00:12:17:C7:C6:C3, Freq 2462 MHz, Rate 54 Mb/s, Strength 46 WEP

andras@andras-laptop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1a:4b:58:fa:c9
          UP BROADCAST RUNNING MULTICAST MTU:64 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:18

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:242 errors:0 dropped:0 overruns:0 frame:0
          TX packets:242 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:15140 (15.1 KB) TX bytes:15140 (15.1 KB)

wlan0 Link encap:Ethernet HWaddr 00:1b:77:50:1b:25
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC HWaddr 00-1B-77-50-1B-25-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns

If I restart Network-Manager manually no dhcp anytime (see network.log)
In syslog there is an error message:

dhclient: send_packet: Message too long

See original description
Revision history for this message
Major Andras (majorandras) wrote :
Revision history for this message
Major Andras (majorandras) wrote :
Revision history for this message
Major Andras (majorandras) wrote :
Revision history for this message
Major Andras (majorandras) wrote :
description: updated
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report. This is probably a dup of bug 274069 . affecting to dhcp3.

Can you try one of the following:
- remove the option interface-mtu in /etc/dhcp3/dhclient.conf
- sudo ifconfig eth0 mtu 1000
- check if your router is in full duplex mode.

Thanks.

Revision history for this message
Major Andras (majorandras) wrote :

You are right !

If I remove interface-mtu from /etc/dhcp3/dhclient.conf, the network is working properly.

I found a line in my syslog file:

nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.

My router is an old one and I gues it can't handle interface-mtu parameter.

What will be the final solutions for this issue ?

Thank You for help.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I'll talk with the dev about this issue, the mtu parameter has been reenabled in Intrepid in dhcp3-client 3.1.1-1ubuntu1, and there are some reports about network problems since then

For your reference, here is the relevant part of the changelog:
" - debian/dhclient.conf: Get the interface-mtu parameter again. Previous
      Ubuntu versions ignored it because of broken old DHCP servers which hand
      out the wrong value. (LP#61989) However, this breaks correct and
      deliberately sent non-default values, which is a bigger pain. If this is
      still an issue, a better fix is to discard unplausibly low values only.
"

I'm marking this report duplicates of bug 274069 .

Thanks for your help to make Ubuntu better !

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

BTW, the workaround for now is to remove the mtu parameter or set it to a low value (something around 1000 or so)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.