Community discussions

MikroTik App
 
Cameron Earnshaw
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 90
Joined: Sun May 30, 2004 6:46 pm
Contact:

Routing issue has me stumped

Tue Feb 22, 2005 7:21 am

I had two separate networks feeding into the same T1. Because we have now installed a wireless link that allows us to connect them on the LAN side I decided to put them all onto the same subnet. When we switched the wireless link on I turned the DHCP server off on the second network, and had planned that as the leases expired the clients on the second network would get their IP address, gateway, DNS settings etc from the first network's router. Within 72 hours everyone should be on the #1 subnet. Once the two networks were linked I released and renewed my own IP address to try it out. Sure enough, I got the new IP address from network #1 as planned. However, although I was now on the right subnet, and could ping the gateway and even log into net #1's Mikrotik with Winbox, I could not get past the local interface onto the public side of the router. My computer showed up in the ARP list but it just wouldn't route properly. The router from #2 subnet is still running but with its DHCP tuned off. Could this have something to do with why it won't route? The only other device on the old network is a wireless access point. Could there be a bridge table in it that needs to be cleared out? The clients who were on net #1 continued working normally but any of the net #2 clients who obtained a new IP address would not route properly. I have disconnected the wireless link until I can figure this out. Any ideas would be greatly appreciated.

Cameron
 
wifiradio
just joined
Posts: 23
Joined: Sat Feb 12, 2005 3:29 pm
Location: Canada

Fri Feb 25, 2005 2:32 am

the second network connot access the public side because you either need a src-nat to the interface supporting network #2 or a route in the ISPs router supporting the second interface ... I am assuming the #1 network interface is src-nat to the public side ...