* Harald Dunkel <harald.dun...@aixigo.de> [2011-02-17 16:51]: > Hi folks, > > what would be the correct way to define network aliases > on a carp interface? Currently I have the code below, but > I see some packet filter problems around route-to that > might be related to a misconfigured carp interface. > > em1: > inet 172.12.96.5 255.255.252.0 NONE > inet alias 172.12.101.5 255.255.255.0 NONE > inet alias 172.12.126.5 255.255.255.0 NONE > -inet6 > group internal > > > carp1: > inet 172.12.96.4 255.255.252.0 NONE vhid 7 pass xxxxxxxxxxxxx carpdev > em1 advbase 1 advskew 0 > inet alias 172.12.101.4 255.255.255.0 NONE > inet alias 172.12.126.4 255.255.255.0 NONE > -inet6 > > > Do I have to add similar carpdev lines to the aliases? > Can I or should I drop the aliases on em1?
your way to configure aliases is correct, however, the masks are not. you are screwing up routing. you want an all-ones netmask on each and every IP address except one per subnet. alas you want 255.255.255.255 on the carp if's IPs. -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting
