Bridge/Router... Which one works?

[Ninjahedge]

Hey guys,

After trying to get the Linksys E2000 to play nice and act as a bridge unit and router, I just plain gave up.

According to IT at work, this is a No-Go as far as the E2000 is concerned.

Now, aside from getting an actual "bridge" unit, are there any wireless routers than WILL work as a bridge? The important part is just that I really do not want to have to have 2 pieces of equipment hooked up to do the same thing one should be able to do (plugs, config, wiring...)


Any input would be appreciated.

 

[kornphlake]

I believe any router that can run dd-wrt will function as a wireless bridge, there may be others as well.

Not sure I understand the part about not wanting 2 pieces of equipment, a bridge converts a wireless signal into a wired ethernet connection, you've got to have 2 pieces of equipment for this to work, a router or wireless access point and a bridge. In the case of using a router configured as a bridge you'll still be using 2 routers. Maybe a little better description of the application would help hone in the best answer to your question.

 

[Ninjahedge]

What I mean is, I do not want two pieces at the receiving end. I used to have that before with a b/g access point wired to a router.

Now, I simply want to use a wireless router and program it for the net, then simply hook up the equipment to its wired ports, done.

But as soon as I hook up and assign it an IP, I can't get any further. It is inaccessible and I have to hard-reset and start over again. After several hours and several cycles (including following instructions found on some other sites), trying with both ddWRT and factory default and nada.

So if there is a way to do it with the E2000, I am all ears, but if not, I need to know what wireless router can be easily config'd to act as a bridge point and router (all in one).

 

[VirtualLarry]

I need to know what wireless router can be easily config'd to act as a bridge point and router (all in one).

That doesn't make sense. Do you want a wireless bridge, or a router? They are not the same thing. A wireless bridge, ALSO requires a router, to bridge to, wirelessly. So you do need two devices, a router AND a bridge. It doesn't make sense to only have a bridge, it needs a router to connect to. Yes, you can have just a router, without a bridge.

A router, flashed with DD-WRT firmware, can be configured to act as EITHER a bridge OR a router, if need be. But if it is configured as a bridge, then you need an ADDITIONAL router to bridge to.

The Internet (WAN) connection, would connect to the Internet/WAN port on the router. Any local LAN PCs would be connected to the ethernet ports. You can also connect laptops through wireless. You would also configure the bridge such that the bridge's WAN is effectively the wireless router. The bridge's WAN ethernet port would be empty. You would connect the wired devices that need the bridge into the bridge's ethernet ports, and the bridge would communicate wirelessly to the router, to connect to the internet, and the rest of the LAN.

DD-WRT supports the E2000:
http://dd-wrt.com/wiki/index.php/Linksys_E2000

 

[kornphlake]

Again, I'm not sure what you're after, a bridge, a router, or a router configured as a bridge (which becomes a bridge not a router and a bridge.)

What are you trying to connect the bridge to (neighbor's wifi, dsl modem with wireless AP, existing wireless router, etc?) What devices do you wish to connect to the bridge, are they to connect using an ethernet cable or wireless b/g/n?

 

[Ninjahedge]

I am after turning on the E2000 in my living room, have it connect to an existing 802.11n signal and be able to have equipment plugged into it.

That's it.

If you can get 2-way communication between a wireless device and one of the hard wired ports on a wireless router, why can't you connect:

Internet (or network server) -> E3000 -> E2000 -> HTPC.

 

[smitbret]

I am after turning on the E2000 in my living room, have it connect to an existing 802.11n signal and be able to have equipment plugged into it.

That's it.

If you can get 2-way communication between a wireless device and one of the hard wired ports on a wireless router, why can't you connect:

Internet (or network server) -> E3000 -> E2000 -> HTPC.

I'm thinking that English is not your first language, is it?

I though I had you figured out until you threw the "If you can get 2-way communication between a wireless device and one of the hard wired ports on a wireless router...."

You can't get 2-way communication between a wireless device and a hard-wired port. Why would a wireless device communicate with a hardwired port? They are two separate pieces of a router.

Anyway, from what I can glean, you would like to use your E2000 as a wirless bridge, right? You need to flash your E2000 with a DD-WRT firmware:

http://www.dd-wrt.com/wiki/index.php/Linksys_E2000

Then you can put the E2000 into bridge mode and hook up your wired devices to it. Initially, you'll probably need to be hard-wired to configure it. Once it is configured and can see the wireless signal, it should be as simple as plugging your equipment into the back. It will work as a bridge/switch from there.

 

[ccbadd]

I think you just need to install DD_WRT and configure it as a repeater bridge.

 

[Ninjahedge]

I'm thinking that English is not your first language, is it?

It is, thanks for the condescending attitude.

I though I had you figured out until you threw the "If you can get 2-way communication between a wireless device and one of the hard wired ports on a wireless router...."

You can't get 2-way communication between a wireless device and a hard-wired port. Why would a wireless device communicate with a hardwired port? They are two separate pieces of a router.

Really? You mean that I can't get to the laptop in the other room when I am sitting at my hard-wired desktop and vice versa? I will have to go home and tell my computer to stop doing that then.

Anyway, from what I can glean, you would like to use your E2000 as a wirless bridge, right? You need to flash your E2000 with a DD-WRT firmware:

http://www.dd-wrt.com/wiki/index.php/Linksys_E2000

Then you can put the E2000 into bridge mode and hook up your wired devices to it. Initially, you'll probably need to be hard-wired to configure it. Once it is configured and can see the wireless signal, it should be as simple as plugging your equipment into the back. It will work as a bridge/switch from there.

Already did that (read other posts) and followed the instructions to the letter. It lets me see the connection, and everything seems to be just fine, until I change the IP to match the base E3000 address (192.168.2.###) then all communication goes bye-bye.

I have heard from other people that the E2000 has problems with this. I am just trying to confirm (or deny) this and see if anyone has any other link that is not easily Google-able.

 

[Ninjahedge]

I think you just need to install DD_WRT and configure it as a repeater bridge.

I did exactly that, and then I hit a wall that requires a hard reset of the E2000.

Unless they released a NEW ddWRT for the E2000 that I was not aware of (in the past ~6 months).....

 

[kornphlake]

Just buy a bridge if what you need is a bridge, then you don't have to mess around with firmware. Problem solved.

If that's not good enough, buy one of the routers that comes from the factory with dd-wrt and set it to be a bridge, it "should" work, but might require some additional configuration.

 

[kornphlake]

Already did that (read other posts) and followed the instructions to the letter. It lets me see the connection, and everything seems to be just fine, until I change the IP to match the base E3000 address (192.168.2.###) then all communication goes bye-bye.

Why would you set two devices to have the same IP? An IP can only be used by one device on a network. You should be setting the ip of the bridge (e2000) to some static IP number outside the range of IPs served by DHCP from the router.

Have you tried finding different instructions, it sounds like you might be following instructions that are flawed.

 

[JackMDS]

If you want to use only the wire ports of the Router/Bridge, then configure it as a Client Bridge.

http://www.dd-wrt.com/wiki/index.php/Client_Bridged

Otherwise, to use both the Wireless and the wire capacity of the Bridge use this configuration.

http://www.dd-wrt.com/wiki/index.php/WDS_Linked_router_network

If you follow the instruction on the whatever you choose of the pages above and it does not work, get yourself a new Router.

There is a list of Wireless Routers on DD-WRT Wiki site, http://www.dd-wrt.com/wiki/index.php/Main_Page

My favorite is this one, http://www.newegg.com/Product/Produc...82E16833162031

 

[Ninjahedge]

Why would you set two devices to have the same IP? An IP can only be used by one device on a network. You should be setting the ip of the bridge (e2000) to some static IP number outside the range of IPs served by DHCP from the router.

Miscommunication.

I mean I change it to be on the same sub (loop?) as the E3000.

The current setup is that the 192.168.1.1 is the main Verizon router. That is then linked up to the E3000. The E3000 does the g/n wireless and is also hooked up to my NAS and main machine.

The E3000 starts off in the 192.168.2.### range, and so does everything else in the network. I made sure there was no conflicts before I tried giving the E2000 a 192.168.2.### address that was different than all the others. I have tried several, and also tried when all other machines were not active just to see what was happening.

Nothing.

Have you tried finding different instructions, it sounds like you might be following instructions that are flawed.

I only found two sets, and they were pretty similar. I was wondering if anyone else had a suggested link or had a similar problem that they were able to work around.

Any suggestion would be welcomed! (Whether it be hardware or config). I just do not want to have to either get ANOTHER piece of equipment to be the n bridge AND blow the dust off the old 54 upstairs..... (HDTV does not stream well on g...)

 

[Ninjahedge]

Jack, thanks. I will give it a look when I get home.

 

[smitbret]

It is, thanks for the condescending attitude.



Really? You mean that I can't get to the laptop in the other room when I am sitting at my hard-wired desktop and vice versa? I will have to go home and tell my computer to stop doing that then.

Well, I originally hadn't meant it to be condescending. We field people who are unable to structure a thought into simple English all the time around here. Most of the time, it's because English isn't their natural language. Glad to know that's not the case here and that it's just because you struggle with simple literacy.

Wireless communication requires a device to send a signal wirelessly and a device to receive the signal, also wirelessly. No wireless device communicates with a hard-wired port. The router translates the between the two.

 

[VirtualLarry]

Perhaps the problem is when the E2000 is configured as a client bridge, as 192.168.2.x, that the computer you are using to configure it, loses it's IP address because you left it on DHCP, and the wireless link isn't up yet, so it hasn't allowed your local PC to pull an IP from the primary router.

I've never used Client Bridge mode, I've only used Client mode, and WDS mode, on Broadcom hardware with DD-WRT.

I set someone up with DD-WRT and Client mode (one PC connected via ethernet), and it was pretty trivial.

First, have to set configuring PC's IP address, to 192.168.1.8, connect to DD-WRT router at 192.168.1.1. Then change DD-WRT router's LAN IP to 192.168.2.1.

At that point, I wondered why I could no longer access the router. So I hard-reset it, thinking it hung.

It was my mistake, I forgot to change the configuring PC's IP address as well to 192.168.2.8, to match the subnet of the router after I had changed it.

The reason for changing the LAN IP subnet, is because when in Client mode, the router acts as a client, and (I think) NATs between the two subnets, and the primary router was already on 192.168.1.1. So therefore we had to change the DD-WRT router to 192.168.2.1.

After that was done, we set the wireless config on the router, to Client mode, N-only, filled in the SSID of the primary router, and saved and applied, then went to the wireless security tab and selected the security type and filled in the password.

The DD-WRT router then grabbed a WAN IP from the primary router, and we were in business.

See? Simple.

 

[Ninjahedge]

Well, I originally hadn't meant it to be condescending. We field people who are unable to structure a thought into simple English all the time around here. Most of the time, it's because English isn't their natural language. Glad to know that's not the case here and that it's just because you struggle with simple literacy.

F-u too.

Wireless communication requires a device to send a signal wirelessly and a device to receive the signal, also wirelessly. No wireless device communicates with a hard-wired port. The router translates the between the two.

Are you splitting hairs? If so, please spare me, you are being no use whatsoever and seem to delight in insulting another poster. Piss off.

 

[Ninjahedge]

VL, I will have to read that a few times to get the gist!

Pardon my inexperience with networking (beyond the basics)...

 

[alyarb]

Use DHCP forwarding on the bridge but disable NAT/SPI and other stuff that will default to being on.

 

[kornphlake]

Sounds like you've got some fubared configuration. You need one DHCP server, presumably in the router your ISP supplies, everything else should be used as a switch, access point or bridge.

I'd keep everything on the same subnet, leave the verizon as 192.168.1.1, make the E3000 192.168.1.2 and the E2000 should be 192.168.1.3. The Verizon router should be the DHCP server for the entire network, set it to serve a range of 192.168.1.100-192.168.1.130 or whatever you feel is appropriate. Hardwire the verizon router to the E3000 using the LAN port on the E3000 so it will act as a switch/access point rather than a router, there's no need to double NAT. The E2000 and E3000 need to have the DHCP servers disabled, it's difficult to connect to a device that isn't serving IPs, you'll have to follow a specific sequence of setting up the connections between the devices before disabling the DHCP server, it will probably take some trial and error.

 

[VirtualLarry]

That's one way to do it, I suppose. I use a verizon FIOS router, and I have two of my own routers. The verizon router is 192.168.1.1, and my two routers are 192.168.2.1 and 192.168.2.2. I have my primary router in the DMZ of the verizon router, so every unsolicited incoming connection goes to my primary router, where it can be handled by port-forwarding or uPNP.

 

[Ninjahedge]

I don't remember exactly why I bumped it to the "2"s, but it may be to avoid any "automatic" assignment that might conflict with ones that are set up for things like the Verizon Channel boxes.

Each MFR has their own thing, and i was just looking for a way to connect without having to reconfig everything....

List:
2 x Slimline music servers
1 x Linksys Power Line (router?)
1 x WDTV HDTV player
1 x laptop
1 x Desktop
1 x HTPC
1 x "IP Phone" device
1 x Verizon box (which I should have connected to get info...)
1 x XB360

Now getting all these ducks in a row is hard enough. Trying to get them to dance together for an untrained Net Novice? Well, maybe I am only a lackey, I think I got enough "exp" to get me to the next level by now!

Thanks for the help guys. From what you are saying, I SHOULD be able to set this puppy up, it just keeps pissing on the carpet.

 

[mammador]

There are routers that can act as both a bridge and a router. Why do you need a bridge anyhow? Bridges are simply less advanced switches. Are you using 1980s networking tech or something? lol..

 

[smitbret]

There are routers that can act as both a bridge and a router. Why do you need a bridge anyhow? Bridges are simply less advanced switches. Are you using 1980s networking tech or something? lol..

Easier to setup. Some of us don't wanna have to mess with DD-WRT, Tomato or other stuff.