Truthfully both are matters of preference and all about how you go about
it. Configuring redistributed connected is perfectly fine if you know
what you are doing. If you have self control and play within the
boundaries you will be fine. This is coming from someone who both has on
more than one occasion dated sisters and redistributed static and
connected routes. I agree it is something that people who do not know
what they are doing regularly enable for simplicity, but those same
people will more than likely make other config issues with OSPF that
will cause problems. Rules like don't ever use feature X because you may
not know what it does could apply to anything and there is a reason and
a purpose for all. Some people could argue that people make the mistake
of adding to many networks in to OSPF and accidentally leak it out, by
not knowing to make all interfaces passive by default. Same goes for
sisters if you accidentally talk about the girl you hooked up with at a
party with your friend there while your dating his sister....
On 1/2/2020 4:57 PM, Ken Hohhof wrote:
The only reason I can think of, is that you have to be careful if you assign an
IP address like 192.168.88.1 or 169.254.1.x to an interface for maybe
administrative purposes, if that interface ever becomes active, and you don't
have a route filter, then the router will advertise that block via OSPF.
Can you be more specific why it is bad bad bad?
I have actually been known to redistribute static routes (usually with a
filter). I'm guessing you would characterize that as 4 or 5 bads? Usually
this is to route a small block to a microPOP or customer router that I don't
want to be an OSPF peer. In some cases the customer router is connected via
PPPoE. I made the mistake once of trying to mix PPPoE and OSPF on an
interface. That was indeed very bad.
Oh, and I hope you realize some people like doing bad things, dangerous things,
forbidden things. Like if a girl wants a guy to ask her out, she will get a
friend to tell him she's off limits, which will make her irresistible. But
then:
https://tvtropes.org/pmwiki/pmwiki.php/Main/MySisterIsOffLimits
-----Original Message-----
From: AF <af-boun...@af.afmug.com> On Behalf Of Dennis Burgess via AF
Sent: Thursday, January 2, 2020 3:16 PM
To: AnimalFarm Microwave Users Group <af@af.afmug.com>
Cc: Dennis Burgess <dmburg...@linktechs.net>
Subject: Re: [AFMUG] PPPoE and /32's
NEVER redistribute connected... bad bad bad .
The sub area you can announce out the /25 or whatever it is, but keep /32s from
leaving the stub area. Your OSPF-out filters do not work inner area, i.e.
between backbone and backbone routers, only intra-area, that means area 44
(stub) it will filter out the /32s..
Dennis Burgess, Mikrotik Certified Trainer MTCNA, MTCRE, MTCWE, MTCTCE, MTCINE,
MTCSE, HE IPv6 Sage, Cambium ePMP Certified Author of "Learn RouterOS- Second
Edition”
Link Technologies, Inc -- Mikrotik & WISP Support Services
Office: 314-735-0270 Website: http://www.linktechs.net Create Wireless
Coverage’s with www.towercoverage.com
-----Original Message-----
From: AF <af-boun...@af.afmug.com> On Behalf Of Adam Moffett
Sent: Thursday, January 2, 2020 12:10 PM
To: af@af.afmug.com
Subject: [AFMUG] PPPoE and /32's
If you redistribute connected routes on a PPPoE server you get a route for
every /32 and that's undesirable.
My solution currently is to NOT redistribute connected and instead just
advertise the larger network which will encompass all the /32's.
I read a presentation suggesting to use an OSPF stub area for the PPPoE
concentrator. Is there a reason I'd want to use a stub area instead of
specifying the network to distribute?
--
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com
--
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com
--
Trey Scarborough
VP Engineering
3DS Communications LLC
p:9729741539
--
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com
