What's a stub area that's also through the default route?

senseivita

I'm trying to figure out how to set up a remote router's network and/or area type so it's (a direct) part of the backbone.

From what I've learned so far, what I should do is to create a virtual link with area zero/backbone. I'm not sure if that's every single router on area zero that it can't reach directly or some sort of virtualized/logical connection point (like a CARP). Regardless, since there's no options for it in the GUI, before I get to the CLI* I'd like to explore what other options are there to set it up.

~~The~~ my problem is that it matches more than one do and don't of a certain something, for instance;

It's like a stub area, except it's on the default route but not on the only route out and needs routes back as if it were a local network.
It's on a OpenVPN tap tunnel and a bridgeless (ovpnsX and ovpncX assigned directly without bridging) /24 subnet; therefore a broadcast network, yet currently it's a "Point-to-point with extras" (i.e; multicast).

This is the topology (more or less):
alt text

For what it's worth, all routes everywhere inside are available on the pseudo-isolated upstream router and the networks (and gateways) to which the public interfaces of it connect, they appear on the routing tables all the way inside/downstream the network, but it's still a broken area zero which is supposed to be a huge no-no, and only router ID 1.0.0.1, the one "breaking" area zero apart is the only one that has formes full adjacencies with all routers.

alt text

It wasn't easy to get them to do so, not the first time at least, I'm a little uneasy about changing things without blindly now that I made a little progress.

Could you guide me a little on what should I do? ( Please?! )

*: Full disclosure: I already got to the CLI, learned how to use vtysh a bit, and I'm already using the huge box to paste a custom config in one of the routers but that hasn't thought me fully about area/network types. :)

Derelict

@senseivita If you need to be able to announce routes into the backbone from an otherwise stubby area, that is generally called a Not So Stubby Area

senseivita

@derelict Thank you!

I had a hunch about that, but as I also saw this "NSSA Totally Stub Area" and I'm like what the ff—is that one or two things? "Not-So-Stubby-Area Totally Stub Area"

You were right one time because about to configure the virtual link, I realized it's at the other side of an ABR. The ABR already would know about it.

I tried setting up the edge router as a type shortcut ABR, but it would form no adjacencies at all. This was only just now though, I haven't had time to explore; inadvertently I enabled DHCP snooping on two switchports to a hypervisor which it's statically multi-homed itself, but the DHCP had migrated there at some point and it was only a matter of time before leases expired and created chaos.

DHCP issues look a lot like multicast issues. "OSPF uses multicast…" of course I went with the worst possible choice.

Thanks again — I can sleep now. *sleeping-standing-up-emoji…-or-something*