• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

2 Subnets Via WDS? Is It Possible?

twodaend

Member
I was wondering if it would be possible for me to connect 2 subnets via WDS. Currently I have 2 WRT54G v3's connected via WDS and all devices on the 192.168.1.x subnet. I want one WRT54G to be 192.168.2.x and all devices behind it (PS2, Media PC) to have 192.168.2.x. Is it possible to connect the 2 WRT54G's via WDS with different subnets (192.168.1.x & 192.168.2.x), or do I have to run a cable to do this?

So far I can only get the 2 subnets to work when I run a cable from a LAN port on WRT1 to WAN port on WRT2. The routers will normally not be close enough to run a cable, this was just to test. I added the advance routing 192.168.2.0, 255.255.255.0, 192.168.1.2 and everything works so long as the cable is in place, but I want to do it via WDS.

I used these two instruction to try and make it work. The WDS instructions work so long as everything is on the same subnet. I tried to combine those instruction with the second set, but am not successful connecting 2 subnets via WDS only with a cable.

WDS Instruction

Bridge Instructions
 
I was told that I could change the subnet mask to 255.255.254.0, but if I change the subnet to 255.255.254.0, is this now a Class B or still a Class C or does it matter. I thought you could only extend a class, not take away from a class.

Ex.
Normal Class C
255.255.255.0

Extended Class C
255.255.255.248

Normal Class B
255.255.0.0

Extended Class B
255.255.254.0
 
first of all, what is the end goal? Adding IP to make finding devices easier?

If you use a 192.168.X.X network with subnet mask of 255.255.0.0 then 192.168.0.1-192.168.255.254 are all valid hosts for the same subnet. Thus 192.168.1.X is in the same network as 192.168.2.X,. If you run these with a class C mask (255.255.255.0) then you are on different subnets, and would require a router to route traffic between them. That is why connecting to thw WAN port of one worked, as you were then "Routing" traffic.
 
Back
Top