![]() ![]() In IPv6, you must define each interface explicitly anyway, so you may as well get used to that being a part of the process. IMO, it's better to explicitly define each interface with its own network=x.x.x.x/30 entry to give yourself the 100% granularity that will come in handy later. You couldn't individually disable OSPF on any particular interface within that range if the need were to arise. The drawback to this method is that it's an all-or-nothing proposition. You could use network=10.10.2.0/24 and then any /30 interface within that /24 block would become active in OSPF. so at the /routing ospf network segment, I enter every interface ip to networks like 10.10.2.5/30, 10.10.2.1/30, 10.10.2.20/30 so in here is better to use /24 or better to use /30. one some routers there is 3-4 device on their ether interfaces and i connect them to each other with /30 ip addresses. Set redistribute-connected=as-type-1 router-id=10.255.255.2Īdd authentication=simple authentication-key=xxx interface=ether1-10.10.0.3 network-type=broadcastĪdd authentication=simple authentication-key=xxx interface=LoopBack network-type=broadcastĪdd area=backbone network=10.255.255.2/32Īm I going on the correct way to remove bridges and go routed network ? and also do i need add loopback ip to ospf network(area=backbone network=10.255.255.2/32) ?Ĭan i use 10.10.2.0/24 instead of 10.10.2.0/30 at /routing ospf network ? cause i will remove every device from bridge step by step and I would like to use 10.10.2.0/24 range. Set redistribute-connected=as-type-1 router-id=10.255.255.1Īdd authentication=simple authentication-key=xxxx interface=Router2 network-type=broadcast priority=2Īdd authentication=simple authentication-key=xxxx interface=ether1-PPPoE-Server network-type=broadcastĪdd authentication-key=xxxx interface=loopback network-type=broadcastĪdd area=backbone network=10.255.255.1/32Īdd address=10.10.2.2/30 interface=ether1-10.10.0.3 network=10.10.2.0Īdd address=10.255.255.2 interface=LoopBack network=10.255.255.2 I'd suppose there were NAT rules, so even packets sent from the interface-state-independent address got src-nated to the address attached to the WAN interface when routed out through that interface.I remove PPPoE_Server link interface from bridge and give them 10.10.2.1/30 ip to their ethernet interfacesĪnd here is ip and OSPF settings at gateway router Īdd address=10.10.0.3/23 interface=Router2 network=10.10.0.0Īdd address=10.10.2.1/30 interface=ether1-PPPoE-Server network=10.10.2.0Īdd address=10.255.255.1 interface=loopback network=10.255.255.1 So the question is what traffic you were torching in the latter case and whether there were any NAT rules configured. What torch shows depends on the addresses in the packets, not on what address is attached to the interface. ![]() Even if the address fits into a subnet attached to some physical interface, Mikrotik will not respond ARP requests about that address even if they come through that physical interface. So a neighbor router only knows how to send a packet to that address if it has a route to it. To the second question - the interface-state-independent address only exists in the 元 domain. If there are no alternative paths in your network, there is no point in using interface-state-independent addresses. And you need that an outage of any link does not invalidate an IP address used by the dynamic routing protocols to talk to the router. It makes sense to use an "interface-state-independent" address in mesh topology networks with dynamic routing protocols, where you require path redundancy - if there is an outage on a link between nodes, the traffic gets routed via some other path instead. So the "interface-state-independent" address exists, but it is not attached to a loopback interface as such. ![]() So when you want to configure an IP address that will not depend on a state of any physical interface, you have to create a bridge interface with no member ports and attach the address to it. There is a "real" loopback interface on Mikrotik too, but it is not made visible in the RouterOS configuration. So on bare Linux systems, long before bridges were implemented, people started attaching addresses they needed to stay active no matter what to a loopback interface, and from there the shortcut "loopback address" comes. Addresses attached to a physical interfaces become inactive if the interface they are attached to goes down. The idea behind a "loopback address" is that this address is always active on the device. To the first question, I'd start from the fact that the popular name "loopback address" is technically wrong - it is a shortcut obfuscating the actual point. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |