Having a bit of trouble trying to log into the client radios on our wireless network behind the MT router.
What I have is the MT router set up on 10.10.0.253 on ether1 to get out to the rest of the network, clients are on a DHCP network behind the router using a 10.10.10.0/24 addressing scheme on ether2. The radios are set to static IP’s of 10.10.10.6 to 10.10.10.50. The DHCP pool is from 10.10.10.51 to 10.10.10.254.
What I want to do is be able to access the client radios from any computer on the network which has an address of 10.10.0.0/16 or 10.168.0.0/16. Even if I could just access the AP radio of 10.10.10.2 that would be enough to get me started on figuring out how to set up the NAT for the rest of the radio IP’s.
I’ve tried various NAT configurations already without much luck. Maybe I’m just missing something simple.
Well, I’m still learning this stuff as I go along. But NAT just seemed to make the most sense at the time. Is there another method I might want to persue? VPN/IPSec?
Well, keeping it simple, you could just use routing. Clients on the 10.10.0.0 network have a route set to the 10.10.10.0 network using gateway 10.10.0.253.
Would I use the /ip routes menu or would this be done in /routing RIP/OSPF/BGP? I am not familiar with how to set up a route like this. The only routes I have in my MT box right now were created automatically by MT when I set the box up.
I read that article for the IPv4 stuff and some of it seemed to make sense. Everything except the part about the Next Hop component. Nowhere in the MT router setup do I see where to specify the Next Hop.
I’ve been banging my head on the desk all week trying to figure this out with little progress. It is very important to our ISP to get this working so we can determine if a client is having a problem with their radio without having to take a long drive. These radios are only accessible from HTTP on port 80 if that makes any difference.
The “next hop” is configured in the ip routing table (if talking about static routing, not OSPF or the like).
(It’s the “gateway” in MikroTik terminology.)
