freebsd-net Digest, Vol 365, Issue 3
freebsd-n...@freebsd.org
freeb...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-net
or, via email, send a message with subject or body 'help' to
freebsd-n...@freebsd.org
You can reach the person managing the list at
freebsd-...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-net digest..."
Today's Topics:
1. Samba Errors (John Dakos)
2. Re: kern/131153: [iwi] iwi doesn't see a wireless network
(Adam K Kirchhoff)
3. Re: kern/131162: [ath] Atheros driver bugginess and kernel
crashes (Adam K Kirchhoff)
4. Re: kern/144898: [wpi] [panic] wpi panics system (Dominic Fandrey)
5. Re: kern/131162: [ath] Atheros driver bugginess and kernel
crashes (rpa...@FreeBSD.org)
6. Workaround for mpd5 and 8.0 broken proxy arp? (J. English)
7. Re: Workaround for mpd5 and 8.0 broken proxy arp?
(Boris Kochergin)
8. Re: Workaround for mpd5 and 8.0 broken proxy arp?
(Boris Kochergin)
9. Re: Workaround for mpd5 and 8.0 broken proxy arp? (Mike Tancsa)
10. Re: Workaround for mpd5 and 8.0 broken proxy arp? (Ruslan Ermilov)
11. RE: Workaround for mpd5 and 8.0 broken proxy arp? (Li, Qing)
12. Re: kern/144564: lltable grows too much (Evgenii Davidov)
13. Re: Workaround for mpd5 and 8.0 broken proxy arp? (Ruslan Ermilov)
----------------------------------------------------------------------
Message: 1
Date: Tue, 30 Mar 2010 15:38:25 +0300
From: "John Dakos" <gda...@enovation.gr>
Subject: Samba Errors
To: <freeb...@freebsd.org>
Message-ID: <000001cad005$e65ed930$b31c8b90$@gr>
Content-Type: text/plain; charset="us-ascii"
I have FreeBSD 8.0 with samba, is work very well. But I have message errors
every minute.
I googled but nothing . any idea ?
thanks
Mar 30 15:13:18 zeus smbd[65156]: [2010/03/30 15:13:18, 0]
lib/util_sock.c:1491(get_peer_addr_internal)
Mar 30 15:13:18 zeus smbd[65156]: getpeername failed. Error was Socket is
not connected
Mar 30 15:13:18 zeus smbd[65156]: [2010/03/30 15:13:18, 0]
lib/access.c:410(check_access)
Mar 30 15:13:18 zeus smbd[65156]: [2010/03/30 15:13:18, 0]
lib/util_sock.c:1491(get_peer_addr_internal)
Mar 30 15:13:18 zeus smbd[65156]: getpeername failed. Error was Socket is
not connected
Mar 30 15:13:18 zeus smbd[65156]: [2010/03/30 15:13:18, 0]
lib/util_sock.c:1491(get_peer_addr_internal)
Mar 30 15:13:18 zeus smbd[65156]: getpeername failed. Error was Socket is
not connected
Mar 30 15:13:18 zeus smbd[65156]: [2010/03/30 15:13:18, 0]
lib/util_sock.c:1491(get_peer_addr_internal)
Mar 30 15:13:18 zeus smbd[65156]: getpeername failed. Error was Socket is
not connected
Mar 30 15:13:18 zeus smbd[65156]: Connection denied from 0.0.0.0
Mar 30 15:13:18 zeus smbd[65156]: [2010/03/30 15:13:18, 0]
lib/util_sock.c:738(write_data)
Mar 30 15:13:18 zeus smbd[65156]: [2010/03/30 15:13:18, 0]
lib/util_sock.c:1491(get_peer_addr_internal)
Mar 30 15:13:18 zeus smbd[65156]: getpeername failed. Error was Socket is
not connected
Mar 30 15:13:18 zeus smbd[65156]: write_data: write failure in writing to
client 0.0.0.0. Error Socket is not connected
Mar 30 15:13:18 zeus smbd[65156]: [2010/03/30 15:13:18, 0]
smbd/process.c:62(srv_send_smb)
Mar 30 15:13:18 zeus smbd[65156]: Error writing 5 bytes to client. -1.
(Socket is not connected)
------------------------------
Message: 2
Date: Tue, 30 Mar 2010 13:50:09 GMT
From: Adam K Kirchhoff <akirchho...@comcast.net>
Subject: Re: kern/131153: [iwi] iwi doesn't see a wireless network
To: freeb...@FreeBSD.org
Message-ID: <201003301350....@freefall.freebsd.org>
The following reply was made to PR kern/131153; it has been noted by GNATS.
From: Adam K Kirchhoff <akirchho...@comcast.net>
To: bug-fo...@FreeBSD.org, ad...@voicenet.com
Cc:
Subject: Re: kern/131153: [iwi] iwi doesn't see a wireless network
Date: Tue, 30 Mar 2010 09:26:23 -0400
This bug appears to be resolved now. iwi and ath are both seeing the
APs in question. There is a separate, new issue with iwi, but I'll
open up a new PR for it if I have to.
Adam
------------------------------
Message: 3
Date: Tue, 30 Mar 2010 14:10:07 GMT
From: Adam K Kirchhoff <ad...@mckella280.com>
Subject: Re: kern/131162: [ath] Atheros driver bugginess and kernel
crashes
To: freeb...@FreeBSD.org
Message-ID: <201003301410....@freefall.freebsd.org>
The following reply was made to PR kern/131162; it has been noted by GNATS.
From: Adam K Kirchhoff <ad...@mckella280.com>
To: bug-fo...@FreeBSD.org, ad...@voicenet.com
Cc:
Subject: Re: kern/131162: [ath] Atheros driver bugginess and kernel crashes
Date: Tue, 30 Mar 2010 09:27:56 -0400
This can be closed. ath is working with these APs now.
Adam
------------------------------
Message: 4
Date: Tue, 30 Mar 2010 14:50:02 GMT
From: Dominic Fandrey <kami...@bsdforen.de>
Subject: Re: kern/144898: [wpi] [panic] wpi panics system
To: freeb...@FreeBSD.org
Message-ID: <201003301450....@freefall.freebsd.org>
The following reply was made to PR kern/144898; it has been noted by GNATS.
From: Dominic Fandrey <kami...@bsdforen.de>
To: bug-fo...@FreeBSD.org, kami...@bsdforen.de
Cc:
Subject: Re: kern/144898: [wpi] [panic] wpi panics system
Date: Tue, 30 Mar 2010 16:43:15 +0200
Because there were so many net related commits in RELENG_8
recently I rebuilt my system today.
It appears that the system now doesn't panic any more. If at
all the connection, now works for a maximum of 10 seconds,
though.
I have to reload the if_wpi and wpifw modules to get it
running again (for another 10 seconds).
This is what ttyv0 looks like, the beacon misses start
after a couple of seconds:
wpi0: Regulatory Domain: MoW2
wpi0: Hardware Type: B
wpi0: Hardware Revision: ?
wpi0: SKU does support 802.11a
wpi0: [ITHREAD]
wlan0: Ethernet address: 00:1c:bf:58:3a:87
wpi0: timeout resetting Tx ring 1
wpi0: timeout resetting Tx ring 3
wpi0: timeout resetting Tx ring 4
microcode alive notification version 10e02 alive 1
microcode alive notification version 10e02 alive 1
wpi_newstate: INIT -> SCAN flags 0x0
wpi0: scan timeout
wpi_newstate: SCAN -> SCAN flags 0x0
microcode alive notification version 10e02 alive 1
microcode alive notification version 10e02 alive 1
wpi_newstate: SCAN -> AUTH flags 0x0
config chan 1 flags 8005 cck f ofdm 15
wpi_newstate: AUTH -> ASSOC flags 0x0
wpi_newstate: ASSOC -> RUN flags 0x0
config chan 1 flags 8005
wpi0: need multicast update callback
wpi0: need multicast update callback
wpi0: need multicast update callback
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
Beacon miss: 2728567458 >= 7
...
I also recognized that wlan0 always lists "txpower 0",
even if I try to set it manually (txpowermax is 50.0).
------------------------------
Message: 5
Date: Tue, 30 Mar 2010 15:21:18 GMT
From: rpa...@FreeBSD.org
Subject: Re: kern/131162: [ath] Atheros driver bugginess and kernel
crashes
To: ad...@voicenet.com, rpa...@FreeBSD.org, freeb...@FreeBSD.org
Message-ID: <201003301521....@freefall.freebsd.org>
Synopsis: [ath] Atheros driver bugginess and kernel crashes
State-Changed-From-To: open->closed
State-Changed-By: rpaulo
State-Changed-When: Tue Mar 30 15:20:56 UTC 2010
State-Changed-Why:
Submitter agrees to close PR.
http://www.freebsd.org/cgi/query-pr.cgi?pr=131162
------------------------------
Message: 6
Date: Tue, 30 Mar 2010 15:08:23 -0400
From: "J. English" <j_en...@kawasaki-tn.com>
Subject: Workaround for mpd5 and 8.0 broken proxy arp?
To: <freeb...@freebsd.org>
Message-ID: <005801cad03c$5f5128d0$1df37a70$@kawasaki-tn.com>
Content-Type: text/plain; charset="us-ascii"
Hello All,
I've recently set up a FreeBSD 8.0 VPN server with mpd5 for people to
connect remotely. However, looking at my mpd.log shows that I'm having
problems with proxy-arp:
[B-1] IFACE: No interface to proxy arp on for 192.168.1.185
In googling for solutions, I came across others who have posted to this list
who have had similar problems. It also looks like a problem report has been
submitted for proxy arp being broken in 8.0 RELENG.
My options are 1) to wait until proxy arp is fixed (don't know how long that
will take), or 2) go back and implement my VPN using 7.2 (would require a
lot of effort). I was wondering if anyone else could suggest other
alternatives that would allow my external clients to access my intranet
without proxy arp.
------------------------------
Message: 7
Date: Tue, 30 Mar 2010 15:54:00 -0400
From: Boris Kochergin <sp...@acm.poly.edu>
Subject: Re: Workaround for mpd5 and 8.0 broken proxy arp?
To: "J. English" <j_en...@kawasaki-tn.com>
Cc: freeb...@freebsd.org
Message-ID: <4BB256D8...@acm.poly.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
J. English wrote:
> Hello All,
>
> I've recently set up a FreeBSD 8.0 VPN server with mpd5 for people to
> connect remotely. However, looking at my mpd.log shows that I'm having
> problems with proxy-arp:
> [B-1] IFACE: No interface to proxy arp on for 192.168.1.185
>
> In googling for solutions, I came across others who have posted to this list
> who have had similar problems. It also looks like a problem report has been
> submitted for proxy arp being broken in 8.0 RELENG.
>
> My options are 1) to wait until proxy arp is fixed (don't know how long that
> will take), or 2) go back and implement my VPN using 7.2 (would require a
> lot of effort). I was wondering if anyone else could suggest other
> alternatives that would allow my external clients to access my intranet
> without proxy arp.
>
How about a userspace implementation of proxy ARP, like the one in the
choparp/pkg-descr port?
-Boris
------------------------------
Message: 8
Date: Tue, 30 Mar 2010 15:54:54 -0400
From: Boris Kochergin <sp...@acm.poly.edu>
Subject: Re: Workaround for mpd5 and 8.0 broken proxy arp?
To: "J. English" <j_en...@kawasaki-tn.com>
Cc: freeb...@freebsd.org
Message-ID: <4BB2570E...@acm.poly.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Boris Kochergin wrote:
> J. English wrote:
>> Hello All,
>>
>> I've recently set up a FreeBSD 8.0 VPN server with mpd5 for people to
>> connect remotely. However, looking at my mpd.log shows that I'm having
>> problems with proxy-arp:
>> [B-1] IFACE: No interface to proxy arp on for 192.168.1.185
>>
>> In googling for solutions, I came across others who have posted to
>> this list
>> who have had similar problems. It also looks like a problem report
>> has been
>> submitted for proxy arp being broken in 8.0 RELENG.
>>
>> My options are 1) to wait until proxy arp is fixed (don't know how
>> long that
>> will take), or 2) go back and implement my VPN using 7.2 (would
>> require a
>> lot of effort). I was wondering if anyone else could suggest other
>> alternatives that would allow my external clients to access my intranet
>> without proxy arp.
>>
> How about a userspace implementation of proxy ARP, like the one in the
> choparp/pkg-descr port?
>
> -Boris
>
Oops. I meant the net-mgmt/choparp port.
-Boris
------------------------------
Message: 9
Date: Tue, 30 Mar 2010 17:20:52 -0400
From: Mike Tancsa <mi...@sentex.net>
Subject: Re: Workaround for mpd5 and 8.0 broken proxy arp?
To: "J. English" <j_en...@kawasaki-tn.com>,
<freeb...@freebsd.org>
Message-ID: <201003302120....@lava.sentex.ca>
Content-Type: text/plain; charset="us-ascii"; format=flowed
At 03:08 PM 3/30/2010, J. English wrote:
>In googling for solutions, I came across others who have posted to this list
>who have had similar problems. It also looks like a problem report has been
>submitted for proxy arp being broken in 8.0 RELENG.
>My options are 1) to wait until proxy arp is fixed (don't know how long that
>will take),
Are you sure its still broken in RELENG_8 ? There were a couple of
fixes since 8.0 that have gone into the tree if I recall correctly.
http://svn.freebsd.org/viewvc/base?view=revision&revision=201614
http://lists.freebsd.org/pipermail/svn-src-stable-8/2010-March/001790.html
---Mike
>_______________________________________________
>freeb...@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-net
>To unsubscribe, send any mail to "freebsd-net...@freebsd.org"
--------------------------------------------------------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, mi...@sentex.net
Providing Internet since 1994 www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
------------------------------
Message: 10
Date: Wed, 31 Mar 2010 04:48:23 +0400
From: Ruslan Ermilov <r...@FreeBSD.org>
Subject: Re: Workaround for mpd5 and 8.0 broken proxy arp?
To: Mike Tancsa <mi...@sentex.net>
Cc: "J. English" <j_en...@kawasaki-tn.com>, freeb...@freebsd.org
Message-ID: <20100331004...@edoofus.dev.vega.ru>
Content-Type: text/plain; charset=us-ascii
On Tue, Mar 30, 2010 at 05:20:52PM -0400, Mike Tancsa wrote:
> At 03:08 PM 3/30/2010, J. English wrote:
> >In googling for solutions, I came across others who have posted to this list
> >who have had similar problems. It also looks like a problem report has been
> >submitted for proxy arp being broken in 8.0 RELENG.
>
> >My options are 1) to wait until proxy arp is fixed (don't know how long that
> >will take),
>
> Are you sure its still broken in RELENG_8 ? There were a couple of
> fixes since 8.0 that have gone into the tree if I recall correctly.
>
> http://svn.freebsd.org/viewvc/base?view=revision&revision=201614
>
> http://lists.freebsd.org/pipermail/svn-src-stable-8/2010-March/001790.html
Yes, it's still broken (it's a regression compared to 7.x). A
workaround I've found working after analyzing the newer kernel
code is to ALWAYS use the same IP address for the local end of
the tunnel as of the corresponding ARP capable interface.
Cheers,
--
Ruslan Ermilov
r...@FreeBSD.org
FreeBSD committer
------------------------------
Message: 11
Date: Tue, 30 Mar 2010 18:25:48 -0700
From: "Li, Qing" <qin...@bluecoat.com>
Subject: RE: Workaround for mpd5 and 8.0 broken proxy arp?
To: "Ruslan Ermilov" <r...@freebsd.org>, "Mike Tancsa" <mi...@sentex.net>
Cc: "J. English" <j_en...@kawasaki-tn.com>, freeb...@freebsd.org
Message-ID:
<B583FBF374231F4A8960...@bcs-mail03.internal.cacheflow.com>
Content-Type: text/plain; charset="us-ascii"
>
> Yes, it's still broken (it's a regression compared to 7.x). A
> workaround I've found working after analyzing the newer kernel
> code is to ALWAYS use the same IP address for the local end of
> the tunnel as of the corresponding ARP capable interface.
>
Are you using VLANs?
Were you getting the following error message?
"cannot intuit interface index and type for x.x.x.x"
Could you please revert back to your original configuration
and give the following patch try (in addition to the patches
mentioned by Mike) ?
http://people.freebsd.org/~qingli/mpd-patch.diff
Thanks,
-- Qing
------------------------------
Message: 12
Date: Wed, 31 Mar 2010 15:34:52 +0400
From: Evgenii Davidov <da...@korolev-net.ru>
Subject: Re: kern/144564: lltable grows too much
To: Kevin Day <toa...@dragondata.com>
Cc: freeb...@freebsd.org, bug-fo...@FreeBSD.org
Message-ID: <20100331113...@korolev-net.ru>
Content-Type: text/plain; charset=koi8-r
Здравствуйте,
On Sun, Mar 28, 2010 at 12:34:42PM -0500, Kevin Day пишет:
> This patch also corrected a long-standing bug we were running into on our public 6to4 relay that would cause llentry to grow over time until we hit the limit. I've been testing it for 5 days now with moderate load (>50mbps, 3kpps) including all sorts of junk traffic to invalid destinations, and there doesn't seem to be a leak now.
yesterday i cvsuped to RELENG_8
and tried the patch
as i could see the problem with lltable was fixed by the patch
but some of other stuff was broken, i saw some new messages:
Mar 31 00:33:04 i1 kernel: ip_dn_ctl dummynet: compat option 60
Mar 31 00:33:04 i1 kernel: ip_dummynet_compat setting compatibility with FreeBSD 8
Mar 31 01:49:10 i1 kernel: in_cksum_skip: out of data by 38505
Mar 31 09:02:46 i1 kernel: ipfw: ouch!, skip past end of rules, denying packet
and some ip-addresses in vlanes was not working
so i rebooted to the old kernel
it may be somthing with ipfw in RELENG_8
maybe i could test the patch with RELENG_8_0 but list time i tried it there was a mpd error like "ifa_add_loopback_route: insertion failed" i tried it on march 12 and don't kown is it fixed..
--
Evgenii V Davidov
------------------------------
Message: 13
Date: Wed, 31 Mar 2010 15:34:32 +0400
From: Ruslan Ermilov <r...@freebsd.org>
Subject: Re: Workaround for mpd5 and 8.0 broken proxy arp?
To: "Li, Qing" <qin...@bluecoat.com>
Cc: "J. English" <j_en...@kawasaki-tn.com>, freeb...@freebsd.org,
Mike Tancsa <mi...@sentex.net>
Message-ID: <20100331113...@edoofus.dev.vega.ru>
Content-Type: text/plain; charset=us-ascii
On Tue, Mar 30, 2010 at 06:25:48PM -0700, Li, Qing wrote:
> > Yes, it's still broken (it's a regression compared to 7.x). A
> > workaround I've found working after analyzing the newer kernel
> > code is to ALWAYS use the same IP address for the local end of
> > the tunnel as of the corresponding ARP capable interface.
> >
>
> Are you using VLANs?
Yes, we do.
> Were you getting the following error message?
> "cannot intuit interface index and type for x.x.x.x"
>
> Could you please revert back to your original configuration
> and give the following patch try (in addition to the patches
> mentioned by Mike) ?
>
> http://people.freebsd.org/~qingli/mpd-patch.diff
I'll give it a try in the next few days, and let you know.
Cheers,
--
Ruslan Ermilov
r...@FreeBSD.org
FreeBSD committer
------------------------------
End of freebsd-net Digest, Vol 365, Issue 3
*******************************************