Ugh! I thought I knew what I was doing.
Aug. 10th, 2005 11:11 amI recently went to add a second segment to my network. basicly this is how it works right now -
Satellite bidirectional modem (land connections are better but that's a different post) with built in NAT and DHCP (oh how I wish I could turn off both of them and let one of my other routers do that stuff).
Connected to the satellite modem is a DLink 802.11g router (I forgot the model and I'm at work). Router is set to IP address of 192.168.0.10 (modem is set to 192.168.0.1), has dhcp turned off and the sat modem is plugged into port 1 instead of WAN because we aren't interested in the NAT abilities of the router, we just want the wireless bridge and switching abilities for the wired section of the network. All that works fine.both wired and wireless clients can get dhcp addresses and connect to the internet.
Now comes the part I thought I knew what I was doing and I'm not... We recently picked up a USR 802.11g (model 8054) router. The idea is that our network upstairs (which isn't connected to anything) will use the USR to connect to the network downstairs wirelessly (running cables just isn't a viable option). Except I can't get the USR to talk wirelessly to the DLINK.
The USR IP address is set to 192.168.0.254, and I've tried the following things - setting the channels to same number, setting the channels to different numbers, setting the SSIDs to the same name and setting the SSIDs to different names. Regardless the USR doesn't do anything except sometimes interfere with the working segment depending on configuration. I guess I need to do more reading.
Satellite bidirectional modem (land connections are better but that's a different post) with built in NAT and DHCP (oh how I wish I could turn off both of them and let one of my other routers do that stuff).
Connected to the satellite modem is a DLink 802.11g router (I forgot the model and I'm at work). Router is set to IP address of 192.168.0.10 (modem is set to 192.168.0.1), has dhcp turned off and the sat modem is plugged into port 1 instead of WAN because we aren't interested in the NAT abilities of the router, we just want the wireless bridge and switching abilities for the wired section of the network. All that works fine.both wired and wireless clients can get dhcp addresses and connect to the internet.
Now comes the part I thought I knew what I was doing and I'm not... We recently picked up a USR 802.11g (model 8054) router. The idea is that our network upstairs (which isn't connected to anything) will use the USR to connect to the network downstairs wirelessly (running cables just isn't a viable option). Except I can't get the USR to talk wirelessly to the DLINK.
The USR IP address is set to 192.168.0.254, and I've tried the following things - setting the channels to same number, setting the channels to different numbers, setting the SSIDs to the same name and setting the SSIDs to different names. Regardless the USR doesn't do anything except sometimes interfere with the working segment depending on configuration. I guess I need to do more reading.
no subject
Date: 2005-08-10 05:37 pm (UTC)no subject
Date: 2005-08-10 05:39 pm (UTC)So either need to get a bridging device, or find a way to hack the USR.
I know one of the homebrew firmwares for my wrt54g from linksys provides wireless bridging. You have to enter the SSID and Mac Address of sister AP's in order for it to connect, on a seperate wireless bridging page in the config.
no subject
Date: 2005-08-10 05:44 pm (UTC)no subject
Date: 2005-08-10 06:06 pm (UTC)no subject
Date: 2005-08-10 06:18 pm (UTC)Even want a bash shell on a router? (:
-----
Honestly, I think your best bet is taking the USR back while you can and getting a wireless bridge.
no subject
Date: 2005-08-10 06:23 pm (UTC)no subject
Date: 2005-08-10 09:40 pm (UTC)no subject
Date: 2005-08-10 09:52 pm (UTC)no subject
Date: 2005-08-11 03:38 am (UTC)no subject
Date: 2005-08-11 03:44 am (UTC)it's running a linux of sorts with a 175MHz MIPS processor.
I haven't seen any firmwares for dlink stuff that's not pre packaged 'from dlink' though.
you can also get an opensource firmware for the wrtg54 series that lets you do seamless mesh networking over wireless.
no subject
Date: 2005-08-12 03:48 am (UTC)