1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Strange gateway/router access problem

Discussion in 'Tomato Firmware' started by tievolu, Mar 5, 2013.

  1. tievolu

    tievolu Network Guru Member

    I have two Asus RT-N16's running Shibby's Tomato v107, configured like this:

    RT-N16 (Gateway) - Access point + WDS (192.168.1.1)
    |
    |~~WDS link
    |
    RT-N16 (Bridge/Router) - Access point + WDS (192.168.1.2)

    The idea is that the APs running on each router cover the two halves of my house, as one router is not sufficient due to a very thick wall in the middle (used to be an external wall). The two routers almost have a line-of-sight connection, with just two thin doors between them.

    This works very well, with just one odd problem. For some reason, the gateway router cannot "see" the bridge/router, in that it cannot ping it or connect to it it any way (e.g. telnet or ssh). This means that I cannot remotely administer the bridge from the WAN, despite setting up a port forward from an external port to port 443 on the bridge/router. The logs on the gateway indicate that the connection is accepted and forwarded properly, but as far as I can tell the bridge/router never sees any connection attempt coming in.

    Strangely, it's only the gateway that can't see the bridge/router - wired and wireless clients on the LAN can see and access the web interface on both the gateway and the bridge/router.

    Does anyone know what's going on here?
     
  2. tievolu

    tievolu Network Guru Member

    Doh! Entirely my fault. Just noticed that I had a static IP set up for the bridge on the gateway, but it was mapped to the bridge's wired MAC address. I switched this to the bridge's wireless MAC and everything's working now.

    Move along. Nothing to see here... :rolleyes:
     
    philess likes this.

Share This Page