desktop-packages team mailing list archive

[Bryan Quigley <bryan.quigley@xxxxxxxxxxxxx>]

This bug was fixed upstream and likely fixed in current Ubuntu releases.

** Changed in: network-manager (Ubuntu)
       Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/250654

Title:
  Do not default to a /24 when DHCP doesn't specify netmask

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
   affects ubuntu/network-manager

  Just had a bizarre network at heathrow:
  Retrieved the following IP4 configuration from the DHCP daemon:
  address 10.231.33.227
  netmask 255.255.255.0
  broadcast 10.231.33.255
  gateway 10.231.32.1
  nameserver 192.168.22.22
  nameserver 192.168.22.23
  domain name 'hatbl.btopenzone.com'

  Now, I'm not exactly sure what windows does, but it clearly works.

  In this case, the 'ip route add default via 10.231.32.1 dev wlan0'
  command fails (no such process) because there is no route to
  10.231.32/24

  Adding a manual route thusly:
  ip route add 10.231.32.1 dev wlan0
  allows the default route to be added (and the network then works fine -
  see for instance me filing this bug report).

  I suggest a) checking for insane DHCP parameters, and b) issuing a
  direct route as above when discovered - it's almost certain to work.

  -Rob
  -- 
  GPG key available at: <http://www.robertcollins.net/keys.txt>.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/250654/+subscriptions