Hi I realised that while ROS 6.45.7 doesn't allow you to specify the source address for a transport mode IPSec policy, you can specify the local address against the peer definition. Doing that has stopped the CHR apparently thinking the source address of the IPSec connection has changed and tearing ...

Hi I am experimenting with running a CHR in AWS. There is an IPSec/GRE connection to another CHR I have in a private datacentre through which OSPF operates. It basically works, I have the IPSec/GRE tunnel up and passing traffic and all is good. However! I noticed if I am not passing traffic across t...

I found this thread when I was Googling for the same question and thought I'd post my answer in case it helps anyone else (I realise it's some years since the original post) The info command (now) works via the API - tested with ROS 6.45.5. The following API call returns the RSSI, session-uptime and...

I confirm that Winbox 3.8 is unreliable (and unusable!) when it comes to adjusting Sce or Dst ports in both NAT rules and Firewall rules.

Another: Unable to disable IP Neighbor Discovery in Winbox 3.8.

All of this works fine in Winbox 3.7.

Using RB2011 with RouterOS 6.37.3.

Thanks
Giles.

your hyper-v client is a dhcp-client receiving the address from the DHCP server? Yes. Mikrotik - DHCP server. Guest OS on HOST and HOST himself - clients In addition - when described error is occurred, the affected clients remaining in "offering" state in DHCP server - Leases table with c...