Re: Intel 3945 wpi driver doesn't seem to work ('cause of license problems???)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 vittorio wrote: legal.intel_wpi.license_ack=1 is in /boot/loader.conf BUT 1) it seems that sysctl is unable to find it and I have to set it via kenv legal.intel_wpi.license_ack=1 Shouldn't this variable be set by sysctl or by loader.conf? 2) dhclient is unable to get an IP address (trying to set wpi0 up with a fixed IP makes wpi0 not associated to any AP) Hmmm I have a similar setup. In my case, it's a Dell D800 using iwi: % grep iwi /var/run/dmesg.boot iwi0: Intel(R) PRO/Wireless 2200BG mem 0xfafee000-0xfafeefff irq 9 at device 3.0 on pci2 [...] and a ZyXEL 660HW router: Menu 24.2.1 - System Maintenance - Information Name: gate.infracaninophile.co.uk Routing: IP ZyNOS F/W Version: V3.40(ACI.7) | 10/18/2006 ADSL Chipset Vendor: DMT FwVer: 3.4.1.0_A_TC, HwVer: T14F7_+ Standard: Multi-Mode However I have no problems setting legal.intel_iwi.license_ack=1 from /boot/loader.conf -- it could be something as stupid as no newline at end of file. Try running 'od -c /boot/loader.conf' or 'cat -e /boot/loader.conf' to verify. On the question of the DHCP service provided by this combination router and wlan hardware, and indeed the whole performance at providing wireless lan connectivity -- I'm not particularly impressed. I'd restart the laptop and everything would be fine for a few hours, but leave it running overnight and it would lose the lease and end up without an IPv4 address. IPv6 addresses autoconfigured with rtadvd and rtsol seem quite a lot more stable but I've seen every combination of being able or not to ping or ping6 the laptop from a wired machine. In the end I found that setting the ZyXEL to do DHCP Relay and running isc-dhcpd on a FBSD box with the lease times increased as so: default-lease-time 3600;# 1 hour max-lease-time 86400; # 1 day plus moving the laptop to within about 2m of the ZyXEL seems to have made quite an improvement. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHe1w38Mjk52CukIwRCLkmAJ9VIYUgB1SHW+AUkvE7949OFnlbgACfUf4V r8g3taRYYcBHLv9GIdOsKmc= =+AU+ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel 3945 wpi driver doesn't seem to work ('cause of license problems???)
What I really need is an explanation **step by step** on how to set up a wpi connection. Step by step . Ciao Vittorio Il Wednesday 02 January 2008 10:41:11 Matthew Seaman ha scritto: vittorio wrote: legal.intel_wpi.license_ack=1 is in /boot/loader.conf BUT 1) it seems that sysctl is unable to find it and I have to set it via kenv legal.intel_wpi.license_ack=1 Shouldn't this variable be set by sysctl or by loader.conf? 2) dhclient is unable to get an IP address (trying to set wpi0 up with a fixed IP makes wpi0 not associated to any AP) Hmmm I have a similar setup. In my case, it's a Dell D800 using iwi: % grep iwi /var/run/dmesg.boot iwi0: Intel(R) PRO/Wireless 2200BG mem 0xfafee000-0xfafeefff irq 9 at device 3.0 on pci2 [...] and a ZyXEL 660HW router: Menu 24.2.1 - System Maintenance - Information Name: gate.infracaninophile.co.uk Routing: IP ZyNOS F/W Version: V3.40(ACI.7) | 10/18/2006 ADSL Chipset Vendor: DMT FwVer: 3.4.1.0_A_TC, HwVer: T14F7_+ Standard: Multi-Mode However I have no problems setting legal.intel_iwi.license_ack=1 from /boot/loader.conf -- it could be something as stupid as no newline at end of file. Try running 'od -c /boot/loader.conf' or 'cat -e /boot/loader.conf' to verify. On the question of the DHCP service provided by this combination router and wlan hardware, and indeed the whole performance at providing wireless lan connectivity -- I'm not particularly impressed. I'd restart the laptop and everything would be fine for a few hours, but leave it running overnight and it would lose the lease and end up without an IPv4 address. IPv6 addresses autoconfigured with rtadvd and rtsol seem quite a lot more stable but I've seen every combination of being able or not to ping or ping6 the laptop from a wired machine. In the end I found that setting the ZyXEL to do DHCP Relay and running isc-dhcpd on a FBSD box with the lease times increased as so: default-lease-time 3600;# 1 hour max-lease-time 86400; # 1 day plus moving the laptop to within about 2m of the ZyXEL seems to have made quite an improvement. Cheers, Matthew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Intel 3945 wpi driver doesn't seem to work ('cause of license problems???)
Context: Router ZyXEL ADSL+2 with dhcp up and running Laptop HP Pavillion Entertainment DV6000 intel centrino duo 2GB of memory hpbsd# uname -a FreeBSD hpbsd.vic 7.0-BETA4 FreeBSD 7.0-BETA4 #0: Thu Dec 27 22:18:53 CET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HP03 i386 hpbsd# all wpi's necessary devices are compiled in the kernel device wpi device pci device wlan device wlan_amrr device firmware /var/log/messages kernel: wpi0: Intel(R) PRO/Wireless 3945ABG mem 0xd800-0xd8000fff irq 16 at device 0.0 on pci2 kernel: wpi0: Ethernet address: 00:19:d2:99:e3:cb kernel: wpi0: [ITHREAD] kernel: wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps kernel: wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps kernel: wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps the line legal.intel_wpi.license_ack=1 is in /boot/loader.conf BUT 1) it seems that sysctl is unable to find it and I have to set it via kenv legal.intel_wpi.license_ack=1 Shouldn't this variable be set by sysctl or by loader.conf? 2) dhclient is unable to get an IP address (trying to set wpi0 up with a fixed IP makes wpi0 not associated to any AP) Here it is a session log SNIP hpbsd# sysctl -a|grep legal hpbsd# hpbsd# kenv legal.intel_wpi.license_ack=1 legal.intel_wpi.license_ack=1 hpbsd# kenv legal.intel_wpi.license_ack 1 hpbsd# ifconfig wpi0 ssid my_wireless weptxkey 1 wepmode on wepkey 0x1f7b0a5a0d hpbsd# dhclient wpi0 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 18 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 5 No DHCPOFFERS received. No working leases in persistent database - sleeping. hpbsd# ifconfig wpi0 wpi0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:19:d2:99:e3:cb inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps) status: associated ssid my_wireless channel 6 (2437 Mhz 11g) bssid 00:02:cf:61:81:fd authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit txpower 50 bmiss 7 scanvalid 60 protmode CTS /SNIP Even giving an ip fixed address to wpi0 doesn't seem to work, I cannot ping anything and for netstat -rn wpi0 doesn't seem to exist. Please help Ciao from Rome -- Vittorio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
