SXT P2P Config Issue

RouterOS Wireless Networking
1

I’ve followed the WISP guide to link two SXT 5HnD up with great results (just on a tested link on the floor for the moment).

The SXT our end is on the 192.168.100.x range.

During the test’s ive bridged it according to WISP article and setup default route on the remote SXT and can traceroute etc. However where the remote SXT is going it’s on 192.168.2.x range, how can i best configure this so it has its own network internally still but can still have it’s default gateway pointing to an address out on the internal 192.168.100.x range. (I was hoping to set client pc’s to use the remote SXT address as the default gateway given out by dhcp).

So to clarify the config:

SXT our end - 192.168.100.253
SXT remote end - 192.168.2.253
Default gateway for internet 192.168.100.254

I need the SXT remote end to also be able to connect to any machine on 192.168.100.x segment should it need to.

Thanks,
Chris

2

Think i may have answered my own question, havent tested it with a client yet but i did the following:

  • Changed the ip address currently assigned to ether1 to bridge1
  • Added the internal lan address on ether1

Is this the best way?

Thanks,
Chirs

3

This works great after creating a masquarde rule on the Remote SXT. However got a slight issue that i cant seem to resolve. on the main link SXT dhcp is on the network dishing out 192.168.100.x addresses on the remote end i’ve also got dhcp being dished out on 192.168.2.x. From the looks of it because its bridged dhcp is coming across from 192.168.100.x - how can i stop this?

Thanks,
Chris

4

Think you are mixing up the need for bridging vs routing

If the remote end is on a completely different subnet then no need to have a bridge
Stick the subnet on the ether and serve dhcp from there
Then on the wireless interface make it a member of the main subnet
Then run masquerade/nat between the two subnets, or add static routes on the other SXT

Nick.

5

Cheers nick (notice how i asked here first rather than annoy you!). Disable the bridge both ends but then the static route setup on 0.0.0.0/0 to default gw ip on 192.168.100.254 doesnt work says unreachable - not sure what you mean make it a member of the main subnet…

Thanks,
Chris

6

Thanks Nick that helped me solve the issue with a clean head this morning, simple when you know how!