Hey All,
So here's a brief run-down of the situation:
We have two buildings where I work, they are a block apart and are currently bridged by 802.11a wireless routers. (Shudder-slow) Being the good (speed hungry) IT person that I am I bought 2 Linksys WRT54GL routers to replace the old D-Links there now. (I have flashed the routers with DDWRT btw) I need the information between buildings to flow seemlessly. After doing some research I figured that WDS would probably be the best way to go. I setup both routers and they seem to be working just fine. I am plugged into R1 and it can ping, wirelessly, R2. However, when I plug into R2 to see about getting an IP address (DHCP forwarding is on) it won't assign my computer an IP. But R1 can still ping R2, and even access the setup page for R2 wirelessly.
Any thoughts as to why it goes one way but not the other? (And don't try to tell me this is a great security feature...
)
So here's a brief run-down of the situation:
We have two buildings where I work, they are a block apart and are currently bridged by 802.11a wireless routers. (Shudder-slow) Being the good (speed hungry) IT person that I am I bought 2 Linksys WRT54GL routers to replace the old D-Links there now. (I have flashed the routers with DDWRT btw) I need the information between buildings to flow seemlessly. After doing some research I figured that WDS would probably be the best way to go. I setup both routers and they seem to be working just fine. I am plugged into R1 and it can ping, wirelessly, R2. However, when I plug into R2 to see about getting an IP address (DHCP forwarding is on) it won't assign my computer an IP. But R1 can still ping R2, and even access the setup page for R2 wirelessly.
Any thoughts as to why it goes one way but not the other? (And don't try to tell me this is a great security feature...
