Re: Problem with carp and inet alias
* Sebastian John ba...@fukz.de [2013-11-19 19:00]: try to use the correct network mask in alias configuration: inet alias 200.200.200.163 255.255.255.240 try to not give wrong advice. all-ones netmask is EXACTLY the right thing here. probably even for the first (main) address, unless carpdev is unnumbered. -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services GmbH, AG Hamburg HRB 128289, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting pgp07t8jYq4FG.pgp Description: PGP signature
Re: Problem with carp and inet alias
Hello, try to use the correct network mask in alias configuration: inet alias 200.200.200.163 255.255.255.240 .. Sebastian On Tue, Nov 19, 2013 at 02:55:45AM -0800, Christiano Liberato wrote: Hi, fw1: 200.200.200.168 fw2: 200.200.200.172 carp0 (for twho fw) inet 200.200.200.162 255.255.255.240 200.200.200.175 vhid 1 advskew 0 carpd= ev em0 pass senha inet alias 200.200.200.163 255.255.255.255 inet alias 200.200.200.164 255.255.255.255 inet alias 200.200.200.165 255.255.255.255 inet alias 200.200.200.166 255.255.255.255 inet alias 200.200.200.167 255.255.255.255 After restart the fw, I can not access the router (gateway). I think it has= problems default route in between. Searching the internet, I found the post http://openbsd.7691.n7.nabble.com/= Carp-with-aliases-route-problem-td84179.html, Todd T. Fries-2, saying that = in /etc/netstart interface carp rises after the physical and do not know if= it is necessary to change this sequence. Anyone have an environment with carp and alias working to give an opinion? Thanks. -- signature.asc Description: Digital signature
Re: Problem with carp and inet alias
Sebastian, my mask is /28 and 255.255.255.240 is fake for post in the list. My first ip is x.x.x.160 (network) and last x.x.x.175 (broadcast). Not understand what is wrong. 2013/11/19 Sebastian John ba...@fukz.de Hello, try to use the correct network mask in alias configuration: inet alias 200.200.200.163 255.255.255.240 .. Sebastian On Tue, Nov 19, 2013 at 02:55:45AM -0800, Christiano Liberato wrote: Hi, fw1: 200.200.200.168 fw2: 200.200.200.172 carp0 (for twho fw) inet 200.200.200.162 255.255.255.240 200.200.200.175 vhid 1 advskew 0 carpd= ev em0 pass senha inet alias 200.200.200.163 255.255.255.255 inet alias 200.200.200.164 255.255.255.255 inet alias 200.200.200.165 255.255.255.255 inet alias 200.200.200.166 255.255.255.255 inet alias 200.200.200.167 255.255.255.255 After restart the fw, I can not access the router (gateway). I think it has= problems default route in between. Searching the internet, I found the post http://openbsd.7691.n7.nabble.com/= Carp-with-aliases-route-problem-td84179.html, Todd T. Fries-2, saying that = in /etc/netstart interface carp rises after the physical and do not know if= it is necessary to change this sequence. Anyone have an environment with carp and alias working to give an opinion? Thanks. --
Re: Problem with carp and inet alias
On 2013/11/19 02:55, Christiano Liberato wrote: Hi, fw1: 200.200.200.168 fw2: 200.200.200.172 carp0 (for twho fw) inet 200.200.200.162 255.255.255.240 200.200.200.175 vhid 1 advskew 0 carpd= ev em0 pass senha inet alias 200.200.200.163 255.255.255.255 inet alias 200.200.200.164 255.255.255.255 inet alias 200.200.200.165 255.255.255.255 inet alias 200.200.200.166 255.255.255.255 inet alias 200.200.200.167 255.255.255.255 After restart the fw, I can not access the router (gateway). I think it has= problems default route in between. Searching the internet, I found the post http://openbsd.7691.n7.nabble.com/= Carp-with-aliases-route-problem-td84179.html, Todd T. Fries-2, saying that = in /etc/netstart interface carp rises after the physical and do not know if= it is necessary to change this sequence. Anyone have an environment with carp and alias working to give an opinion? Thanks. It's probably best if you post the routing table (netstat -rnfinet if you are only concerned with ipv4) from when it's failing, also ifconfig -A might be helpful. And of course which OS, which version, and exactly what you see (just packets dropped? or is there an error message?)...
