I have several Linksys routers and I use one as DHCP server running Tomato and the rest as access points running stock firmware and DDWRT spread around my home office. To control bandwidth on certain APs I set a certain port on main router into a separate bridge and VLAN. Screenshot for reference.

VLAN setup bridge setup

Everything works fine and I can control bandwidth on anything connected on port 3. For some reason though I cannot access the web GUI of APs connected to port 3. I tried setting the AP's IP to 192.168.1.xxx and also 192.168.2.xxx per my bridge IP and none of them worked. Is there something wrong in my setting?

Thank you

  • 1
    Can you ping them? – qasdfdsaq Nov 9 '15 at 11:27
  • 1
    I cannot. Thank you – rabbid Nov 9 '15 at 12:25
  • 1
    That suggests a basic connectivity problem, probably with your AP's IP address settings. – qasdfdsaq Nov 9 '15 at 12:26
  • 1
    Perhaps. Can you give ideas? As I have said I tried setting the AP settings to 192.168.1.xx and 192.168.2.xx with no luck. Bear in mind if I link Port 3 to br0 then everything works fine. – rabbid Nov 9 '15 at 15:54
  • 2
    If clients connected to the APs on VLAN3 can access the internet, it's probably a firewall setting on your APs. – qasdfdsaq Nov 9 '15 at 16:22
up vote 1 down vote accepted

Take a look at this link

Try the following:

With the routes configured it is now safe to disable NAT on Router2 and Router3 by switching their Operating Mode from 'Gateway' to 'Router' on the Setup->Advanced Routing page.

You said you are "setting the AP's IP to 192.168.1.xxx and also 192.168.2.xxx". Make sure you have netmask set to 255.255.255.0 for them as well.

Also, make sure you are setting the LAN IP of the APs.

After you confirmed the above, if you login to your Tomato, you should be able to ping your APs. But if you ping from your PC connected to Tomato and it does not work, it is likely that the APs do not know the route back because your IP's address is an IP from a different LAN of the AP. Your APs need to have a default route correspond to 192.168.1.1 and 192.168.2.1.

  • Thanks for you your suggestion. I tried and can ping to 192.168.2.1 from within Tomato. What does that tell me? Thank you @some-user – rabbid Nov 23 '15 at 14:05
  • You should always be able to ping 192.168.2.1 from Tomato because I believe from your post that it is one of the IP addresses of your Tomato. You should verify if you can ping your AP IP (192.168.2.xxx in your post) from your Tomato. – some user Nov 23 '15 at 21:51
  • Very confused now. I swear yesterday I can ping to my AP to its IP which is 192.168.2.3. Today I fiddled and changed it to 192.168.1.3 because of an article I read and now I can't ping it from within Tomato. What is the correct IP I should use? .2.x or .1.x? Should I connect the ethernet cable to LAN or WAN? I have a suspicion that when I'm using .1.x I should use LAN, while on .2.x I should use WAN, although that's just a guess. Thank you – rabbid Nov 24 '15 at 2:07
  • You cannot just change your IP prefix without changing the LAN it is connected to. From your screen capture, you have 3 networks - LAN (br0), WAN and LAN1 (br1). If your AP is connected to LAN (br0) and you changed its IP from 192.168.1.3 to 192.168.2.3, you won't be able to reach it again. You can however, remove the link to LAN1 (br1) and move LAN (br0) to LAN1 port and change the AP's IP back that way. – some user Nov 24 '15 at 7:12
  • That is correct, I am able to link Port 3 back to bro0 and connect to it again. I'm shooting blindly here, and instead of doing that perhaps you can suggest to me best settings to try instead? Thank you – rabbid Nov 24 '15 at 7:30

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.