I have 2 mikroticks in lan 192.168.8.0/24. 2011(192.168.8.1) and CHR(192.168.8.2). On 2011 port ether1 i have 1 main static ip and second extra that i am not using it wright now, i want to forward second static ip to CHR ether1. How can i do this?
It is hard to suggest anything without knowing the actual arrangement. Do you have a /29 subnet form the ISP, or is the second public address routed via the first one, or maybe there is yet another setup?
1 ip ..210.41/24 using it on 2011 now
2 ip ..210.54/24 reserve ip on using it now but want to assing it to CHR eher1 port
gateway ..210.1
2011
ether2 local in bridge 192.168.8.1/24
CHR
ehter1 192.168.8.2/24(what to forward ..210.54/24 here)
ehter2 192.168.8.3/24
Quite a punk ISP… anyway:
- either add a route dst-address=..210.42 gateway=192.168.8.2 and a selective arp-proxy /ip arp add adddress=..210.42 interface=ether1 publish=yes to the 2011 and on the CHR, /ip address add address=..210.54**/32** interface=ether1 (or basically any interface you wish, you can even use a macvlan interface if you want to allow firewall rules on the CHR to match on in-interface and it is running ROS 7)
- or you can create a WAN VLAN on the bridge on the 2011, add ether1 as an access port to that VLAN, and add that VLAN in trunk mode to the port to which the hypervisor is connected, if your hypervisor allows tagged frames and can deliver them tagged or tagless to the VMs
Yes, but it is not enough. You also have to set pvid=5 on the /interface/bridge/port row for ether1. You can leave the untagged list empty in the above window because ether1 will be added to it automatically as you do the previous step, but you must add also the bridge to the tagged list for VLAN 5 - see here why. To make these settings actually work, you have to set vlan-filtering on the bridge to yes. And finally you have to attach an /interface/vlan to the bridge and move the ..210.41/24 from ether1 to this /interface/vlan.
210.42 not 210.41?
Sorry, 210.54, no idea how I confused it for 210.42. In the routing case, you do not touch the 210.41 at all; in the bridging case, you move it from ether1 to vlan 5 interface on bridge.
Thank you very mutch! Routing way working flawlessly.
I have one problem after choosing routing way ihave high cycling increasing ping betweeen 192.168.8.1 and 8.2 2011 an chr
Sorry… even after translating it back to your suspected first language I cannot imagine what “high cycling increasing ping” means… can you post an example of the output of the ping command?
ping was 0.1
0.2
1
2
4
10
20
50
100
etc.
I solved it by disabling ether2 and bridge and done all routing through ether1 on CHR