Ok
I too have been struck by this *multiple* times on my base home router.
I am not sure how its happening, but I have placed in my kernel a special
catch that if the default route is set via the normal route.c path and it
is *not* the default route to my ISP, I will crash the kernel.
My thought
On Tue, Apr 23, 2013 at 1:08 PM, Randall Stewart wrote:
> Ok
>
> I too have been struck by this *multiple* times on my base home router.
>
I hate "me too" style posts, since often they conflate unrelated
issues - however, "me too"!
In my scenario, I have a simple home router with a wan if connec
On 03/13/2013 06:27, Mark Martinec wrote:
> Having multiple IPv6 subnets on the same wire is asking for trouble.
>
> For example, I believe an ICMP redirect still (in 9.1) does not create
> a temporary route:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=152791
> which beat us hard time (random un
I am running FreeBSD 9-STABLE (updated yesterday: FreeBSD 9.1-STABLE #15: Mon
Apr 22 07:45:07 UTC 2013) with VirtualBox 4.2.6 from ports … the hardware is
using a Broadcom ethernet:
bce0: mem 0xf400-0xf5ff
irq 16 at device 0.0 on pci7
miibus0: on bce0
bce0: Ethernet address: 00:22:19
Hello all,
I have a question here about how FreeBSD (8.1-RELEASE-p13 specifically)
behaves when acting as a firewall. I understand the pf process is
"giant locked" to a single CPU core when inspecting packets inbound and
outbound. I was wondering, how does that manifest when I look at "top
Dnia wtorek, 23 kwietnia 2013 o 21:49:21 Erich Weiler napisał(a):
> Hello all,
>
> I have a question here about how FreeBSD (8.1-RELEASE-p13 specifically)
> behaves when acting as a firewall. I understand the pf process is
> "giant locked" to a single CPU core when inspecting packets inbound and
