Re: patch: bad ipv6 neighbor solicitation

This patch works for me. On Mon, 14 Dec 2009, Li, Qing wrote: Please find the more proper fix at http://people.freebsd.org/~qingli/nd6-patch.diff I realized I was slightly off in my previous email after I spent a bit more time looking through the problem. Both prefixes are present

Re: How can I find the reason network writes fail with ENOMEM on 7.x?

I've found a high number of failures in output of `vmstat -z` in category of "NetGraph data items". Trying to monitor those failures I see that they increase in short moments and stay at the level for longer. It's like NetGraph data items: 36, 546,1, 545, 514855314626,

net/mpd5, ppp, proxy-arp issues

Hi, Recently there have been several reports regarding issues with ppp, mpd5 and proxy-arp configuration over the ppp links. I read through the various postings and the problems seem to be: 1. Unable to add proxy-arp entries for the remote ppp clients. 2. Log showing "ifa_add_loopback_route: ins

Re: patch: bad ipv6 neighbor solicitation

You are correct. I added the route and it works fine. route add -inet6 2610:28:1800:4001::/64 -iface em0 Thanks, Tom On Dec 15, 2009, at 5:00 PM, Li, Qing wrote: > Thanks for sending me the routing table output. > > Actually I believe both your problems are indeed related to the > prefix rou

RE: patch: bad ipv6 neighbor solicitation

Thanks for sending me the routing table output. Actually I believe both your problems are indeed related to the prefix route. I was able to reproduce Dennis Glatting's problem, which was due to one of the prefix entry being off-link. In your case the prefix route for 2610:28:1800:4001:20e:cff:

RE: patch: bad ipv6 neighbor solicitation

Thanks for reporting back. I asked you for a routing table dump in my previous email, would you mind emailing it to me privately? -- Qing > -Original Message- > From: Tom Pusateri [mailto:pusat...@bangj.com] > Sent: Tuesday, December 15, 2009 1:28 PM > To: Li, Qing > Cc: freebsd-net@free

Re: patch: bad ipv6 neighbor solicitation

I didn't think this routing patch was related to the "bad neighbor solicitation messages" as suggested in the subject field but I tried it anyway. It does not fix my IPv6 problem. I still get "bad neighbor solicitation messages" and freebsd 8 doesn't respond to 4/5 IPv6 pings. Thanks, Tom On D

uath under FreeBSD 8.0-STABLE

Ok, I am able to load firmware with: uathload -d /dev/ugen4.3 but it also appears to do so when I plug it in... Now what? It doesn't show up in ifconfig... ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To

Re: bin/140571: [patch] ifconfig(8) does not set country DE

Synopsis: [patch] ifconfig(8) does not set country DE State-Changed-From-To: open->patched State-Changed-By: gavin State-Changed-When: Tue Dec 15 21:08:39 UTC 2009 State-Changed-Why: Fixed in HEAD Responsible-Changed-From-To: freebsd-net->gavin Responsible-Changed-By: gavin Responsible-Changed-

Re: bin/140571: commit references a PR

The following reply was made to PR bin/140571; it has been noted by GNATS. From: dfil...@freebsd.org (dfilter service) To: bug-follo...@freebsd.org Cc: Subject: Re: bin/140571: commit references a PR Date: Tue, 15 Dec 2009 20:44:26 + (UTC) Author: gavin Date: Tue Dec 15 20:44:12 2009 New

Re: kern/129135: [vge] vge driver on a VIA mini-ITX not working

Synopsis: [vge] vge driver on a VIA mini-ITX not working State-Changed-From-To: open->feedback State-Changed-By: yongari State-Changed-When: Tue Dec 15 20:14:33 UTC 2009 State-Changed-Why: Would you try the patch at the following URL? http://people.freebsd.org/~yongari/vge/vge.miipoll.diff The pa

Re: kern/82497: [vge] vge(4) on AMD64 only works when loaded late, not in loader.conf

Synopsis: [vge] vge(4) on AMD64 only works when loaded late, not in loader.conf State-Changed-From-To: open->feedback State-Changed-By: yongari State-Changed-When: Tue Dec 15 20:11:46 UTC 2009 State-Changed-Why: Would you try the patch at the following URL? http://people.freebsd.org/~yongari/vge/

Re: kern/81644: [vge] vge(4) does not work properly when loaded as a KLD

Synopsis: [vge] vge(4) does not work properly when loaded as a KLD State-Changed-From-To: feedback->closed State-Changed-By: yongari State-Changed-When: Tue Dec 15 20:07:50 UTC 2009 State-Changed-Why: Close, I can't reproduce this on recent 9-CURRENT. Responsible-Changed-From-To: freebsd-net->

Re: kern/141646: [em] em(4) + lagg(4) + vlan(4) generates ISL-tagged frames instead of 802.1q-tagged frames

Old Synopsis: em(4) + lagg(4) + vlan(4) generates ISL-tagged frames instead of 802.1q-tagged frames New Synopsis: [em] em(4) + lagg(4) + vlan(4) generates ISL-tagged frames instead of 802.1q-tagged frames Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Resp

Re: Chelsio S310E-BT: cxgbc0: prep adapter faliled (FreeBSD 8.0)

On Tue, Dec 15, 2009 at 09:01:32AM -0600, Jack Goral wrote: > Hi Navdeep, > > Thank you for response. > > I've build 8.0-stable as of Dec 11 and I get same error message as before: > > #kldload if_cxgb.ko > cxgbc): mem 0xf46fe000-0xf44fefffm > 0xf480-0xf4,0xf46ff000-0xf46 irq 30 at

RE: Chelsio S310E-BT: cxgbc0: prep adapter faliled (FreeBSD 8.0)

Hi Navdeep, Thank you for response. I've build 8.0-stable as of Dec 11 and I get same error message as before: #kldload if_cxgb.ko cxgbc): mem 0xf46fe000-0xf44fefffm 0xf480-0xf4,0xf46ff000-0xf46 irq 30 at device 0.0 on pci 3 prep adapter failed cxgbc0: no msi message to release dev

networking differences with php file_get_contents under 6.1 and 7.2 ?

Hello, I just observed a strange thing on 2 servers with a very similar setup (apache config, php version/ini, virtual ip addresses, etc.) but under 2 different FreeBSD versions. I would like to understand if is related to the OS version and why. To test, I have a short php script which calls