Create PPTP connection for different IP range to main LAN

Hi,
I am trying to create a PPTP connection into the Routerboard which gives me a different LAN address to the primary Lan BUT does connect me to the same interface as the primary LAN… sorry i’m not really sure how to explain it very well.

I appreciate this is an odd request so will explain why.

We use allot of UBNT equipment and always have a Routerboard as our gateway. Each network has its own primary LAN, e.g. 10.0.0.1/24 ( gateway would be 10.0.0.1 ). Unfortunately sometimes the UBNT kit will reset and we have to send out an engineer to connect to the network with a laptop, set there the Ethernet port to 192.168.1.x and connect to the default UBNT IP address of 192.168.1.20.. although the fix is quick and straight forward some of the networks we support can be a 2 or 3 hour drive so its a very inefficient way of working.

What we are trying to do is create a PPTP connection into the RB that gives us a 192.168.1.50 ( or anything as long as its not .10 or .20 ) IP address that then allows us to ping devices on the eth2 interface which is our primary LAN and connects to all the UBNT kit. That way we can remote in, connect to the reset UBNT device and reconfigure it.

I presume this is possible with with the little knowledge i have of RB i’m struggling to create the route that connect the PPTP connection to the primary LAN but with a different IP range.

I have a PPTP connection that gives me an IP address of 192.168.1.50 from a pool i have created but i then get a subnet of 255.255.255.255 so i’m unable to do anything.

Any pointers would be appreciated.

Thanks

Hi,

What you want to do is Access to UBNT default network from your PPTP client besides internet.
There is a “trick” that maybe help you.
When you have the same subnet in more than one interface (PPTP interface and ether interface), you have a layer 2 conflict so you should help interface to decide what should do. So you need to change interface Ethernet as proxy-arp in order to ask for arp request in the other interfaces.

Of course Ethernet interface has to have a the IP address 192.168.1.1

Thanks for the input @gustavomam

The fix was to add the subnet being used by the UBNT equipment ( 192.168.1.1/24 ) as a second LAN Address to the same ether interface as the primary LAN.

A PPTP session to the RB provides an IP address on the same 192.168.1.x network via a dedicated pool

That allowed us to SSH via a telnet session from the RB to the UBNT device and then configure the device via command line in the SSH session to have the the correct IP information and then open it in a browser as we do normally to restore the last working backup.

Works very well and will stop needless trips out of the office for what ends up to be a 30 min job.

Thanks.. Pigsfoot

Your welcome!

Making a better community in this forum we will be “routing the world” with MikroTik jejeje

The best way to learn more things in MikroTik is helping another colleagues :smiley: