Their problem was exactly what I am trying to accomplish now. Of course an answer was never posted.
Currently I have a PPPoE server setup within a /16 network. It has just one ethernet on the /16 to connect it. I want it to receive all the routes from the other routers sending information along the /16.
What I can tell is, when a PPPoE client connects, their route is added to the server, and everything’s fine. However, once OSPF realized there’s a new “interface/ip”, it starts sending out a route on how to get to the network. This is what I want to stop. Since there is no “network”, because it’s PPPoE. If ospf doesn’t add in it’s inactive route, then everything propogates properly.
Hopefully this makes some sense. And if there’s a better way that I can’t see because I’m in the forest, please let me know.
doesn’t work. This is set on my router that accept PPTP for my clients that have connection to ADSL trough my MTik.
It add this to OSPF routing table and I can’t get rid of it.
For pppoe. Make all pppoe interfaces passiv in ospf interface configuration. Add pppoe /16 network to different area than backbone and use area range. to aggregate all /32 routes into on e/16 network. This is the proper way how to set up ospf in such cases.
You didn’t understand me. I don’t want ospf to propagate pptp to other parts of network. This, mine, ROS is part of our network and it is part of OSPF routers that actively route our network. I doesn’t see difference from what you wrote and what I made on router. Sorry.
I made as you said. My pptp clients now gets 172.16.254.x IP’s and now ospf doesn’t propagate those IP’s anymore. My area on network covers only 10.0.0.0/8 subnets so 172.16.x.x is out of bussiness. I can’t set those pptp interaces as passive in OSPF interface properties because those pptp interfaces are made dinamicaly when clients connect.. For now it works. Thanks
Yo can set them passive, add ethernet interfaces explicitly and add one more entry for interface all with property passive=yes. In such configuration all dynamic interfaces will be passive.
Sorry to drag up an old thread, but it’s top of the searches on the subject so here goes.
While the solution from mrz is correct for an OSPF design where all routers are backbone routers, in larger networks this wont always be the case. The problem here then is filtering the PPPoE interfaces from the backbone, but using an area range command on the ABR then causes loss of routing for non-PPPoE devices on the same subnet. I think I have an easier solution for filtering PPPoE, even intra-area. Either configure a blackhole route and redistribute this into OSPF for the subnet and don’t add an area command for the PPPoE subnet, or configure a loopback for the subnet and set the OSPF instance to redistribute connected interfaces, but set an ospf-out filter on the subnet with /32 prefix length. I chose the latter as it allows engineers to connect on site without having to use PPPoE.
Yes, we figured this out already and figured out how to do it.
The trick, which wasn’t clear, is you purposely do not add the PPPoE subnets into the “networks” list on the Mikrotik under OSPF. Instead you redistribute connected (either as type 1 or type 2), and then the PPPoE subnets appear as type 5 (external) LSAs, and the ospf-out filter works on them.
The filter can then remove the /32’s for the individual tunnels, leaving behind the larger subnet.
The end result is that you get rid of the tunnel IPs without having to set up a separate stub area; the only change is that the PPPoE subnet appears as external (LSA type 5) instead of intra-area type 1, but I do not see any issues with this - unless you do, mrz? (we are already using this in production and it seems fine)