Re: portsnap mirror servers
Hello, On Wed, Apr 19, 2006 at 01:28:56AM +0100, Chris wrote: > On 18/04/06, Colin Percival <[EMAIL PROTECTED]> wrote: > > Why do you think there should be an .eu mirror? > > Whilst portsnap is fast, it is a noticeable speed difference when > using from eu servers, I also think its a good idea for redundancy. I did not yet check in the sources or with tcpdump, but from the htrougput I see, I'd guess, there's a lot of sequential two-way communication involved. That kind of traffic is massively influenced by latency. While most sites in europe are reachable for me with a latency of 15-30ms, I have between 120 and 200 ms to most sites across the atlantic. Maybe this is old-school and not valid today anymore as it was 10 years ago, but keeping traffic local and not pushing the same data through the big exchanges and long distance lines again and again stil seems reasonable to me for various reasons. I also vote for more geographic distribution and a local mirror in europe. While not having any usage data (current usage, hstroy, perspectives), I cannot decide of course, if the time has already come, but I think time will come in foreseeable future. - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | pgpny7QCRrb3G.pgp Description: PGP signature
Re: portsnap mirror servers
On 2006.04.19 09:50:31 +0200, Oliver Brandmueller wrote: > On Wed, Apr 19, 2006 at 01:28:56AM +0100, Chris wrote: > > On 18/04/06, Colin Percival <[EMAIL PROTECTED]> wrote: > > > Why do you think there should be an .eu mirror? > > > > Whilst portsnap is fast, it is a noticeable speed difference when > > using from eu servers, I also think its a good idea for redundancy. > > I did not yet check in the sources or with tcpdump, but from the > htrougput I see, I'd guess, there's a lot of sequential two-way > communication involved. That kind of traffic is massively influenced by Hey, Recent portsnap versions (since the ones shipped in 6.0 AFAIR) uses HTTP pipelining (when possible) which means that the latency really doesn't matter since many requests are sent at once without waiting for the reply. I should mention that when pipelining is enabled I don't really see a big difference when using portsnap from Europe compared to systems in the US. More often the local disk limits the speed of portsnap updates for me rather than bandwith/latency. As Colin has said before, there will be more mirrors later, but there really just isn't a need for more right now. -- Simon L. Nielsen pgpEnLZ2E3Q1N.pgp Description: PGP signature
em (+pf+vlan+bridge+netgraph) stop sending packets (?)
I run a 6.1-RC (as of Apr, 14th) and after a day nothing can be sent from em interface. It is a filtering+accounting bridge-on-a-stick, with em interface connected to 3Com Switch 4200 100Mbit (not Gbit) port with 4 tagged vlans on it: # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. hostname=".gfk.ru" defaultrouter="10.X.X.X" ifconfig_sis0="10.X.X.X/24" ifconfig_em0="up" cloned_interfaces="vlan0 vlan1 vlan2 vlan3 bridge0 bridge1" ifconfig_vlan0="84.X.X.X/28 vlan 21 vlandev em0 up" ifconfig_vlan1="vlan 22 vlandev em0 up" ifconfig_bridge0="addm vlan0 addm vlan1 up" ifconfig_vlan2="217.X.X.X/29 vlan 31 vlandev em0 up" ifconfig_vlan3="vlan 32 vlandev em0 up" ifconfig_bridge1="addm vlan2 addm vlan3 up" syslogd_flags="-ss" sshd_enable="YES" ipsec_enable="YES" pf_enable="YES" pf_rules="/etc/pf.freeroute" pflog_enable="YES" and kernel is GENERIC with unused hardware removed and options DEVICE_POLLING options IPSEC options IPSEC_ESP options IPSEC_FILTERGIF device vlan device pf device pflog device pfsync device if_bridge # altq(9). Enable the base part of the hooks with the ALTQ option. # also have the ALTQ_NOPCC option. options ALTQ options ALTQ_CBQ# Class Bases Queueing options ALTQ_RED# Random Early Detection options ALTQ_RIO# RED In/Out options ALTQ_HFSC # Hierarchical Packet Scheduler options ALTQ_CDNR # Traffic conditioner options ALTQ_PRIQ # Priority Queueing options ALTQ_NOPCC # Required for SMP build #optionsALTQ_DEBUG added. em0 is [EMAIL PROTECTED]:10:0: class=0x02 card=0x002e8086 chip=0x100e8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82540EM Gigabit Ethernet Controller' class= network subclass = ethernet em0: port 0xb400-0xb43f mem 0xd7ea-0xd7eb,0xd7e8-0xd7e9 irq 18 at device 10.0 on pci0 em0: [GIANT-LOCKED] em0: Ethernet address: 00:07:e9:09:c2:3d Polling was not used (I'll try to work with polling enabled on em0). ALTQ is not configured, pf has all block rules logged and I can't see anything relevant logged to pflog. This machine also use netgraph netflow for traffic accounting on vlan interfaces, but shutting down all netgraph nodes does not help. Turning vlans, bridge and em down and up does not help too. Traffic is received (I can see pairs of OSPF HELO messages from ISP router logged on pflog0 exactly every 10 seconds), but it looks like nothing can be sent. Yuriy Tsibizov, GfK RUS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Tyan K8WE BIOS v1.03 and -STABLE
* Damian Gerow ([EMAIL PROTECTED]) wrote: > I tried updating the BIOS on my K8WE (S2895) yesterday to 1.03, but > after the update, FreeBSD (RELENG_6 dated March 26) would randomly > freeze after booting. > > As I was updating from v1.01, I suspect it may be the updates to > the nVidia SATA firmware that caused the issue, as things generally > froze shortly after the background fsck processed kicked in (with, > obviously, the exception of the first boot, and a few others). It may > be worth noting that Windows, though booting fine, did complain that > the ATA driver was mis-matched for the firmware of the ATA controller. > > Is anyone else successfully running -STABLE with v1.03 on a K8WE? Just > wondering if this is something specific to the options I've chosen, or if > it's an interaction issue between FreeBSD and this BIOS revision. > > (No, I haven't tried just going to 1.02, as I needed the machine. Though > that should be a fairly good test to narrow down what the problem is.) I've not tried 1.03; I just tried flashing, but apparantly the only floppy I have to hand has died. However, I've been running 1.02 for months without problems. The only SATA issues I've encountered are non-functional hot-plug and the usual 4GB+/multiple drives lockup, which I "solved" by using a LSI MegaRAID for 6 of the 8 drives. This is using the same SATA firmware as 1.03 according to the changelog on http://www.tyan.com/support/html/b_s2895.html so I doubt it's that. -- Thomas 'Freaky' Hurst http://hur.st/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Tyan K8WE BIOS v1.03 and -STABLE
From: "Thomas Hurst" <[EMAIL PROTECTED]>
* Damian Gerow ([EMAIL PROTECTED]) wrote:
I tried updating the BIOS on my K8WE (S2895) yesterday to 1.03, but
after the update, FreeBSD (RELENG_6 dated March 26) would randomly
freeze after booting.
As I was updating from v1.01, I suspect it may be the updates to
the nVidia SATA firmware that caused the issue, as things generally
froze shortly after the background fsck processed kicked in (with,
obviously, the exception of the first boot, and a few others). It may
be worth noting that Windows, though booting fine, did complain that
the ATA driver was mis-matched for the firmware of the ATA controller.
Is anyone else successfully running -STABLE with v1.03 on a K8WE? Just
wondering if this is something specific to the options I've chosen, or if
it's an interaction issue between FreeBSD and this BIOS revision.
(No, I haven't tried just going to 1.02, as I needed the machine. Though
that should be a fairly good test to narrow down what the problem is.)
I've not tried 1.03; I just tried flashing, but apparantly the only
floppy I have to hand has died. However, I've been running 1.02 for
months without problems. The only SATA issues I've encountered are
non-functional hot-plug and the usual 4GB+/multiple drives lockup, which I
"solved" by using a LSI MegaRAID for 6 of the 8 drives.
This is using the same SATA firmware as 1.03 according to the changelog
on http://www.tyan.com/support/html/b_s2895.html so I doubt it's that.
I have one of those here, too. I have the 205H BIOS running. At the moment
the system is tied up being XP because that's where I earn my income.
One thing I did discover is that the latest AMD AGP software that is
officially posted as of the beginning of the year is bad. I managed to get
a copy of an experimental AGP GART driver that works like a champ. There
might be a similar issue with the code for BSD to watch for. (It took
over a month to track that down. I could only run a single CPU with
cards in carefully selected slots with the release GART BIOS. With this
beta one I got I can go full bore and everything is basically cool.)
{^_^} Joanne
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
kouwell ata raid
hello, i'm looking for some cheap hardware ata raid (mirror) for freebsd 6 i think about KOUWELL KW-571B, it uses Silicon Image Sil 0680 chip. I heard that this chip was not supported in FreeBSD, but as I look to "man ad", it seems, it is supported now. My question is, does somebody use it? and works it? is there some management software (ie. disk failure signalization)? Thank for help Ondra ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kouwell ata raid
Ondra Holecek wrote: hello, i'm looking for some cheap hardware ata raid (mirror) for freebsd 6 i think about KOUWELL KW-571B, it uses Silicon Image Sil 0680 chip. I heard that this chip was not supported in FreeBSD, but as I look to "man ad", it seems, it is supported now. My question is, does somebody use it? and works it? is there some management software (ie. disk failure signalization)? If it is anything like the previous Sil chipsets it will not be reliable. I'd be very sceptical about it indeed. I would be interested if you could provide some information on your experiences with it. Also if is worth knowing that at least on some "hardware" RAID implementations they are not really hardware at all (from what I understand). This is true one at least one system (a low-end Dell PowerEdge). HTH, Dominic Thank for help Ondra ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ath compile error on releng_5
seems the ath_hal source on releng_5 is i386 and does not compile as module neither as kernel configuration on amd64 ath compiles as module but can not be loaded (exec error) I suppose this is a known issue or some needs details? ld -d -warn-common -r -d -o ath_hal.ko hal.o ah_osdep.o ld: Relocatable linking with relocations from format elf32-i386-freebsd (hal.o) to format elf64-x86-64 (ath_hal.ko) is not supported *** Error code 1 Stop in /usr/src/sys/modules/ath_hal. João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
wpa_supplicant and wi
I am using a Netgear MA401 with the wi driver, and am having trouble
using wpa_supplicant to set static WEP keys. I have the wlan_wep.ko
module loaded with wlan and wi built into the kernel. My
wpa_supplicant.conf looks like this:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid="INTERNERD"
scan_ssid=1
priority=1
key_mgmt=NONE
wep_key0=75745E266D4247372840217E73
wep_tx_keyidx=0
}
and wpa_supplicant -i wi0 -c /etc/wpa_supplicant.conf -d -d returns
the following:
Initializing interface 'wi0' conf '/etc/wpa_supplicant.conf' driver
'default' ctrl_interface 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0 (from group name 'wheel')
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=9):
49 4e 54 45 52 4e 45 52 44INTERNERD
scan_ssid=1 (0x1)
priority=1 (0x1)
key_mgmt: 0x4
wep_key0 - hexdump(len=13): 75 74 5e 26 6d 42 47 37 28 40 21 7e 73
wep_tx_keyidx=0 (0x0)
Priority group 1
id=0 ssid='INTERNERD'
Initializing interface (2) 'wi0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Own MAC address: 00:09:5b:29:81:67
wpa_driver_bsd_set_wpa: enabled=1
wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1
wpa_driver_bsd_del_key: keyidx=0
wpa_driver_bsd_del_key: keyidx=1
wpa_driver_bsd_del_key: keyidx=2
wpa_driver_bsd_del_key: keyidx=3
wpa_driver_bsd_set_countermeasures: enabled=0
wpa_driver_bsd_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 10 usec
Added interface wi0
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=9):
49 4e 54 45 52 4e 45 52 44INTERNERD
State: SCANNING -> ASSOCIATED
Associated to a new BSS: BSSID=00:14:bf:00:2e:d4
No keys have been configured - skip key clearing
Network configuration found for the current AP
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
EAPOL: External notification - portControl=ForceAuthorized
Associated with 00:14:bf:00:2e:d4
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state S_FORCE_AUTH
EAPOL: SUPP_BE entering state IDLE
Cancelling authentication timeout
State: ASSOCIATED -> COMPLETED
No keys are set on the wi0 interface apparently, as ifconfig reports
deftxkey UNDEF and no configured keys. In other outputs from
wpa_supplicant that I've seen, there are lines beginning with
wpa_driver_bsd_key_set that appear to be key setting.
Does anyone have this working with a MA401 that could help me out?
Thanks,
Isaac Waldron
--
Isaac Waldron
[EMAIL PROTECTED]
mobile: 1-508-353-3453
aim: n1yzi
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wpa_supplicant and wi
I should add that I'm running RELENG_6 updated and compiled on 4/19/2006.
On 4/19/06, Isaac Waldron <[EMAIL PROTECTED]> wrote:
> I am using a Netgear MA401 with the wi driver, and am having trouble
> using wpa_supplicant to set static WEP keys. I have the wlan_wep.ko
> module loaded with wlan and wi built into the kernel. My
> wpa_supplicant.conf looks like this:
>
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=wheel
>
> network={
> ssid="INTERNERD"
> scan_ssid=1
> priority=1
> key_mgmt=NONE
> wep_key0=75745E266D4247372840217E73
> wep_tx_keyidx=0
> }
>
> and wpa_supplicant -i wi0 -c /etc/wpa_supplicant.conf -d -d returns
> the following:
>
> Initializing interface 'wi0' conf '/etc/wpa_supplicant.conf' driver
> 'default' ctrl_interface 'N/A'
> Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
> Reading configuration file '/etc/wpa_supplicant.conf'
> ctrl_interface='/var/run/wpa_supplicant'
> ctrl_interface_group=0 (from group name 'wheel')
> Line: 4 - start of a new network block
> ssid - hexdump_ascii(len=9):
> 49 4e 54 45 52 4e 45 52 44INTERNERD
> scan_ssid=1 (0x1)
> priority=1 (0x1)
> key_mgmt: 0x4
> wep_key0 - hexdump(len=13): 75 74 5e 26 6d 42 47 37 28 40 21 7e 73
> wep_tx_keyidx=0 (0x0)
> Priority group 1
>id=0 ssid='INTERNERD'
> Initializing interface (2) 'wi0'
> EAPOL: SUPP_PAE entering state DISCONNECTED
> EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> EAPOL: SUPP_BE entering state INITIALIZE
> EAP: EAP entering state DISABLED
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> Own MAC address: 00:09:5b:29:81:67
> wpa_driver_bsd_set_wpa: enabled=1
> wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1
> wpa_driver_bsd_del_key: keyidx=0
> wpa_driver_bsd_del_key: keyidx=1
> wpa_driver_bsd_del_key: keyidx=2
> wpa_driver_bsd_del_key: keyidx=3
> wpa_driver_bsd_set_countermeasures: enabled=0
> wpa_driver_bsd_set_drop_unencrypted: enabled=1
> Setting scan request: 0 sec 10 usec
> Added interface wi0
> State: DISCONNECTED -> SCANNING
> Starting AP scan (specific SSID)
> Scan SSID - hexdump_ascii(len=9):
> 49 4e 54 45 52 4e 45 52 44INTERNERD
> State: SCANNING -> ASSOCIATED
> Associated to a new BSS: BSSID=00:14:bf:00:2e:d4
> No keys have been configured - skip key clearing
> Network configuration found for the current AP
> WPA: clearing AP WPA IE
> WPA: clearing AP RSN IE
> WPA: clearing own WPA/RSN IE
> EAPOL: External notification - portControl=ForceAuthorized
> Associated with 00:14:bf:00:2e:d4
> WPA: Association event - clear replay counter
> EAPOL: External notification - portEnabled=0
> EAPOL: External notification - portValid=0
> EAPOL: External notification - portEnabled=1
> EAPOL: SUPP_PAE entering state S_FORCE_AUTH
> EAPOL: SUPP_BE entering state IDLE
> Cancelling authentication timeout
> State: ASSOCIATED -> COMPLETED
>
> No keys are set on the wi0 interface apparently, as ifconfig reports
> deftxkey UNDEF and no configured keys. In other outputs from
> wpa_supplicant that I've seen, there are lines beginning with
> wpa_driver_bsd_key_set that appear to be key setting.
>
> Does anyone have this working with a MA401 that could help me out?
>
> Thanks,
> Isaac Waldron
> --
> Isaac Waldron
> [EMAIL PROTECTED]
> mobile: 1-508-353-3453
> aim: n1yzi
>
--
Isaac Waldron
[EMAIL PROTECTED]
mobile: 1-508-353-3453
aim: n1yzi
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ssh- lagging logins
On Apr 19, 2006, at 00:16, Low Kian Seong wrote: Cyberhigh, Well, you can always try to find out what is going on my passing the '-vvv' parameter to ssh while it's trying to access the remote machine. On 4/19/06, CyBerHigh <[EMAIL PROTECTED]> wrote: I am using Freebsd 6.0 and running Openssh. All of a sudden it takes nearly 4 minutes to conferm that my password is correct. It has never done this to me and all of a sudden it started it. I haven't even update the ports collection or anything so there is no reason I can think of way it would just start? Does anyone else have this problem? You may want to check your DNS infrastructure / settings. SSHd does lookups to make sure that forward and reverse mappings are the same. If there's an issue with DNS, then these lookups may take a while. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ypwhich -m
Hi, I found that ypwhich -m does not work on 6.1-RC, it shows ypwhich: can't find the master of `�`: reason: No such map in server's domain IIRC, there was a commit last year to fix this. After some search, I think it is include/rpcsvc/yp_prot.h revision 1.13 done by peter@ (CC'ed). As far as I can tell, ypwhich -m is also broken on 5.4 and 5.5-PRERELEASE. I have tested that revision on a 5.5-PRERELEASE machine, it fixes ypwhich -m. I would like to see this MFC'ed to RELENG_6 and RELENG_5, so the newer releases will have this fixed. Thanks, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wpa_supplicant and wi
> Date: Wed, 19 Apr 2006 18:12:13 -0400
> From: "Isaac Waldron" <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
> I should add that I'm running RELENG_6 updated and compiled on 4/19/2006.
>
> On 4/19/06, Isaac Waldron <[EMAIL PROTECTED]> wrote:
> > I am using a Netgear MA401 with the wi driver, and am having trouble
> > using wpa_supplicant to set static WEP keys. I have the wlan_wep.ko
> > module loaded with wlan and wi built into the kernel. My
> > wpa_supplicant.conf looks like this:
> >
> > ctrl_interface=3D/var/run/wpa_supplicant
> > ctrl_interface_group=3Dwheel
> >
> > network=3D{
> > ssid=3D"INTERNERD"
> > scan_ssid=3D1
> > priority=3D1
> > key_mgmt=3DNONE
> > wep_key0=3D75745E266D4247372840217E73
> > wep_tx_keyidx=3D0
> > }
> >
> > and wpa_supplicant -i wi0 -c /etc/wpa_supplicant.conf -d -d returns
> > the following:
> >
> > Initializing interface 'wi0' conf '/etc/wpa_supplicant.conf' driver
> > 'default' ctrl_interface 'N/A'
> > Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.con=
> f'
> > Reading configuration file '/etc/wpa_supplicant.conf'
> > ctrl_interface=3D'/var/run/wpa_supplicant'
> > ctrl_interface_group=3D0 (from group name 'wheel')
> > Line: 4 - start of a new network block
> > ssid - hexdump_ascii(len=3D9):
> > 49 4e 54 45 52 4e 45 52 44INTERNERD
> > scan_ssid=3D1 (0x1)
> > priority=3D1 (0x1)
> > key_mgmt: 0x4
> > wep_key0 - hexdump(len=3D13): 75 74 5e 26 6d 42 47 37 28 40 21 7e 73
> > wep_tx_keyidx=3D0 (0x0)
> > Priority group 1
> >id=3D0 ssid=3D'INTERNERD'
> > Initializing interface (2) 'wi0'
> > EAPOL: SUPP_PAE entering state DISCONNECTED
> > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > EAPOL: SUPP_BE entering state INITIALIZE
> > EAP: EAP entering state DISABLED
> > EAPOL: External notification - portEnabled=3D0
> > EAPOL: External notification - portValid=3D0
> > Own MAC address: 00:09:5b:29:81:67
> > wpa_driver_bsd_set_wpa: enabled=3D1
> > wpa_driver_bsd_set_wpa_internal: wpa=3D3 privacy=3D1
> > wpa_driver_bsd_del_key: keyidx=3D0
> > wpa_driver_bsd_del_key: keyidx=3D1
> > wpa_driver_bsd_del_key: keyidx=3D2
> > wpa_driver_bsd_del_key: keyidx=3D3
> > wpa_driver_bsd_set_countermeasures: enabled=3D0
> > wpa_driver_bsd_set_drop_unencrypted: enabled=3D1
> > Setting scan request: 0 sec 10 usec
> > Added interface wi0
> > State: DISCONNECTED -> SCANNING
> > Starting AP scan (specific SSID)
> > Scan SSID - hexdump_ascii(len=3D9):
> > 49 4e 54 45 52 4e 45 52 44INTERNERD
> > State: SCANNING -> ASSOCIATED
> > Associated to a new BSS: BSSID=3D00:14:bf:00:2e:d4
> > No keys have been configured - skip key clearing
> > Network configuration found for the current AP
> > WPA: clearing AP WPA IE
> > WPA: clearing AP RSN IE
> > WPA: clearing own WPA/RSN IE
> > EAPOL: External notification - portControl=3DForceAuthorized
> > Associated with 00:14:bf:00:2e:d4
> > WPA: Association event - clear replay counter
> > EAPOL: External notification - portEnabled=3D0
> > EAPOL: External notification - portValid=3D0
> > EAPOL: External notification - portEnabled=3D1
> > EAPOL: SUPP_PAE entering state S_FORCE_AUTH
> > EAPOL: SUPP_BE entering state IDLE
> > Cancelling authentication timeout
> > State: ASSOCIATED -> COMPLETED
> >
> > No keys are set on the wi0 interface apparently, as ifconfig reports
> > deftxkey UNDEF and no configured keys. In other outputs from
> > wpa_supplicant that I've seen, there are lines beginning with
> > wpa_driver_bsd_key_set that appear to be key setting.
> >
> > Does anyone have this working with a MA401 that could help me out?
> >
> > Thanks,
> > Isaac Waldron
> > --
> > Isaac Waldron
> > [EMAIL PROTECTED]
> > mobile: 1-508-353-3453
> > aim: n1yzi
> >
Unfortunately the wi driver (and some versions of the hardware) does not
provide enough information to the wlan layer to support wpa-supplicant.
Check out the archives for previous discussions of this.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ypwhich -m
On Wed, Apr 19, 2006 at 07:45:47PM -0400, Rong-En Fan wrote:
> Hi,
>
> I found that ypwhich -m does not work on 6.1-RC, it shows
>
> ypwhich: can't find the master of `???`: reason: No such map in server's
> domain
>
> IIRC, there was a commit last year to fix this. After some search, I think
> it is include/rpcsvc/yp_prot.h revision 1.13 done by peter@ (CC'ed).
> As far as I can tell, ypwhich -m is also broken on 5.4 and 5.5-PRERELEASE.
>
> I have tested that revision on a 5.5-PRERELEASE machine, it
> fixes ypwhich -m. I would like to see this MFC'ed to RELENG_6
> and RELENG_5, so the newer releases will have this fixed.
I've verified this on a 6-STABLE machine from January. If approved,
I'll do it tomorrow cut-n-paste damanged patch below. It's a trivial
one line change so anyone could do it.
-- Brooks
@@ -148,7 +148,7 @@
};
struct ypmaplist {
- char ypml_name[YPMAXMAP + 1];
+ char *ypml_name;
struct ypmaplist *ypml_next;
};
--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
pgpXQfxob30Uw.pgp
Description: PGP signature
Re: ath compile error on releng_5
On Wednesday 19 April 2006 14:57, JoaoBR wrote: > seems the ath_hal source on releng_5 is i386 and does not compile as > module neither as kernel configuration on amd64 > > ath compiles as module but can not be loaded (exec error) > > I suppose this is a known issue or some needs details? > > ld -d -warn-common -r -d -o ath_hal.ko hal.o ah_osdep.o > ld: Relocatable linking with relocations from format > elf32-i386-freebsd (hal.o) to format elf64-x86-64 (ath_hal.ko) is not ^^ ^ > supported *** Error code 1 Something isn't right there. You can't mix 32 and 64 bit binaries. Myy recollection is that on 5.x, the only hal is for i386. Assuming that my recollection is right, you'd have to go to 6.x. -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath compile error on releng_5
JoaoBR wrote: seems the ath_hal source on releng_5 is i386 and does not compile as module neither as kernel configuration on amd64 ath compiles as module but can not be loaded (exec error) I suppose this is a known issue or some needs details? ld -d -warn-common -r -d -o ath_hal.ko hal.o ah_osdep.o ld: Relocatable linking with relocations from format elf32-i386-freebsd (hal.o) to format elf64-x86-64 (ath_hal.ko) is not supported *** Error code 1 Stop in /usr/src/sys/modules/ath_hal. releng5 only has i386 support I believe. Trying to use a 32-bit build in a 64-bit kernel will not work. I'm not sure what you're trying to do but wireless support in releng5 is unlikely to be very satisfying; switch to releng6. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wpa_supplicant and wi
Isaac Waldron wrote:
I should add that I'm running RELENG_6 updated and compiled on 4/19/2006.
On 4/19/06, Isaac Waldron <[EMAIL PROTECTED]> wrote:
I am using a Netgear MA401 with the wi driver, and am having trouble
using wpa_supplicant to set static WEP keys. I have the wlan_wep.ko
module loaded with wlan and wi built into the kernel. My
wpa_supplicant.conf looks like this:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid="INTERNERD"
scan_ssid=1
priority=1
key_mgmt=NONE
wep_key0=75745E266D4247372840217E73
wep_tx_keyidx=0
}
and wpa_supplicant -i wi0 -c /etc/wpa_supplicant.conf -d -d returns
the following:
Initializing interface 'wi0' conf '/etc/wpa_supplicant.conf' driver
'default' ctrl_interface 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0 (from group name 'wheel')
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=9):
49 4e 54 45 52 4e 45 52 44INTERNERD
scan_ssid=1 (0x1)
priority=1 (0x1)
key_mgmt: 0x4
wep_key0 - hexdump(len=13): 75 74 5e 26 6d 42 47 37 28 40 21 7e 73
wep_tx_keyidx=0 (0x0)
Priority group 1
id=0 ssid='INTERNERD'
Initializing interface (2) 'wi0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Own MAC address: 00:09:5b:29:81:67
wpa_driver_bsd_set_wpa: enabled=1
wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1
wpa_driver_bsd_del_key: keyidx=0
wpa_driver_bsd_del_key: keyidx=1
wpa_driver_bsd_del_key: keyidx=2
wpa_driver_bsd_del_key: keyidx=3
wpa_driver_bsd_set_countermeasures: enabled=0
wpa_driver_bsd_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 10 usec
Added interface wi0
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=9):
49 4e 54 45 52 4e 45 52 44INTERNERD
State: SCANNING -> ASSOCIATED
Associated to a new BSS: BSSID=00:14:bf:00:2e:d4
No keys have been configured - skip key clearing
Network configuration found for the current AP
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
EAPOL: External notification - portControl=ForceAuthorized
Associated with 00:14:bf:00:2e:d4
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state S_FORCE_AUTH
EAPOL: SUPP_BE entering state IDLE
Cancelling authentication timeout
State: ASSOCIATED -> COMPLETED
No keys are set on the wi0 interface apparently, as ifconfig reports
deftxkey UNDEF and no configured keys. In other outputs from
wpa_supplicant that I've seen, there are lines beginning with
wpa_driver_bsd_key_set that appear to be key setting.
Does anyone have this working with a MA401 that could help me out?
Should work; I'll check on it.
Sam
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wpa_supplicant and wi
Sam Leffler wrote:
Isaac Waldron wrote:
I should add that I'm running RELENG_6 updated and compiled on 4/19/2006.
On 4/19/06, Isaac Waldron <[EMAIL PROTECTED]> wrote:
I am using a Netgear MA401 with the wi driver, and am having trouble
using wpa_supplicant to set static WEP keys. I have the wlan_wep.ko
module loaded with wlan and wi built into the kernel. My
wpa_supplicant.conf looks like this:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid="INTERNERD"
scan_ssid=1
priority=1
key_mgmt=NONE
wep_key0=75745E266D4247372840217E73
wep_tx_keyidx=0
}
and wpa_supplicant -i wi0 -c /etc/wpa_supplicant.conf -d -d returns
the following:
Initializing interface 'wi0' conf '/etc/wpa_supplicant.conf' driver
'default' ctrl_interface 'N/A'
Configuration file '/etc/wpa_supplicant.conf' ->
'/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0 (from group name 'wheel')
Line: 4 - start of a new network block
ssid - hexdump_ascii(len=9):
49 4e 54 45 52 4e 45 52 44INTERNERD
scan_ssid=1 (0x1)
priority=1 (0x1)
key_mgmt: 0x4
wep_key0 - hexdump(len=13): 75 74 5e 26 6d 42 47 37 28 40 21 7e 73
wep_tx_keyidx=0 (0x0)
Priority group 1
id=0 ssid='INTERNERD'
Initializing interface (2) 'wi0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Own MAC address: 00:09:5b:29:81:67
wpa_driver_bsd_set_wpa: enabled=1
wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1
wpa_driver_bsd_del_key: keyidx=0
wpa_driver_bsd_del_key: keyidx=1
wpa_driver_bsd_del_key: keyidx=2
wpa_driver_bsd_del_key: keyidx=3
wpa_driver_bsd_set_countermeasures: enabled=0
wpa_driver_bsd_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 10 usec
Added interface wi0
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=9):
49 4e 54 45 52 4e 45 52 44INTERNERD
State: SCANNING -> ASSOCIATED
Associated to a new BSS: BSSID=00:14:bf:00:2e:d4
No keys have been configured - skip key clearing
Network configuration found for the current AP
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
EAPOL: External notification - portControl=ForceAuthorized
Associated with 00:14:bf:00:2e:d4
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state S_FORCE_AUTH
EAPOL: SUPP_BE entering state IDLE
Cancelling authentication timeout
State: ASSOCIATED -> COMPLETED
No keys are set on the wi0 interface apparently, as ifconfig reports
deftxkey UNDEF and no configured keys. In other outputs from
wpa_supplicant that I've seen, there are lines beginning with
wpa_driver_bsd_key_set that appear to be key setting.
Does anyone have this working with a MA401 that could help me out?
Should work; I'll check on it.
Sorry I forgot how poorly wi works; you'll need to stick to command line
tools until someone decides they want to give it some TLC.
Sam
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ypwhich -m
Brooks Davis wrote:
On Wed, Apr 19, 2006 at 07:45:47PM -0400, Rong-En Fan wrote:
Hi,
I found that ypwhich -m does not work on 6.1-RC, it shows
ypwhich: can't find the master of `???`: reason: No such map in server's domain
IIRC, there was a commit last year to fix this. After some search, I think
it is include/rpcsvc/yp_prot.h revision 1.13 done by peter@ (CC'ed).
As far as I can tell, ypwhich -m is also broken on 5.4 and 5.5-PRERELEASE.
I have tested that revision on a 5.5-PRERELEASE machine, it
fixes ypwhich -m. I would like to see this MFC'ed to RELENG_6
and RELENG_5, so the newer releases will have this fixed.
I've verified this on a 6-STABLE machine from January. If approved,
I'll do it tomorrow cut-n-paste damanged patch below. It's a trivial
one line change so anyone could do it.
-- Brooks
@@ -148,7 +148,7 @@
};
struct ypmaplist {
- char ypml_name[YPMAXMAP + 1];
+ char *ypml_name;
struct ypmaplist *ypml_next;
};
Approved
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
