I have a wAPR-2nD (behind NAT as it is customary for 3G) that I would like to manage remotely. To do this I set up a CHR on a VM that the wAPR-2nD can connect to:
I set up an SSTP connection from the wAPR-2nD to the CHR and then an EoIP tunnel using the SSTP endpoint IPs.
They appear as RoMON neighbors and as normal neighbors, here from the point of view of the CHR:
They can RoMON ping each other:
But when I try to connect to the wAPR’s RoMON address using the CHR as RoMON agent, I only get:
Firewall setting? MAC server setting?
EoiP-tunnel is member of what “Interface list” ?
And heh … , I use a similar setup. Use CHR as IP default gateway for PC, SSTP is used with masquerade, but No EoIP, nor RoMON (MAC based access ?) but Winbox, with normal IP based access.
The CHR used is mAP Lite (mobile) and hAP Lite (@home).
Sorry, I was referring tot the WAPR for the “Firewall” and “MAC Server” settings.
Masquerade on the CHR to allow all clients (PC) to have the same IP address on the wAPR for the response. (This is instead of the RoMON hop on the CHR)
“MAC server” , is under Tools, and sets the interfaces where MAC access is allowed.
With the default Firewall on the wAPR the SSTP interface (and eventually the EoIP) should be in the LAN interface list, to keep it simple)
Got same issue on one location, i see all romons devices and can ping and all but cant connect, completely shut down FW doesnt help, i think they broke it with some update again like same happen recently before, and cant updated them right now as i cant connect via romon…gona need to go to location.
I do think it has something to do with Winbox. If I enter the RoMON address of the CHR in Winbox and try to connect to it, essentially using the CHR as both RoMON agent and as host-to-manage, it will hang as well, so the VPN and the EoIP aren’t really the issue here.