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. bin/142547: wpa_supplicant(8) drops connection on key
renegotiation (Eugeny N Dzhurinsky)
2. Re: Poor situation with snmp support in FreeBSD (Bruce Simpson)
3. Re: NFS lockd problem (Chuck Swiger)
4. Re: bin/142547: wpa_supplicant(8) drops connection on key
renegotiation (bsch...@FreeBSD.org)
5. Re: Poor situation with snmp support in FreeBSD
(alexpali...@yahoo.com)
6. Re: NFS lockd problem (Ronald Klop)
7. Re: NFS lockd problem (Ronald Klop)
----------------------------------------------------------------------
Message: 1
Date: Sat, 27 Mar 2010 15:10:03 GMT
From: Eugeny N Dzhurinsky <bo...@redwerk.com>
Subject: bin/142547: wpa_supplicant(8) drops connection on key
renegotiation
To: freeb...@FreeBSD.org
Message-ID: <201003271510....@freefall.freebsd.org>
The following reply was made to PR bin/142547; it has been noted by GNATS.
From: Eugeny N Dzhurinsky <bo...@redwerk.com>
To: bug-fo...@FreeBSD.org, sweetpea...@tentacle.net
Cc:
Subject: bin/142547: wpa_supplicant(8) drops connection on key renegotiation
Date: Sat, 27 Mar 2010 17:01:17 +0200
Hello!
I'm not sure, but the problem with wpa_supplicant occurs on FreeBSD 8.0 stable
with recent sources. The problem occurs only with if_ath driver (with if_rum
no such problem occurs).
The symptoms are - no network packets are transferred after group key
renegotiation occurs. restarting wpa_supplicant helps.
The only workaround I found for now is to setup AP with wpa_group_rekey=1800
--
Eugene N Dzhurinsky
------------------------------
Message: 2
Date: Sat, 27 Mar 2010 15:51:22 +0000
From: Bruce Simpson <b...@incunabulum.net>
Subject: Re: Poor situation with snmp support in FreeBSD
To: freeb...@freebsd.org
Message-ID: <4BAE297A...@incunabulum.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 03/26/10 04:58, Alexander Bubnov wrote:
> Hello Harti and freebsd-net maillist!
> One more question please in scope of snmp topic. does bsnmp support master
> agentx mode?
>
I totally agree that would be a good way to go, but it's a case of
someone having time to sit down and finish things off properly.
(Unfortunately stuff on my plate mostly doesn't involve FreeBSD these
days...)
But agentx does have pluggability that other access modes don't, and it
is probably the right fix for other stuff I look at.
------------------------------
Message: 3
Date: Sat, 27 Mar 2010 11:50:17 -0700
From: Chuck Swiger <csw...@mac.com>
Subject: Re: NFS lockd problem
To: Giulio Ferro <au...@zirakzigil.org>
Cc: "freeb...@freebsd.org" <freeb...@freebsd.org>,
freebsd...@freebsd.org
Message-ID: <4931283F-5B5B-4368...@mac.com>
Content-Type: text/plain; charset=us-ascii
On Mar 26, 2010, at 3:08 AM, Giulio Ferro wrote:
> Outset:
> 1 NFS server (with lockd)
> 2 NFS client (with lockd)
>
> The clients serve several jails with apache, whose data (www) resides on the server
If you need file locking to work reliably, you pretty much have to give up on using NFS + rpc.lockd and run against a local UFS filesystem.
Regards,
--
-Chuck
------------------------------
Message: 4
Date: Sat, 27 Mar 2010 19:49:25 GMT
From: bsch...@FreeBSD.org
Subject: Re: bin/142547: wpa_supplicant(8) drops connection on key
renegotiation
To: sweetpea...@tentacle.net, bsch...@FreeBSD.org,
freeb...@FreeBSD.org, bsch...@FreeBSD.org
Message-ID: <201003271949....@freefall.freebsd.org>
Synopsis: wpa_supplicant(8) drops connection on key renegotiation
State-Changed-From-To: closed->feedback
State-Changed-By: bschmidt
State-Changed-When: Sat Mar 27 19:45:40 UTC 2010
State-Changed-Why:
Are you sure this is related to wpa_group_rekey?
I do have a setup running with wpa_group_rekey=20 and both AP and STA are
ath(4). Can you reproduce this issue with
wlandebug +crypto +state
?
Responsible-Changed-From-To: freebsd-net->bschmidt
Responsible-Changed-By: bschmidt
Responsible-Changed-When: Sat Mar 27 19:45:40 UTC 2010
Responsible-Changed-Why:
Are you sure this is related to wpa_group_rekey?
I do have a setup running with wpa_group_rekey=20 and both AP and STA are
ath(4). Can you reproduce this issue with
wlandebug +crypto +state
?
http://www.freebsd.org/cgi/query-pr.cgi?pr=142547
------------------------------
Message: 5
Date: Sat, 27 Mar 2010 17:42:27 -0700 (PDT)
From: alexpali...@yahoo.com
Subject: Re: Poor situation with snmp support in FreeBSD
To: Hartmut Brandt <hartmut...@dlr.de>, Vasily Samoylov
<ma...@vas.org.ua>
Cc: freeb...@freebsd.org, Shteryana Shopova <shte...@gmail.com>,
Harti Brandt <ha...@freebsd.org>, Ivan Voras <ivo...@freebsd.org>
Message-ID: <124901....@web56406.mail.re3.yahoo.com>
Content-Type: text/plain; charset=us-ascii
One thing that is not working as expected in bsnmpd (or maybe I'm not expecting the right thing) is replying to queries on multihomed hosts.
That is, if one machine has 2 network interfaces, one with IP address 192.168.1.1, mask 255.255.255.0 and another 10.10.10.10 (same mask), if a host on the 192.168 segment tries to query this host on its 10.10.10.10 IP address, it will receive a reply from 192.168.1.1 - which will be ignored, since it's not the host we tried to query.
Is this the normal behaviour?
Thank you
Alex Popa
------------------------------
Message: 6
Date: Sun, 28 Mar 2010 13:19:59 +0300
From: "Ronald Klop" <ronald-...@klop.yi.org>
Subject: Re: NFS lockd problem
To: "Giulio Ferro" <au...@zirakzigil.org>, "Chuck Swiger"
<csw...@mac.com>
Cc: "freeb...@freebsd.org" <freeb...@freebsd.org>,
freebsd...@freebsd.org
Message-ID: <op.u99y3lgt8527sy@pinky>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
On Sat, 27 Mar 2010 20:50:17 +0200, Chuck Swiger <csw...@mac.com> wrote:
> On Mar 26, 2010, at 3:08 AM, Giulio Ferro wrote:
>> Outset:
>> 1 NFS server (with lockd)
>> 2 NFS client (with lockd)
>>
>> The clients serve several jails with apache, whose data (www) resides
>> on the server
>
> If you need file locking to work reliably, you pretty much have to give
> up on using NFS + rpc.lockd and run against a local UFS filesystem.
I don't have this experience. I use NFS locking between FreeBSD, Linux,
NetApp and SUN stuff. Older versions of FreeBSD had some troubles, but
more recent ones work very well.
Ronald.
------------------------------
Message: 7
Date: Sun, 28 Mar 2010 13:24:23 +0300
From: "Ronald Klop" <ronald-...@klop.yi.org>
Subject: Re: NFS lockd problem
To: "freeb...@freebsd.org" <freeb...@freebsd.org>,
freebsd...@freebsd.org, "Giulio Ferro" <au...@zirakzigil.org>
Message-ID: <op.u99zaxmh8527sy@pinky>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
On Fri, 26 Mar 2010 12:08:26 +0200, Giulio Ferro <au...@zirakzigil.org>
wrote:
> Outset:
> 1 NFS server (with lockd)
> 2 NFS client (with lockd)
>
> The clients serve several jails with apache, whose data (www) resides on
> the server
>
> From time to time everything seem to freeze. Then, after one minute or
> so, the system
> works again as nothing had happened.
>
> In these occasions I get this in the logs on the client madchines:
> Mar 26 10:29:38 virt1 kernel: nfs server
> 192.168.40.121:/data/mount_servers/wwwsec/www: lockd not responding
>
> followed shortly after by:
>
> Mar 26 10:29:38 virt1 kernel: nfs server
> 192.168.40.121:/data/mount_servers/wwwsec/www: lockd is alive again
>
>
> On the server I only get this:
> Mar 26 10:29:31 data1 kernel: NLM: failed to contact remote rpcbind,
> stat = 5, port = 28416
>
> I don't think it's a network problem, since all connections are local
> and high speed (1Gb/s)
>
> I must admit that, with the other nfs problem I reported weeks ago, this
> kind of freebsd system seems
> less than stable to me, and this is very disappointing...
>
> Anyway I'd appreciate any pointer on this issue...
I'm no NFS expert, so I don't know if I can help, but regularly people
want to know your FreeBSD version(s), your used NFS version, if you are
running NFS over TCP or UDP. Does it help to switch between UDP/TCP?
Ronald.
------------------------------
End of freebsd-net Digest, Vol 364, Issue 7
*******************************************