Mailing List Archive

On Thu, 7 Aug 2003, Nick Grundy wrote:

> > On Wed, 6 Aug 2003, Gilad Arnold wrote:
> 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


In Quagga (telnet to localhost port 2601), do this:

conf t
interface rl0
ip address 192.168.4.17/30
ip address 192.168.4.21/30 secondary
ip address 192.168.4.25/30 secondary
ip address 192.168.4.29/30 secondary
ip address 192.168.4.33/30 secondary
ip address 192.168.4.37/30 secondary
ip address 192.168.4.41/30 secondary

That will bind up all of those IP addresses on interface rl0. While it
might not CURRENTLY do anything special for "secondary" addresses, you
never know... You might move your routing platform to an operating system
that does.

Note... the ethX:Y notation in Linux is there for backwards
compatibility. It SHOULD go away sometime. IPTools will bind as many
addresses as someone likes onto ethX without the need for those silly :Y
"sub-interfaces."

Oh, one more thing. If you're running a Quagga router, I HIGHLY recommend
that you do ALL IP address configuration and routes (static and default
even) inside the Quagga interface. It makes life MUCH easier when you
don't have to remember what you've done with some silly network init
script 2 years down the road when you need to work on the router. You can
simply do a "sh running config" and get the whole picture at once.


--
---
John Fraizer | High-Security Datacenter Services |
President | Dedicated circuits 64k - 155M OC3 |
EnterZone, Inc | Virtual, Dedicated, Colocation |
http://www.enterzone.net/ | Network Consulting Services |