Current problem reports assigned to freebsd-net@FreeBSD.org

[FreeBSD bugmaster]

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker  Resp.  Description

o kern/160206  net[gif] gifX stops working after a while (IPv6 tunnel)
o kern/159817  net[udp] write UDPv4: No buffer space available (code=55)
o kern/159795  net[tcp] excessive duplicate ACKs and TCP session freezes
o kern/159629  net[ipsec] [panic] kernel panic with IPsec in transport m
o kern/159621  net[tcp] [panic] panic: soabort: so_count
o kern/159603  net[netinet] [patch] in_ifscrubprefix() - network route c
o kern/159602  net[netinet] [patch] arp_ifscrub() is called even if IFF_
o kern/159601  net[netinet] [patch] in_scrubprefix() - loopback route re
o kern/159353  net[netinet] [patch] conditional call of ifa_del_loopback
o kern/159294  net[em] em watchdog timeouts
o kern/159203  net[wpi] Intel 3945ABG Wireless LAN not support IBSS
o kern/158930  net[bpf] BPF element leak in ifp->bpf_if->bif_dlist
o kern/158726  net[ip6] [patch] ICMPv6 Router Announcement flooding limi
o kern/158694  net[ix] [lagg] ix0 is not working within lagg(4)
o kern/158665  net[ip6] [panic] kernel pagefault in in6_setscope()
o kern/158635  net[em] TSO breaks BPF packet captures with em driver
f kern/157802  net[dummynet] [panic] kernel panic in dummynet
o kern/157785  netamd64 + jail + ipfw + natd = very slow outbound traffi
o kern/157429  net[re] Realtek RTL8169 doesn't work with re(4)
o kern/157418  net[em] em driver lockup during boot on Supermicro X9SCM-
o kern/157410  net[ip6] IPv6 Router Advertisements Cause Excessive CPU U
o kern/157287  net[re] [panic] INVARIANTS panic (Memory modified after f
o kern/157209  net[ip6] [patch] locking error in rip6_input() (sys/netin
o kern/157200  net[network.subr] [patch] stf(4) can not communicate betw
o kern/157182  net[lagg] lagg interface not working together with epair 
o kern/156877  net[dummynet] [panic] dummynet move_pkt() null ptr derefe
o kern/156667  net[em] em0 fails to init on CURRENT after March 17
o kern/156408  net[vlan] Routing failure when using VLANs vs. Physical e
o kern/156328  net[icmp]: host can ping other subnet but no have IP from
o kern/156317  net[ip6] Wrong order of IPv6 NS DAD/MLD Report
o kern/156283  net[ip6] [patch] nd6_ns_input - rtalloc_mpath does not re
o kern/156279  net[if_bridge][divert][ipfw] unable to correctly re-injec
o kern/156226  net[lagg]: failover does not announce the failover to swi
o kern/156030  net[ip6] [panic] Crash in nd6_dad_start() due to null ptr
o kern/155772  netifconfig(8): ioctl (SIOCAIFADDR): File exists on direc
o kern/155680  net[multicast] problems with multicast
s kern/155642  net[request] Add driver for Realtek RTL8191SE/RTL8192SE W
o kern/155604  net[flowtable] Flowtable excessively caches dest MAC addr
o kern/155597  net[panic] Kernel panics with "sbdrop" message
o kern/155585  net[tcp] [panic] tcp_output tcp_mtudisc loop until kernel
o kern/155420  net[vlan] adding vlan break existent vlan
o bin/155365   net[patch] routed(8): if.c in routed fails to compile if 
o kern/155177  net[route] [panic] Panic when inject routes in kernel
o kern/155030  net[igb] igb(4) DEVICE_POLLING does not work with carp(4)
o kern/155010  net[msk] ntfs-3g via iscsi using msk driver cause kernel 
o kern/155004  net[bce] [panic] kernel panic in bce0 driver
o kern/154943  net[gif] ifconfig gifX create on existing gifX clears IP
s kern/154851  net[request]: Port brcm80211 driver from Linux to FreeBSD
o kern/154850  net[netgraph] [patch] ng_ether fails to name nodes when t
o kern/154679  net[em] Fatal trap 12: "em1 taskq" only at startup (8.1-R
o kern/154600  net[tcp] [panic] Random kernel panics on tcp_output
o kern/154557  net[tcp] Freeze tcp-session of the clients, if in the gat
o kern/154443  net[if_bridge] Kernel module bridgestp.ko missing after u
o kern/154286  net[netgraph] [panic] 8.2-PRERELEASE panic in netgraph
o kern/154255  net[nfs] NFS not responding
o kern/154214  net[stf] [panic] Panic when creating stf interface
o kern/154185  netrace condition in mb_dupcl
o kern/154169  net[multicast] [ip6] Node Information Query multicast add
o kern/154134  net[ip6] stuck kernel state in LISTEN on ipv6 daemon whic
o kern/154091  net[netgraph] [panic] netgraph, unaligned mb

Re: tcp failing to recover from a packet loss under 8.2-RELEASE?

[Andre Oppermann]

On 29.08.2011 02:08, Lawrence Stewart wrote:

On 08/14/11 23:53, Steven Hartland wrote:

- Original Message - From: "Lawrence Stewart"



Here's my tweaked version of Andre's patch:
http://people.freebsd.org/~lstewart/patches/misctcp/tcp_reass.c-logdebug%2bmissingsegment-20110811-lstewart.diff




Still testing this and just noticed that the patch fails to
compile when INVARIANTS is enabled. The KASSERT calls need
()'s around the split strings.


oops, sorry. Compile tested on 8-STABLE without INVARIANTS enabled :/

Any further feedback with respect to the patch? Plan to submit it to re@ later 
this week for
inclusion in 9.0.


I'm not sure these excessive KASSERT's are really necessary. Probably one
covering those cases at the start of the function is sufficient.

I was about to send the original patch to re@ for approval as well now
that I'm back from vacation and fully available again.  Don't mind if
you do it if you've got the time.

--
Andre
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Request for information/comment on default-free zone router properties

[Ivo Vachkov]

Hello all,

First of all, I'd like to apologize if my question is considered
highly off-topic. I ask it only with regard to the current FreeBSD
routing table implementation.

Is there any (no need to be official) information what is the number
of different routes (for IPv4 and IPv6) on a default-free zone (DFZ)
router in the Internet? I vaguely remember the number 450 000+
distinct routes for IPv4? But what about IPv6?

On a related note, what is the number of the network interfaces on a
DFZ router? No need for exact number, educated guess/estimation would
be greatly appreciated too.

Thank you very much in advance.

-- 
Ivo Vachkov
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Request for information/comment on default-free zone router properties

[sthaug]

> Is there any (no need to be official) information what is the number
> of different routes (for IPv4 and IPv6) on a default-free zone (DFZ)
> router in the Internet? I vaguely remember the number 450 000+
> distinct routes for IPv4? But what about IPv6?

See http://www.cidr-report.org - it has all the information you need.

Extract from the weekly post to Nanog:

Recent Table History
Date  PrefixesCIDR Agg
19-08-11371450  219002
20-08-11371427  219147
21-08-11371547  219346
22-08-11371326  218957
23-08-11371090  219346
24-08-11371769  219465
25-08-11372189  219508
26-08-11372363  219490

> On a related note, what is the number of the network interfaces on a
> DFZ router? No need for exact number, educated guess/estimation would
> be greatly appreciated too.

How long is a piece of string? "It depends."  And the same is the case
for number of interfaces. You obviously need a minimum of three for a
router to do anything "interesting" with the packets. Also, it depends
on whether you're talking about physical interfaces or logical (sub)
interfaces. I'd say anything from 3 to 20 is fairly typical.

Steinar Haug, Nethelp consulting, sth...@nethelp.no
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

RE: ifconfig -alias with duplicate netmasks work?

[Li, Qing]

Hi,

Yes, the address alias and its associated prefix installation code changed. 
Operationally it makes sense because all addresses of that same prefix go
through one route utilizing that given interface.

The side effect is you can have two separate interfaces on the same prefix,
but only a single route is installed, which is associated with the address
installed first.

The other interfaces won't be utilized for outgoing traffic unless you enable
RADIX_MPATH option in the kernel configuration.

I think the manpage needing updates, and I am partly guilty for not having time
to update the content, which does take considerable amount of time for actual 
behavior verification on different released versions.

I am now resuming work on FBSD after a long hiatus, updating the route manpage 
is on my to-do list.

--Qing


> -Original Message-
> From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-
> n...@freebsd.org] On Behalf Of John
> Sent: Monday, August 22, 2011 4:49 PM
> To: FreeBSD Net
> Subject: ifconfig -alias with duplicate netmasks work?
> 
> Fellow Net'ers
> 
>Debugging an nfs locking problem to a linux host, I accidently
> issued some ifconfig commands on the bsd server (9-current) and
> found that duplicate netmasks seem to work fine. For instance:
> 
> bce0: flags=8843 metric 0 mtu
> 1500
>   options=c01bb N_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>
>   ether d4:85:64:66:2a:14
>   inet6 fe80::d685:64ff:fe66:2a14%bce0 prefixlen 64 scopeid 0x1
>   inet 10.24.99.127 netmask 0x broadcast 10.24.255.255
>   inet 10.24.99.128 netmask 0x broadcast 10.24.255.255
>   inet 10.24.99.126 netmask 0x broadcast 10.24.255.255
>   nd6 options=29
>   media: Ethernet autoselect (1000baseT )
>   status: active
> 
> via the commands:
> 
> ifconfig bce0 inet 10.24.99.127 netmask 0x broadcast
> 10.24.255.255
> ifconfig bce0 inet 10.24.99.128 netmask 0x broadcast
> 10.24.255.255 alias
> ifconfig bce0 inet 10.24.99.126 netmask 0x broadcast
> 10.24.255.255 alias
> 
> The man page for ifconfig says one 'must' use a different netmask,
> typically 0x. However, everything still seems to work ok.
> 
> Has something changed, is the manpage wrong, am I totally missing
> something?
> 
> Thanks,
> John
> 
> man ifconfig
> 
> If the address
> is on the same subnet as the first network address for this
> interface, a non-conflicting netmask must be given.  Usually
> 0x is most appropriate.
> ___
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: kern/160300: [if_bridge] [patch] bridge(4) should attempt to use a static MAC address.

[linimon]

Old Synopsis: bridge(4) should attempt to use a static MAC address.
New Synopsis: [if_bridge] [patch] bridge(4) should attempt to use a static MAC 
address.

Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Aug 30 01:46:51 UTC 2011
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=160300
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: kern/160300: [if_bridge] [patch] bridge(4) should attempt to use a static MAC address.

[thompsa]

Synopsis: [if_bridge] [patch] bridge(4) should attempt to use a static MAC 
address.

Responsible-Changed-From-To: freebsd-net->thompsa
Responsible-Changed-By: thompsa
Responsible-Changed-When: Tue Aug 30 01:49:53 UTC 2011
Responsible-Changed-Why: 
Grab.

http://www.freebsd.org/cgi/query-pr.cgi?pr=160300
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: kern/160293: [ieee80211] ppanic] kernel panic during network setup at boot

[linimon]

Old Synopsis: kernel panic during network setup at boot
New Synopsis: [ieee80211] ppanic] kernel panic during network setup at boot

Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Aug 30 02:15:06 UTC 2011
Responsible-Changed-Why: 
Attempt to reclassify.

http://www.freebsd.org/cgi/query-pr.cgi?pr=160293
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: arpresolve: can't allocate llinfo

[Chris Miller]

Qing-

This patch seems to be working. I was not seeing the issue every time so I
can't say with 100% certainty, but I'd say I'm 95% certain at this point. If
you don't hear otherwise in the next few days, assume that it is fixed.

Thanks for your help.

-Chris


On Sat, Aug 27, 2011 at 2:13 PM, Li, Qing  wrote:

> Hi,
>
> Could you please try the patch sitting at
>
>http://people.freebsd.org/~qingli/in.c.diff
>
> and let me know if it works for you?
>
> Thanks,
>
> -- Qing
>
>
> > -Original Message-
> > From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-
> > n...@freebsd.org] On Behalf Of Chris Miller
> > Sent: Tuesday, August 16, 2011 3:05 PM
> > To: freebsd-net@freebsd.org
> > Subject: arpresolve: can't allocate llinfo
> >
> > I'm using FreeBSD 8.1 and I'm seeing the following messages spit out
> > frequently.
> >
> > IPv4 address: "169.254.231.172" is not on the network
> > arpresolve: can't allocate llinfo for 169.254.231.172
> >
> > Background:
> > I have two interfaces attached to the same LAN, both configured using
> > 169.254/16 link local automatic addressing.
> > ARP entries exist for each interface.
> > There are two routing entries for 169.254.0.0/16, one going out each
> > interface.
> >
> > I've done some debugging and it appears that this happens when a packet
> > is
> > received on one of the interfaces and while sending the reply the
> > routing
> > lookup code says that we should send it out the other interface. This
> > causes
> > the "not on the network" message.
> >
> > I'm looking for suggestions or patches to allow this configuration to
> > work
> > as I need to have both interfaces on this network for redundancy.
> >
> > Thanks for any help.
> >
> > -Chris Miller
> > ___
> > freebsd-net@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-net
> > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

RE: arpresolve: can't allocate llinfo

[Li, Qing]

Thank you Chris for the verification. I will wait a few days before committing 
the patch.

--Qing


From: Chris Miller [mailto:chrismiller@gmail.com]
Sent: Monday, August 29, 2011 7:31 PM
To: Li, Qing
Cc: freebsd-net@freebsd.org
Subject: Re: arpresolve: can't allocate llinfo

Qing-

This patch seems to be working. I was not seeing the issue every time so I 
can't say with 100% certainty, but I'd say I'm 95% certain at this point. If 
you don't hear otherwise in the next few days, assume that it is fixed.

Thanks for your help.

-Chris

On Sat, Aug 27, 2011 at 2:13 PM, Li, Qing 
mailto:qing...@bluecoat.com>> wrote:
Hi,

Could you please try the patch sitting at

   
http://people.freebsd.org/~qingli/in.c.diff

and let me know if it works for you?

Thanks,

-- Qing


> -Original Message-
> From: owner-freebsd-...@freebsd.org 
> [mailto:owner-freebsd-
> n...@freebsd.org] On Behalf Of Chris Miller
> Sent: Tuesday, August 16, 2011 3:05 PM
> To: freebsd-net@freebsd.org
> Subject: arpresolve: can't allocate llinfo
>
> I'm using FreeBSD 8.1 and I'm seeing the following messages spit out
> frequently.
>
> IPv4 address: "169.254.231.172" is not on the network
> arpresolve: can't allocate llinfo for 169.254.231.172
>
> Background:
> I have two interfaces attached to the same LAN, both configured using
> 169.254/16 link local automatic addressing.
> ARP entries exist for each interface.
> There are two routing entries for 169.254.0.0/16, one 
> going out each
> interface.
>
> I've done some debugging and it appears that this happens when a packet
> is
> received on one of the interfaces and while sending the reply the
> routing
> lookup code says that we should send it out the other interface. This
> causes
> the "not on the network" message.
>
> I'm looking for suggestions or patches to allow this configuration to
> work
> as I need to have both interfaces on this network for redundancy.
>
> Thanks for any help.
>
> -Chris Miller
> ___
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to 
> "freebsd-net-unsubscr...@freebsd.org"

___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"