Results 1 to 6 of 6

Thread: [SOLVED] Static Local, DHCP Wireless (Woes)

  1. #1
    Join Date
    Aug 2008
    Beans
    37

    Thumbs down [SOLVED] Static Local, DHCP Wireless (Woes)

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



    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.

    help!

  2. #2
    Join Date
    Nov 2007
    Location
    eastern NC
    Beans
    657
    Distro
    Ubuntu 6.10 Edgy

    Re: Static Local, DHCP Wireless (Woes)

    I just finished a comparable setup, without the gigabit crossover. That is a hardwire connection?

    Simultaneous ethernet and wireless was done by this person:
    http://ubuntuforums.org/showthread.php?t=775216
    Last edited by buccaneere; November 14th, 2008 at 04:46 AM.
    If you wanna' help, great. But explain as you go. Otherwise, you're just giving away fish, and not the important stuff - pole, bait, net, etc...

    Still a beginnerd, but not absolute...

  3. #3
    Join Date
    Aug 2008
    Beans
    37

    Re: Static Local, DHCP Wireless (Woes)

    Thanks for the reply, I quickly glanced at his post and will look at it later tonight. I will also post interface configurations on both boxes over the weekend.

    If you could explain exactly how you set up your situation I would appreciate it.

    The crossover cables are hardwire.

    I want to set up this type of scheme:

    FileComputer:
    ETH0:
    ip: 10.0.0.2
    netmask: 255.0.0.0
    gateway: 10.0.0.1 (Not needed?)

    ETH1:
    ip: 10.0.0.3
    netmask: 255.0.0.0
    gateway: 10.0.0.1 (Not needed?)

    Wlan: (INTERNET)
    DHCP

    MainComputer:
    ETH0:
    ip: 10.0.0.4
    netmask: 255.0.0.0
    gateway: 10.0.0.1 (Not needed?)

    ETH1:
    ip: 10.0.0.5
    netmask: 255.0.0.0
    gateway: 10.0.0.1 (Not needed?)

    Wlan: (INTERNET)
    DHCP

    The wlan right now is a AP that is using wep. but that is my main source for an outside line.

  4. #4
    Join Date
    Jan 2007
    Beans
    5,549

    Re: Static Local, DHCP Wireless (Woes)

    i say , you put it on a different ip setup .. like say you get 10.0.0.x ip from your AP.. then between the Main box and RAID box .. setup ip manually as 10.0.1.x ( not 10.0.0.x) .. and make the Main box as gateway and RAID box as client.. its like a mini network.. so when you want to access your MAIN box or RAID box you type in the 10.0.1.x ip.. and the internet would work as usual using the 10.0.0.x ip

  5. #5
    Join Date
    Aug 2008
    Beans
    37

    Re: Static Local, DHCP Wireless (Woes)

    Alright here is an update, I still require much help:

    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?!

  6. #6
    Join Date
    Aug 2008
    Beans
    37

    Re: Static Local, DHCP Wireless (Woes)

    SOLVED:

    Set the interfaces that are not meant for internet to have gateways of 0.0.0.0

    Network Manager will work properly with this setup!

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •