On Fri, 14 Jan 2011, Bernhard Schmidt wrote:
On Friday 14 January 2011 15:40:18 Dennis Glatting wrote:
I forgot to mention an important data point. I see via WireShark the
EAPOL from the supplicant to the server and the server requesting
identity but the supplicant doesn't appear to see the r
On Friday 14 January 2011 15:40:18 Dennis Glatting wrote:
> I forgot to mention an important data point. I see via WireShark the
> EAPOL from the supplicant to the server and the server requesting
> identity but the supplicant doesn't appear to see the request.
Which FreeBSD version are you runnin
From: Dennis Glatting
To: freebsd-net@freebsd.org
Subject: Looking for hints re 802.1X wired
I am trouble with 802.1x wired and I am wondering whether there is some
required characteristic of the Ethernet driver. AFAICT, I have my
wap_supplicant running correctly and I do have wireless interfaces
I am trouble with 802.1x wired and I am wondering whether there is some
required characteristic of the Ethernet driver. AFAICT, I have my
wap_supplicant running correctly and I do have wireless interfaces that
work both AP and supplicant.
My Ethernet is:
Bart# dmesg|grep em0
em0: port 0x4
Hello.
Sam Leffler wrote:
Are you certain it's that revision? Have you tried r189931 which
worked around certain problems in the initial commit?
Yes, problem still here.
Can you provide sufficient info to reproduce your problem? Filing a
PR for reference is likely the best thing to do.
ok.
Hello again.
Bruce Simpson wrote:
General questions:
Are you running any routing protocols on this machine, or anything
which opens a multicast socket at system startup?
No, any it is a simple work notebook. May be it avahi or hald
starts something, but i think they isn't.
Do you have m
Hi,
Based on the backtrace you've provided, this doesn't seem like a
multicast related issue.
I skimmed wpa_supplicant and I see that whilst it requests a link-layer
multicast address, it does not use IPv4 multicast.
Vany Serezhkin wrote:
Hello.
I do not really sure in this, but :
after t
Vany Serezhkin wrote:
Hello.
I do not really sure in this, but :
after the current updated to
20090309 Merge IGMPv3 and Source-Specific Multicast (SSM) to the FreeBSD
IPv4 stack.
I can't use any wpa_supplicant related networks.
It faulted in any WPA authentications , that i tried.
Also it fa
On Wed, Apr 09, 2008 at 01:43:07PM -0700, Sam Leffler wrote:
>
> I believe it's done w/ bpf and the important change for wired support was
> to accept mcast frames from the PAE mcast address. Like I said to you
> privately; you might try this on releng7 where it was tested by someone.
I debuge
Guido van Rooij wrote:
On Wed, Apr 09, 2008 at 09:58:31PM +0200, Guido van Rooij wrote:
wpa_supplicant send a EAPOL start (version 1, type start)
procurve sends EAP failure (version 1, type: eap packet (code failure, id: 2)
procurve send EAP request identify (veersion 1, type: eap packet (cod
On Wed, Apr 09, 2008 at 09:58:31PM +0200, Guido van Rooij wrote:
>
> wpa_supplicant send a EAPOL start (version 1, type start)
> procurve sends EAP failure (version 1, type: eap packet (code failure, id: 2)
> procurve send EAP request identify (veersion 1, type: eap packet (code:
> request
> type
On Wed, Apr 09, 2008 at 09:11:05AM -0700, Sam Leffler wrote:
> Brooks Davis wrote:
>> On Wed, Apr 09, 2008 at 03:05:31PM +0200, Guido van Rooij wrote:
>>> What is the best way to be able to have a FreeBSD system connect
>>> via 802.1x to a wired network? Wap_supplicant seems to insist on
>>> calli
Brooks Davis wrote:
On Wed, Apr 09, 2008 at 03:05:31PM +0200, Guido van Rooij wrote:
What is the best way to be able to have a FreeBSD system connect
via 802.1x to a wired network? Wap_supplicant seems to insist on
calling 80211 ioctl's and thus fails.
I found the open1x project, but did not f
On Wed, Apr 09, 2008 at 03:05:31PM +0200, Guido van Rooij wrote:
> What is the best way to be able to have a FreeBSD system connect
> via 802.1x to a wired network? Wap_supplicant seems to insist on
> calling 80211 ioctl's and thus fails.
>
> I found the open1x project, but did not find it in the
Marco Molteni wrote:
On Thu, 20 May 2004 11:20:27 +1000
Phillip Crumpler <[EMAIL PROTECTED]> wrote:
[..]
I need a neat and tidy way of notifying either a netgraph node or a
user process about associations.
[..]
You did search the archives, did you? ;-)
Have a look at the following thread:
h
On Thu, 20 May 2004 Sam Leffler <[EMAIL PROTECTED]> wrote:
[..]
> I pointed him at the madwifi project on sourceforge. It's a Linux
> port of the net80211 layer that now includes an 802.1x authenticator
> and soon will have WPA support too. Backporting to FreeBSD should be
> straightforward.
S
On Thursday 20 May 2004 02:17 am, Marco Molteni wrote:
> On Thu, 20 May 2004 11:20:27 +1000
> Phillip Crumpler <[EMAIL PROTECTED]> wrote:
>
> [..]
>
> > I need a neat and tidy way of notifying either a netgraph node or a
> > user process about associations.
>
> [..]
>
> You did search the archives,
On Thu, 20 May 2004 11:20:27 +1000
Phillip Crumpler <[EMAIL PROTECTED]> wrote:
[..]
> I need a neat and tidy way of notifying either a netgraph node or a
> user process about associations.
[..]
You did search the archives, did you? ;-)
Have a look at the following thread:
http://docs.FreeBSD.o
jeremie le-hen wrote:
However, I fight with 802.1x under FreeBSD. I know Pekka Nikander worked on an
802.1x implementation under FreeBSD (see [1]), but I wasn't able to make it
work with a FreeRadius server.
My 802.1x implementation is still lacking quite a lot,
especially at the user space side
An option that was very recently pointed out to me:
http://www.open1x.org/
I have yet to play with it (lack of time). The readme does say that
BSD support is not yet complete so I don't know how much help this is
to you.
DaveD
On Monday, November 25, 2002, at 07:36 PM, jeremie le-hen wrot
20 matches
Mail list logo
