Network Manager having issues with two concurrent connections

[irishdunn]

Running ubuntu 8.10 on both boxes, here is what I need:

Diagram: http://img29.picoodle.com/img/img29/3/8/13/f_Testm_519a06a.jpg

Here is what happens:

Wireless works fine out of the box with 8.10, card (rt61, wmp54G v4.1), as does wired, (onboard, Abit IP35 Pro)

However here is the hitch, I can either use wireless, or wired... never both. If I connect the wired interfaces then my wireless is still connected but i cannot get to the internet, only can ping things on the local network.

If I dont connect the lan then I can use my wireless and get access to the internet.

I need both, as you can tell from above, lan for the fileserver and wireless so I can get to the outside world.

RAID MACHINE:
storrgie@FILEBEAST:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:8d:bb:d5:be
inet addr:192.168.7.4 Bcast:192.168.7.255 Mask:255.255.255.0
inet6 addr: fe80::250:8dff:febb:d5be/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:71289 errors:0 dropped:0 overruns:0 frame:0
TX packets:67496 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5447835 (5.4 MB) TX bytes:4990075 (4.9 MB)
Interrupt:23 Base address:0x6000

eth1 Link encap:Ethernet HWaddr 00:50:8d:bb:d5:bf
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)
Interrupt:22 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:365 errors:0 dropped:0 overruns:0 frame:0
TX packets:365 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:24916 (24.9 KB) TX bytes:24916 (24.9 KB)

wlan0 Link encap:Ethernet HWaddr 00:1c:10:6e:9f:21
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21c:10ff:fe6e:9f21/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11737 errors:0 dropped:0 overruns:0 frame:0
TX packets:5272 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12665536 (12.6 MB) TX bytes:521323 (521.3 KB)

wmaster0 Link encap:UNSPEC HWaddr 00-1C-10-6E-9F-21-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:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

storrgie@FILEBEAST:~$ cat /etc/resolv.conf
# Generated by NetworkManager
domain domain_not_set.invalid
search domain_not_set.invalid
nameserver 192.168.1.1
nameserver 192.168.1.1
nameserver 192.168.0.1
storrgie@FILEBEAST:~$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.7.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0

MAIN Machine:
storrgie@BEAST:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:18:38:04:1e:66
inet addr:192.168.7.2 Bcast:192.168.7.255 Mask:255.255.255.0
inet6 addr: fe80::218:38ff:fe04:1e66/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6273 errors:0 dropped:0 overruns:0 frame:0
TX packets:6705 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:466802 (466.8 KB) TX bytes:511168 (511.1 KB)
Interrupt:23

eth1 Link encap:Ethernet HWaddr 00:18:38:04:1e:67
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)
Interrupt:22 Base address:0x2000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:216 errors:0 dropped:0 overruns:0 frame:0
TX packets:216 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13328 (13.3 KB) TX bytes:13328 (13.3 KB)

wlan0 Link encap:Ethernet HWaddr 00:21:29:6a:05:71
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::221:29ff:fe6a:571/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2282 errors:0 dropped:0 overruns:0 frame:0
TX packets:1871 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1935590 (1.9 MB) TX bytes:327145 (327.1 KB)

wmaster0 Link encap:UNSPEC HWaddr 00-21-29-6A-05-71-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:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

storrgie@BEAST:~$ cat /etc/resolv.conf
# Generated by NetworkManager
domain domain_not_set.invalid
search domain_not_set.invalid
nameserver 192.168.1.1
nameserver 192.168.0.1
storrgie@BEAST:~$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.7.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0

Given these two outputs here is how I got it to work:

I have to boot both of the machines up, let them both connect to each network (LAN and Wireless) AT THIS POINT IN TIME I still do not have internet... at this point in time I check my routing tables, there is no entry for 0.0.0.0 .... I also check my /etc/resolv.conf and there is no entries.

SO HERE IS THE FIX:
I then unplug my crossover cable, for just a second. and network manager writes to my /etc/resolv.conf the values you see above, also there is an entry for 0.0.0.0 in my routing table.

What step am I missing that will help me to not have to crawl around on the floor every time I restart these damn machines?!

[Stephan Trebels (ncubede)]

Just to know what it'll attempt to do:
what are your /etc/network/interfaces, /etc/NetworkManager/nm-system-settings.conf, nm-tool output, and relevant syslog for both machines?

[irishdunn (irishdunn)]

I was contacted through the NM mailing list and told to set the gateway of the lan cards to 0.0.0.0

this enables exactly the functionality that I like, and I am glad to say that this is not a bug now, just a confusion on how to configure the interfaces.

[irishdunn (irishdunn)]

This is not a big, it was an invalid filing. By setting one of the interfaces gateway to 0.0.0.0 I have accomplished the goals required by my network.