Mailing List Archive: Fwd: Re: OSPF passive-interface problem

grr, reply to being set to the user for a list sucks at times
sorry john you're getting this twise, every other mailing list in the world i
use sets the reply-to header to the mailing list except the quagga ones i swear.
</blah>

> On Wed, 6 Aug 2003, Gilad Arnold wrote:
>
> How about this. It doesn't hurt anything and if you take it away, it
> will break a whole hell of a lot of configs out there. Did
> "secondary" have an affair with your girlfriend or something? Why the
> boner for the secondary keyword?
>

Full marks there!

as for the secondary keyword.

I'm fairly new to using zebra but exactly how would i go about attaching alias ip's
to my FreeBSD machines via zebra?
FreeBSD doesn't create new virtual interfaces (eth0:1) like Linux does it attaches the ip
to the interface like so

rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.4.17 netmask 0xfffffffc broadcast 192.168.4.19
inet6 fe80::200:8cff:fe01:222f%rl0 prefixlen 64 scopeid 0x1
inet 192.168.4.21 netmask 0xfffffffc broadcast 192.168.4.23
inet 192.168.4.25 netmask 0xfffffffc broadcast 192.168.4.27
inet 192.168.4.29 netmask 0xfffffffc broadcast 192.168.4.31
inet 192.168.4.33 netmask 0xfffffffc broadcast 192.168.4.35
inet 192.168.4.37 netmask 0xfffffffc broadcast 192.168.4.39
inet 192.168.4.41 netmask 0xfffffffc broadcast 192.168.4.43
ether 00:00:8c:01:22:2f
media: Ethernet autoselect (10baseT/UTP)
status: active

for me the label keyword is useless! (well someone will tell me it's not now :P)

~Nick

Nick Grundy wrote:

> I'm fairly new to using zebra but exactly how would i go about attaching
> alias ip's to my FreeBSD machines via zebra?

Apparently, without any "aliasing" (nor "secondaries"), just type:

interface r10
ip address 192.168.4.17/30
ip address 192.168.4.21/30
ip address 192.168.4.25/30
...

You don't need to specify a 'secondary' nor an alias in zebra at all,
right now it's only there as extra for Cisco-compatibility and Linux
alias control (respectively).

> FreeBSD doesn't create new virtual interfaces (eth0:1) like Linux does it
> attaches the ip to the interface

Aliases are not necessary in Linux either, in newer kernels they're more
of attributes attached to IP addresses for backward compatibility.

> rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet 192.168.4.17 netmask 0xfffffffc broadcast 192.168.4.19
> inet6 fe80::200:8cff:fe01:222f%rl0 prefixlen 64 scopeid 0x1
> inet 192.168.4.21 netmask 0xfffffffc broadcast 192.168.4.23
> inet 192.168.4.25 netmask 0xfffffffc broadcast 192.168.4.27
> inet 192.168.4.29 netmask 0xfffffffc broadcast 192.168.4.31
> inet 192.168.4.33 netmask 0xfffffffc broadcast 192.168.4.35
> inet 192.168.4.37 netmask 0xfffffffc broadcast 192.168.4.39
> inet 192.168.4.41 netmask 0xfffffffc broadcast 192.168.4.43
> ether 00:00:8c:01:22:2f
> media: Ethernet autoselect (10baseT/UTP)
> status: active

Sure, right now your addresses are of distinct subnet ranges. What
happens if you add 192.168.4.65/28 and 192.168.4.66/28, in that order?
Would one of them be denoted as a secondary to the other? What happens
when you delete the first one? (is the other one gone as well?)

> for me the label keyword is useless! (well someone will tell me it's not
> now :P)

No clue.

Gilad