Date: Thu, 19 Jun 2008 12:17:14 +0100 From: "Primeroz lists" <primeroz.lists@googlemail.com> To: "Giulio Ferro" <auryn@zirakzigil.org> Cc: freebsd-net@freebsd.org, Han Hwei Woo <hhw@pce-net.com> Subject: Re: Problems with vlan + carp + alias Message-ID: <55b8c6fe0806190417r440045e6ncf6e99945c453f10@mail.gmail.com> In-Reply-To: <485A3DC6.2030500@zirakzigil.org> References: <4859877A.3020300@zirakzigil.org> <4859A3A1.6070105@pce-net.com> <485A28ED.9020103@zirakzigil.org> <55b8c6fe0806190330p225ec6d1g65f8424efeab9b41@mail.gmail.com> <485A3DC6.2030500@zirakzigil.org>
next in thread | previous in thread | raw e-mail | index | archive | help
What is tcpdump showing for ping on 192.168.10.11 ? can you see echo reply exiting vlan10 interface ? what if you try from your server to "ping -S 192.168.10.11 192.168.10.254" ? Hi Primeroz, thanks for your answer. > I set all the carp interfaces, both base and alias, to the 255.255.255.255netmask > as you suggested. > This is my netstat now: > > ... > 192.168.10.0/24 link#11 UC 0 0 vlan10 > 192.168.10.254 link#11 UHLW 2 0 vlan10 > 192.168.10.10 192.168.10.10 UH 0 0 carp10 > 192.168.10.11 192.168.10.11 UH 0 0 carp10 > 192.168.10.12 192.168.10.12 UH 0 0 carp10 > ... > > As you see, the 192.168.10.0/24 is routed through the vlan10 interface, > and this should be correct. > > As before, I can ping 192.168.10.10, but not 192.168.10.11 and above. > > Could this be a bug of carp with alias interfaces? > > Thanks again. > Giulio. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55b8c6fe0806190417r440045e6ncf6e99945c453f10>