Date: Sun, 14 Mar 2010 00:50:03 GMT From: Nick Leuta <skynick@mail.sc.ru> To: freebsd-pf@FreeBSD.org Subject: Re: kern/143543: [pf] [panic] PF route-to causes kernel panic Message-ID: <201003140050.o2E0o3kF088361@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/143543; it has been noted by GNATS. From: Nick Leuta <skynick@mail.sc.ru> To: bug-followup@FreeBSD.org, slava@aprec.ru Cc: Subject: Re: kern/143543: [pf] [panic] PF route-to causes kernel panic Date: Sun, 14 Mar 2010 03:34:50 +0300 I have the similar problem but in a bit different situation... the rule is: pass out quick route-to (vlan2 192.168.0.1) from 192.168.0.2 to any where 192.168.0.2 is binded to the vlan2 interface. The default gateway is 192.168.1.1 and is accessible through another interface. The "ping -S 192.168.0.2 192.168.0.1" command is used for test purposes, and (sic!) the 192.168.0.1 is unreachable (really down...). Without that rule we have: PING 192.168.0.1 (192.168.0.1) from 192.168.0.2: 56 data bytes <some timeout there> ping: sendto: Host is down <this message is repeated until Ctrl-C is pressed> With the rule we obtain the kernel panic (in "ping" process) instead of the "ping: sendto: Host is down" message after the same timeout as in the case without rule.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201003140050.o2E0o3kF088361>