Author Topic: WBMR-300-HP doesn't route between internal wired networks  (Read 2352 times)

bassplayerchris

  • Calf
  • *
  • Posts: 2
WBMR-300-HP doesn't route between internal wired networks
« on: December 27, 2012, 06:27:30 AM »

Hi -

 

I have the WBMR-300 set up like so:

 

Internet <----> WBMR <-------> 192.168.1.X network

                                       <--------> 192.168.1.2 [router] 192.168.2.1 <---> 192.168.2.X network

 

So two networks with an additional router separating the two.  Anyone on either network can access the internet - but though all filtering is off  hosts on the 192.168.1.X network cannot access hosts on the 192.168.2.X network and vice versa.

 

The [router]'s route table is set with itself as the default route for the 192.168.2.X network.  The WBMR has a route for the 192.168.2.X network that points to the 192.168.1.2 address of the router.  Evidently packets are routing properly in general as hosts can access external addresses.  It looks like the WBMR is filtering out packets between the two networks though.


JakeTheSnake3p0

  • Calf
  • *
  • Posts: 8
Re: WBMR-300-HP doesn't route between internal wired networks
« Reply #1 on: December 27, 2012, 02:52:41 PM »

Is that setup on purpose? Do you really want two separate networks? If not, just put the 2nd router in bridge mode or at least turn off it's dhcp server. If you DO want that, look to see if there's an option to set an additional LAN IP address on the router so that it's on the other subnet.


bassplayerchris

  • Calf
  • *
  • Posts: 2
Re: WBMR-300-HP doesn't route between internal wired networks
« Reply #2 on: December 27, 2012, 05:58:45 PM »
Perhaps I didn't explain myself well enough - I have two separate networks, the WBMR acts as the gateway between the external and internal worlds (as it has a modem on it). The other router *is* on the other subnet - it's also on the 192.168.1.X subnet as it has to route between the two networks. WBMRs LAN settings has the 192.168.1.2 address set up as the gateway for the 192.168.2.X network. It's evidently working to an extent - it just seems that whatever the WBMR sets up as it's iptables set up isn't allowing connections (probably just the SYN packet) between the two networks.