Old Synopsis: Can not set fib for packets originated from local host
New Synopsis: [ipfw] Can not set fib for packets originated from local host
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Fri Jan 2 09:57:11 UTC 2009
Responsible-
Adding a bit more info.. Here's the netstat -m and vmstat -z output after
the mbufs have had a while to build up:
-- netstat -m --
959510/235/959745 mbufs in use (current/cache/total)
257/133/390/25600 mbuf clusters in use (current/cache/total/max)
257/127 mbuf+clusters out of packet secondary zon
The following reply was made to PR kern/130059; it has been noted by GNATS.
From: "Jason DiCioccio"
To: bug-follo...@freebsd.org
Cc:
Subject: Re: kern/130059: [panic] Leaking 50k mbufs/hour
Date: Fri, 2 Jan 2009 13:02:47 -0800
--=_Part_175155_3729370.1230930167365
Content-Type: text/plai
Hi Michael,
The SCTP problem you were having was attributed to the arp-v2 changes.
The reason TCP and UDP works well is because the TCP and UDP
modules does not supply a route entry when calling ip_output().
Consequently in ip_output() the destination (sockaddr) was reinitialized
and the sin_port
Hi Qing,
I have tested your patch and it works!
Thanks you very much for your help.
Best regards
Michael
On Jan 2, 2009, at 11:15 PM, Li, Qing wrote:
Hi Michael,
The SCTP problem you were having was attributed to the arp-v2 changes.
The reason TCP and UDP works well is because the TCP and U
Hi Pyun,
I've noticed an issue for a while now with my chipset (I think that
this is post an MFC between 7.0 and 7.1, but I could be wrong).
Basically, each CPU (with the ULE scheduler) grabs the task to check
for media status, goes out and attempts to get an IP, and if the
timing of the s
Why would a local interface, reported as up in ifconfig, not respond
to a ping of its own IP address? The tun0 reported below doesn't,
and I have no idea how to debug it. (I've overwritten the two most-
significant octets of its IP address, which is Class B, so as not to
publicly identify the net
On Fri, 2 Jan 2009, per...@pluto.rain.com wrote:
> Why would a local interface, reported as up in ifconfig, not respond
> to a ping of its own IP address? The tun0 reported below doesn't,
> and I have no idea how to debug it. (I've overwritten the two most-
> significant octets of its IP add
Ian Smith wrote:
...
> > tun0: flags=8051 mtu 1412
> > inet6 fe80::2b0:d0ff:fe28:ad4f%tun0 prefixlen 64 scopeid 0x4
> > inet ZZZ.ZZZ.233.42 --> ZZZ.ZZZ.233.42 netmask 0x
> > Opened by PID 24635
>
> I don't know if this is relevant or not, but I've never
