NetworkManager in Intrepid manages wrong network connection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Binary package hint: network-manager
This is my /etc/network/
auto lo
iface lo inet loopback
auto usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
up echo 1 > /proc/sys/
up iptables -P FORWARD ACCEPT &
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
The auto usb0 line and everything below is to allow my FreeRunner to
access the Internet whilst it is plugged into the desktop running
Intrepid. This worked fine with Hardy, which correctly assumed the unlisted eth0 should be primarily used via dhcp.
If I comment out auto usb0 and everything below, I can access the rest
of the network, but then, of course, my FreeRunner no longer has
Internet access.
I worked around this by
sudo apt-get remove network-manager
and then adding
auto eth0
iface eth0 inet dhcp
to my /etc/network/
does your usb0 device show up in hal with a "net.80203" capability ?