Synopsis: FreeBSD 8.0-beta3 wpa_supplicant(8) lost auth
Responsible-Changed-From-To: freebsd-net->sam
Responsible-Changed-By: sam
Responsible-Changed-When: Sun Aug 30 19:03:26 UTC 2009
Responsible-Changed-Why:
I'll handle this
http://www.freebsd.org/cgi/query-pr.cgi?p
Hi,
Is this problem still happening?
Cheers
Sam
On 24/01/2010 2:16 PM, Sherin George wrote:
Hello,
I am facing some sort of strange network issue in a freebsd server
occasionally.
OS: FreeBSD 8.0-RELEASE - amd64
Now, I have updated to FreeBSD 8.0-RELEASE-p2
The servers loses network
that s why I 've been so in doubt using freebsd AMD64 release.
On 28/01/2010 1:05 PM, Sherin George wrote:
Hello Sam,
The problem happened today again.
I am getting this message on traceroute
===
traceroute: findsaddr: write: No such process
When running a
Can you incorporate its protocol into freebsd kernel? it is currently
applicable to freebsd 4.4. See below.
http://www.cs.ucla.edu/NRL/hpi/tcpw/implementation.html
On 1/02/2010 9:49 AM, Jerry Toung wrote:
Hello list,
my employer is asking me to implement westwood, this is most likely happen
Synopsis: [vap] second hostap interface (wlan1) unable to send traffic
Responsible-Changed-From-To: freebsd-net->sam
Responsible-Changed-By: sam
Responsible-Changed-When: Thu Jul 24 05:21:31 UTC 2008
Responsible-Changed-Why:
I promised to look at this
http://www.freebsd.org/cgi/query-pr.cgi
Synopsis: [ath] [panic] ath driver causes kernel panic in 7-STABLE
State-Changed-From-To: open->feedback
State-Changed-By: sam
State-Changed-When: Thu Jul 24 05:22:10 UTC 2008
State-Changed-Why:
need network setup information and information on how to reproduce
the problem
The line num
The following reply was made to PR kern/124127; it has been noted by GNATS.
From: sam <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc:
Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) --
recovering
Date: Thu, 31 Jul 2008 16:00:19
Synopsis: [ath] ath cannot connect using WEP
Responsible-Changed-From-To: freebsd-net->sam
Responsible-Changed-By: sam
Responsible-Changed-When: Fri Nov 28 18:13:53 UTC 2008
Responsible-Changed-Why:
didn't know this existed; will check
http://www.freebsd.org/cgi/query-pr.cgi?p
Synopsis: [lagg] [wlan] lagg with wlan laggpport does not work
Responsible-Changed-From-To: freebsd-net->sam
Responsible-Changed-By: sam
Responsible-Changed-When: Sun Mar 29 17:19:47 UTC 2009
Responsible-Changed-Why:
take responsibility
http://www.freebsd.org/cgi/query-pr.cgi?pr=133
Synopsis: [lagg] [panic] Panic when creating vlan's on lagg interface
Responsible-Changed-From-To: freebsd-net->jfv
Responsible-Changed-By: sam
Responsible-Changed-When: Thu Jul 9 15:22:48 UTC 2009
Responsible-Changed-Why:
this is really a driver issue
http://www.freebsd.org/cgi/query-p
Synopsis: [ath]: High wireless traffic on ATH causes high tx failed 'cuz FIFO
underrun
Responsible-Changed-From-To: freebsd-net->sam
Responsible-Changed-By: sam
Responsible-Changed-When: Mon Feb 25 17:18:49 UTC 2008
Responsible-Changed-Why:
assign to the correct person
http://www.fre
Synopsis: [ath] [panic] panic while ejecting ath(4)-adapter during shutdown
Responsible-Changed-From-To: freebsd-net->sam
Responsible-Changed-By: sam
Responsible-Changed-When: Mon Feb 25 17:19:23 UTC 2008
Responsible-Changed-Why:
assign to the correct person
http://www.freebsd.org/cgi/qu
Synopsis: [wpi] wpi doesnt work if kernel has options SCHED_ULE
Responsible-Changed-From-To: freebsd-net->thompsa
Responsible-Changed-By: sam
Responsible-Changed-When: Tue Mar 18 21:54:31 UTC 2008
Responsible-Changed-Why:
Hand to Andrew as he's been working on this driver.
FWIW my guess
Synopsis: [ath] [panic] kernel panic during network activity on ath0
State-Changed-From-To: open->feedback
State-Changed-By: sam
State-Changed-When: Fri May 9 17:10:24 UTC 2008
State-Changed-Why:
need system and network configuration at a minimum
Responsible-Changed-From-To: freebsd-net-&
The following reply was made to PR kern/157410; it has been noted by GNATS.
From: Sam Bowne
To: bug-follo...@freebsd.org
Cc:
Subject: Re: kern/157410: [ip6] IPv6 Router Advertisements Cause Excessive CPU
Use
Date: Mon, 30 May 2011 19:16:20 -0700
--bcaec51a7ff262ecc004a488fdf6
Content-Type
The following reply was made to PR bin/138331; it has been noted by GNATS.
From: Sam Leffler
To: bug-follo...@freebsd.org, sshutdow...@gmail.com
Cc:
Subject: Re: bin/138331: FreeBSD 8.0-beta3 wpa_supplicant(8) lost auth
Date: Sun, 30 Aug 2009 10:28:47 -0700
You appear to say this problem
5 protmode CTS burst hidessid dtimperiod 1
In ap mode you should not manually configure preamble; it should be
selected according to the associated stations. What are you trying to
accomplish?
Sam
___
freebsd-net@freebsd.org mailing list
h
or
both stations are in power save mode and there's a bug in the RELENG_7
ap support; wlandebug +power might help for that.
I can look at adding a knob to force short/long preamble. It would go
into HEAD though and can't promise to backport to RELENG_7.
Sam
Sin wrote:
Sam,
ath/Makefile). Please file a PR if this does not work.
Sam
___
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"
he OFDM speed at
>> which traffic flows best.
>
> May be do you know why I'm getting normal speed (2Mb/s) for some time
> after using "ifconfig bssid ..." command only?
When you set the bssid you reset the state o
I believe this issue is purely cosmetic in that you see 0's in the scan
results display. If you want to fill that data in with something be my
guest but unless the values correspond to the data actually used to make
decision it's just going to cause confusion. It might be simpler
Denis Shaposhnikov wrote:
> Hello,
>
> On Thu, 24 Sep 2009 19:46:41 -0700
> Sam Leffler wrote:
>
>>> May be do you know why I'm getting normal speed (2Mb/s) for some
>>> time after using "ifconfig bssid ..." command only?
>> When you set the
Stef Walter wrote:
> Denis Shaposhnikov wrote:
>> Hello,
>>
>> On Thu, 24 Sep 2009 19:46:41 -0700
>> Sam Leffler wrote:
>>
>>>> May be do you know why I'm getting normal speed (2Mb/s) for some
>>>> time after using "ifconfig bssi
I did got lost (don't see it in the tree).
Sam
___
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"
Hi,
This server is built with Xeon cpu processor, Intel based.
Can FreeBSD 8+ fully compatible with this server like those ordinary
Intel i386 machine?
Thanks
SW
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
major installation difference between AMD (64) and i386
release of FreeBSD (8.0)?
Thank you for your answers.
Sam
On Tue, Jan 12, 2010 at 10:05 AM, Gavin Atkinson wrote:
> On Mon, 11 Jan 2010, Sam Wun wrote:
>> This server is built with Xeon cpu processor, Intel based.
>> Can FreeBSD 8+ f
en we pull
* aggregation up into net80211
*/
Thanks.
What is unclear?
Sam
On Wed, Jan 27, 2010 at 8:04 PM, Alexander Egorenkov <
egore...@googlemail.com> wrote:
Hi,
i'm implementing a device driver for a 802.11n NIC under FreeBSD 8
und experimented with A-MPDU transmission. I look
x aggregation in h/w or in the driver.
Thanks.
On Sun, Jan 31, 2010 at 4:43 AM, Sam Leffler <mailto:s...@errno.com>> wrote:
Alexander Egorenkov wrote:
Sorry, i posted the wrong comment.
Here is the comment which i don't understand:
/*
great work.
Thanks
On Tue, Feb 2, 2010 at 3:46 PM, Li, Qing wrote:
> Just an update on this issue and to letting you know your
> report is not ignored.
>
> I have been working with Sherin George offline and we have
> Been pulling information off Sherin's server box.
>
> The box becomes unrespon
ok to add but probably
used only for testing.
Sam
___
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"
return 1;
}
Reseting this flag in setkey looks right but why only for group keys? I
don't think you want to reset the keyrsc unless instructed; if I recall
a new RSC may be sent down by the authenticator when plumbing a key--but
it's been a while since I looke
Alexander Egorenkov wrote:
On Sat, Feb 6, 2010 at 10:52 PM, Sam Leffler <mailto:s...@errno.com>> wrote:
The advertised rate set should be initially set according to the
capabilities of the device. There were no devices > 2x2 when I
wrote the code so MCS15 is the max.
gher rates things like TCP window sizes become important and
doing things like TSO in s/w can give noticeable speed boosts.
Sam
Alexander Egorenkov wrote:
Hi,
thanks for your help, I implemented A-MPDU Tx in my Ralink driver now
and it works very good.
I have average Tx rate about 4.5~
drivers now use it (or
should use it). I'll leave it to others to deal w/ the politics of the
radiotap noobs; the technical details of doing this are straightforward.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mai
is is old Broadcom code--at one point
Broadcom intentionally didn't advertise WME. If this is the legacy HT
stuff then perhaps we can add the auto-enable conditional on the legacy
HT support.
Sam
___
freebsd-net@freebsd.org mailing
always
welcome; what's there reflects what was needed for the projects I worked on.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-ne
api and generate
events/callbacks on changes. Last I looked doing this right was non-
trivial.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebs
Hi,
With FreeBSD 8.1 RC1,
Can anyone tell me how to resolve the following error from building cyrus-sasl2?
configure: creating ./config.status
autom4te --language=m4sh -B libltdl/config libltdl/config/ltmain.m4sh
> libltdl/config/ltmain.in
autom4te: not found
*** Error code 127
Stop in /usr/port
how to resolve this problem?
Your help is very much appreciated.
Thanks
Sam
___
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"
1
Stop in /usr/ports/lang/perl5.8/work/perl-5.8.9/ext/DynaLoader.
*** Error code 1
Stop in /usr/ports/lang/perl5.8/work/perl-5.8.9.
*** Error code 1
Stop in /usr/ports/lang/perl5.8.
*** Error code 1
Stop in /usr/ports/lang/perl5.8.
I have followed what it told and rerun make command, it still
ge
NAT-T
patches committed for a while but since I'm not setup to do any IPSEC
testing have deferred to others. If we need to break a logjam I'll
pitch in.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/f
or devices that are not capable is not a big deal and is important for
performance. TSO likewise should be done but we're missing a generic
TSO support routine to do that (I believe, netbsd has one and linux has
a GSO mechanism).
Sam
e there's something else wrong which (as you note) probably
requires a packet capture to understand. I'm pretty sure TIM is handled
correctly in RELENG_7 but a packet capture would help us verify that.
Sam
___
freebsd-net@freebsd.org mailing
Sam Leffler wrote:
Larry Baird wrote:
And how do I know that it works ?
Well, when it doesn't work, I do know it, quite quickly most of the
time !
I have to chime in here. I did most of the initial porting of the
NAT-T patches from Kame IPSec to FAST_IPSEC. I did look at every
li
Bjoern A. Zeeb wrote:
On Wed, 16 Jul 2008, Sam Leffler wrote:
Hi,
Please test/review the following patch against HEAD:
http://people.freebsd.org/~sam/nat_t-20080616.patch
This adds only the kernel portion of the NAT-T support; you must
provide the user-level code from another place.
The
VANHULLEBUS Yvan wrote:
On Mon, Jul 21, 2008 at 10:31:10AM +0200, VANHULLEBUS Yvan wrote:
On Wed, Jul 16, 2008 at 09:10:18PM -0700, Sam Leffler wrote:
[...]
Please test/review the following patch against HEAD:
http://people.freebsd.org/~sam/nat_t-20080616.patch
I have tested
VANHULLEBUS Yvan wrote:
[Larry, I kept you in an explicit CC, even if I guess you suscribed to
the list]
On Mon, Jul 21, 2008 at 09:26:15AM +, Bjoern A. Zeeb wrote:
On Wed, 16 Jul 2008, Sam Leffler wrote:
Hi,
Hi.
[...]
My main concern at the moment is the API (pfkey stuff
Bjoern A. Zeeb wrote:
On Mon, 21 Jul 2008, Sam Leffler wrote:
Hi Sam,
We are still missing other things I think not mentioned elswhere like
partial checksum recalculation.
Please send me your specific issues; I haven't seen any comments
about "partial checksum recalculations&q
VANHULLEBUS Yvan wrote:
On Mon, Jul 21, 2008 at 08:33:57AM -0700, Sam Leffler wrote:
VANHULLEBUS Yvan wrote:
[]
After some more testing, I found another issue: in udp4_espdecap(),
when payload <= sizeof(uint64_t) + sizeof(struct esp), packet should
not be discarded, but j
TU on an 802.11 network is 2290. If you don't want the default then
change it. If you cannot then please provide the exact steps you take
that do not work.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
Chris Buechler wrote:
Sam Leffler wrote:
John T. Yocum wrote:
Hello,
I have a system running pfSense, which is built on top of FreeBSD
7.0-RELEASE-p3. In the system I have an Atheros wireless card, which
when I enable hostap, changes it's MTU to 2290. If an explanation is
listed on
ore clear
what you're trying to setup.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
imagine anyone using it w/o some form of security. Having hostapd
handle this would also simplify configuration.
The integration work is straightforward and would be a good project for
someone trying to learn about the wireless facilities.
Sam
__
Without WDS you'll need to bridge/tunnel at a different layer.
Sam
David Cornejo wrote:
I have an existing AP that I have no control over (assume it doesn't
support WDS) sitting on a clinic LAN. I have a second LAN that I need
to bridge to the clinic LAN through a clien
ly apply a temporary bandaid (for lack of time,
etc.) hopefully later this can be reverted to something more efficient
such as pulling up the UDP header as well.
I agree that doing the deep copy is just papering over a bigger problem.
Sam
___
f
p. copy just the headers. no deep copy.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Luigi Rizzo wrote:
On Tue, Aug 26, 2008 at 05:56:13PM -0700, Sam Leffler wrote:
[EMAIL PROTECTED] wrote:
At Tue, 26 Aug 2008 14:50:33 + (UTC),
Bjoern A. Zeeb wrote:
On Tue, 26 Aug 2008, George V. Neville-Neil wrote:
Hi,
At Mon, 25 Aug 2008 21:40:38 +0200
Andrew Thompson wrote:
On Fri, Aug 29, 2008 at 06:41:45PM +0200, Luigi Rizzo wrote:
On Fri, Aug 29, 2008 at 09:32:10AM -0700, Sam Leffler wrote:
Luigi Rizzo wrote:
...
and to be more explicit - the result of m_pullup is that
the number of bytes specified as m_pullup
supported by any bsd driver I
know of. There's a linux driver of unknown quality that someone can use
to build a bsd driver but given how cheap wireless parts are your best
bet is to just replace the card.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7;t have a card so it may take a while to get
something out. Unfortunately it's not feasible for me to send out test
code to try until I can actually work w/ a card.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/m
There is no explicit STA capability in RELENG_7; it only exists in HEAD.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
enabled=0
bsd_set_iface_flags: dev_up=0
___
There is nothing unusual in the log. Your problems are likely lower;
e.g. loss of communication between the ap and sta.
Sam
___
freebsd-net@freebsd.org mailing list
h
deration
http://www.freebsd.org/cgi/query-pr.cgi?pr=128030
Last I checked IPSEC added noticeable overhead. Before anyone does this
you need to measure the cost of having it enabled but not used.
Sam
___
freebsd-net@freebsd.org mailing l
Max Laier wrote:
On Saturday 18 October 2008 19:05:26 Sam Leffler wrote:
[EMAIL PROTECTED] wrote:
Synopsis: [request] Isn't it time to enable IPsec in GENERIC?
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: gavin
Responsible-Changed-When: Sat O
b script
mechanisms (see ddb(4)).
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
stand his question but
trouble% vmstat -m |grep routetbl
routetbl14 2K -33875 16,32,64,128,256
should show memory allocated to the routing table.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
Mykel wrote:
Sam Leffler wrote:
Julian Elischer wrote:
Mykel wrote:
Got a few 6.x machines running OpenBGPd with a few BGP full-feeds and a
handful of peers... I'd like to determine the size of the FIB/kernel
routing table. OpenBGPd does not give me this data, and on my
du
uch older hal and lacks support for many cards. I
recommend using HEAD if wireless support is important to you. No ETA on
an update by me--others are welcome to supply the changes.
All ath cards support all features you listed (except for the 5210 which
Wes Morgan wrote:
On Mon, 15 Dec 2008, Sam Leffler wrote:
Lev Serebryakov wrote:
Hello, All.
`man ath' on FreeBSD 7.1-PRE speaks only about WPA2 in AR5212 and
not-supported AR5005VL. But in "current" cars here are many other
chipsets -- 5213A, 5414, etc... And Atheros s
tions you might consider asking the
freebsd-questions list.
There's also a section in the handbook that talks about setting up
wireless network configs.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
proper TLV-style protocol
and support for features like filtering.
Sam
harti
-Kip
On Sat, Dec 20, 2008 at 9:01 PM, Gerald Pfeifer
wrote:
The code in question on the Wine side is
#if defined(HAVE_SYS_SYSCTL_H) && defined(NET_RT_DUMP)
int mib[] = {CTL_NET, PF_ROUTE, 0, AF_
pt an incompatibility or put back sufficient
compatibility to enable legacy code to work unchanged.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-ne
rrect way is to
/sbin/ifconfig vlan3653 destroy
before unloading the driver.
Angelo.
Thanks, I didn't know freebsd does not allow it.
This seems wrong. Someone should disallow the driver detach/unload.
Please file a PR about this so the issue is not l
Jack Vogel wrote:
On Wed, Jan 7, 2009 at 9:54 AM, Sam Leffler <mailto:s...@freebsd.org>> wrote:
Yony Yossef wrote:
Yony Yossef wrote:
/sbin/ifconfig vlan3653 create
Problem is when I assign an IP to the vlan
alid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:3
The only thing I can think of is that the AP is using some feature that
the iwi driver, or wpa_supplicant, doesn't support.
Is there someway to get this working?
You don't indicate a freebsd version.
Lev Serebryakov wrote:
Hello, Freebsd-net.
I'm getting this error on every operation with new Atheros MiniPCI
card:
ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x490 hal flags
0x150), hal status 12
status 12 is:
HAL_EINVAL = 12, /* Invalid parameter to f
Your panic on card eject has been fixed in HEAD. That was one of the
changes I hoped to backport to RELENG_7 after the hal is brought back.
Sam
Adam K Kirchhoff wrote:
I get similar errors, but only when trying to connect to a particular
wireless network (at work). I can connect to the
s 25 years of userland code expecting
the tcp headers in netinet/ and moving them would be a
nightmare for ports...)
I think sctp belongs in it's own directory.
I'd vote for just ipfw; the "2" was an artifact of previous code.
Sam
_
This patches avoids the crash. Not sure how ifma_protospec is supposed
to be handled so I'm not committing it.
Sam
Index: in.c
===
--- in.c(revision 189750)
+++ in.c(working copy)
@@ -1040,7 +1
this stuff is supposed to work; it should be clear from comments etc but
the code is lacking.
Sam
Coleman Kane wrote:
The crash that I am seeing (using if_ndis) occurs in igmp_fasttimo...
This patch doesn't fix that, I'll get more info as soon as I can.
On Sat, 2009-03-14 at 1
ks fine in general,
i.e. with the AP in my office (WPA) and in my home (WEP);
Is this an ASUS Eee PC? If so, which model is it? It looks like a 901.
It is an Asus EeePC 900, not the 901.
I tested OK with the 701. Sam said that there may be models of
ath(4) requiring further changes to be b
e found the symptom, but the root cause I don't fully
understand.
Sam indicated that the VAP code is using ifma's in some nested way
between
the ifnets which comprise the VAP's member interfaces.
A workaround is pending
net80211 uses the public api's to push mcast ad
The following reply was made to PR kern/132722; it has been noted by GNATS.
From: Sam Leffler
To: "Sean C. Farley"
Cc: Matthias Apitz ,
Matthias Apitz , freebsd-net@freebsd.org,
Bruce Simpson , bug-follo...@freebsd.org
Subject: Re: kern/132722: [ath] Wifi ath0 assoc
.
If one argues that ifconfig should be consistent in it's treatment of
module loading then the patch is fine and should go in. Otherwise...
Sam
___
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"
Matthias Apitz wrote:
El día Tuesday, March 17, 2009 a las 11:56:24AM -0700, Sam Leffler escribió:
His setup is static key wep; not wpa so I don't think wpa_supplicant is
the issue.
Matthias, your tcpdump of the dhclient packets isn't usable; please try:
tcpdump -i
Are you certain it's that revision? Have you tried r189931 which worked
around certain problems in the initial commit?
Can you provide sufficient info to reproduce your problem? Filing a PR
for reference is likely the best thing to do.
Sam
___
Matthias Apitz wrote:
El día Thursday, March 19, 2009 a las 08:44:29AM -0700, Sam Leffler escribió:
Matthias Apitz wrote:
El día Tuesday, March 17, 2009 a las 11:56:24AM -0700, Sam Leffler
escribió:
His setup is static key wep; not wpa so I don't think wpa_supplica
rs_flags'
> *** Error code 1
>
>
>
>
Read UPDATING; you need options AH_SUPPORT_AR5416 in your config file.
Sam
___
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"
x27;m out of ideas. About the only thing I can suggest is you setup a
different ap w/ the same wep key and see if things work. If so then you
know it's something this ap is doing. I can't recall when I last tested
wep on HEAD but I'm pretty sure it works. I wil
initial boot
(including dhcp and anything we bump into).
There are many issues with the wireless code in RELENG_7. Now that the
hal is merged we can try to address them. Unfortunately the 7.2 release
has just begun so it's unclear what we can get in. I'm also l
The following reply was made to PR kern/132722; it has been noted by GNATS.
From: Sam Leffler
To: Matthias Apitz
Cc: bug-follo...@freebsd.org, freebsd-net@freebsd.org
Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP
or IP does not work
Date: Mon, 23 Mar 2009 12:12:04
Bruce M Simpson wrote:
Sam Leffler wrote:
Bruce M Simpson wrote:
...
This may be orthogonal, but:
A lab colleague and I have been seeing a sporadic problem where
the ath0 exhibits the symptoms of being disassociated from its AP.
We are running RELENG_7 on the EeePC 701 since the open
Sam Leffler wrote:
> You or someone else can do likewise but given things
> have sat basically untouched since 7.0RC1 I suspect that's expecting too
> much.
Sorry, this wasn't directed at you; it was meant at the community as a
whole. I don't run RELENG_7 and when I do
ts though they've
done a bunch of work to make it more production-quality.
Note that wds is implemented above the drivers (modulo a bit of glue
code). ath is just one driver that supports wds, ral is another.
Sam
___
freebsd-net@freebsd.org ma
stem would depend on
how much of a win it turns out to be and how intrusive it is as you'd
need to mod all the drivers.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send
It must be the bssid of the peer; it is used to form the 4-address frames.
Sam
David Cornejo wrote:
That brief description was a big help in itself, thank you.
One question: should the BSSID in the legacy mode be the same as the
MAC address of the main WDS node? Or can it be a random
mods
are straightforward but both of us have 4965 cards so can't test the new
stuff. I suggest you not wait if you're motivated.
Sam
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubs
ou why you
cannot associate. You can also enable the same info on the ap side to
see what it thinks is happening.
Sam
___
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"
Sam Leffler wrote:
Boris Kochergin wrote:
Ahoy. I'm having trouble with multiple hostap-mode wlan
pseudo-devices. The machine is an 8-CURRENT from yesterday:
# uname -a
FreeBSD test 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Tue Apr 7 16:54:56
UTC 2009 r...@test:/usr/obj/usr/src/sys/GE
lly need to allocate tags separately when they are
attached at a later time. For embedded/inline mbuf tag space management
I think m_tag_free and m_tag_copy would sufficient for current usage.
Sam
___
freebsd-net@freebsd.org mailing list
http://li
1 - 100 of 309 matches
Mail list logo
