Re: an driver / Cisco Aironet 340 stopped working
Martin Blapp writes: Hi, DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 212.226.167.254 bound to 212.226.167.247 -- renewal in 228123 seconds. So the first time it works ? You get an IP here ... an0: Found Link on interface DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 15 No DHCPOFFERS received. No working leases in persistent database - sleeping. Why don't you get an IP here ? Does the server see your requests ? If not, the an0 driver is broken for your card. IMHO it's not dhclient fault here. Now I tested this at work with ISC DHCPD V3.0.1rc9 and it works just fine. For some reason Cisco dhcp server doesn't like FreeBSD anymore if connect comes from an0 driver :-) Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Hi, Now I tested this at work with ISC DHCPD V3.0.1rc9 and it works just fine. with the freebsd dhclient, or a unmodified V3.0.1rc9 one ? For some reason Cisco dhcp server doesn't like FreeBSD anymore if connect comes from an0 driver :-) Can you test the V3.0.1rc9 one at home too ? Tomppa Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Martin Blapp writes: Hi, Now I tested this at work with ISC DHCPD V3.0.1rc9 and it works just fine. with the freebsd dhclient, or a unmodified V3.0.1rc9 one ? For some reason Cisco dhcp server doesn't like FreeBSD anymore if connect comes from an0 driver :-) Can you test the V3.0.1rc9 one at home too ? I've to clarify this a little. I just used different dhcp server so FreeBSD side was always using the same latest dhclient cvsupped week ago. ISC dhcp server works with an0 and em0 Cisco dhcp server works with em0 but not with an0 Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Doug Ambrisko writes: I assume you are using a pccard version. It only a problem newer firmware. It works ... just noisy! You can try this patch to -current that should make it quiet. There is a bug with -current and setting the TX speed that I need to work on. Looks like things changed in the wlan module. I may commit this but there is an issue with the mpi-350 support. They changed the programing paradigm and after 14 packets the TX engine stalls. I'm still working on tweaks to that. I had hoped to get that working and commit all of this. Let me know how this works. It should just work. I was ready to say that it's not working but then ipv6 came up automatically. I didn't look this before but now it looks that dhclient don't get address but if manually set v4 address it works. I've to check how it works with older kernel because until now I only checked that I didn't get address from dhcp. Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Tomi Vainio - Sun Finland writes: | Doug Ambrisko writes: | | I assume you are using a pccard version. | | It only a problem newer firmware. It works ... just noisy! | | You can try this patch to -current that should make it quiet. | There is a bug with -current and setting the TX speed that I need | to work on. Looks like things changed in the wlan module. | I may commit this but there is an issue with the mpi-350 support. | They changed the programing paradigm and after 14 packets the | TX engine stalls. I'm still working on tweaks to that. | I had hoped to get that working and commit all of this. | | Let me know how this works. It should just work. | | I was ready to say that it's not working but then ipv6 came up | automatically. I didn't look this before but now it looks that | dhclient don't get address but if manually set v4 address it works. | I've to check how it works with older kernel because until now I only | checked that I didn't get address from dhcp. There have been some changes to dhclient (link detection) that might have some interaction side effects. Not blaming dhclient but that is something to be aware of. Doug A. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Hi, | I was ready to say that it's not working but then ipv6 came up | automatically. I didn't look this before but now it looks that | dhclient don't get address but if manually set v4 address it works. | I've to check how it works with older kernel because until now I only | checked that I didn't get address from dhcp. There have been some changes to dhclient (link detection) that might have some interaction side effects. Not blaming dhclient but that is something to be aware of. How old is your CURRENT installation ? Can you run dhclient in verbose mode and in foreground (-d -v) and maybe compile if with -DDEBUG ? Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Martin Blapp writes: How old is your CURRENT installation ? Can you run dhclient in verbose mode and in foreground (-d -v) and maybe compile if with -DDEBUG ? I've supped current on last Saturday. Here are debug logs and how Cisco sees the situation. Windows XP debug from Cisco is quite different. Tomppa *** em0 *** Script started on Tue Aug 19 21:10:58 2003 phb:~(1)# ifconfig -a fwe0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::39ff:fe34:7ff2%fwe0 prefixlen 64 scopeid 0x1 ether 02:00:39:34:7f:f2 ch 1 dma 0 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet6 fe80::208:dff:feda:ec61%em0 prefixlen 64 scopeid 0x2 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 ether 00:08:0d:da:ec:61 media: Ethernet autoselect status: no carrier lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 phb:~(2)# dhclient -d -v em0 Internet Software Consortium DHCP Client V3.0.1rc11 Copyright 1995-2002 Internet Software Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP Listening on BPF/em0/00:08:0d:da:ec:61 Sending on BPF/em0/00:08:0d:da:ec:61 Sending on Socket/fallback em0: Polling interface state em0: client state of 2 em0: link = 1 em0: Found Link on interface em0: Polling interface state em0: client state of 2 em0: link = 1 DHCPREQUEST on em0 to 255.255.255.255 port 67 em0: Polling interface state em0: client state of 1 em0: link = 1 DHCPREQUEST on em0 to 255.255.255.255 port 67 em0: Polling interface state em0: client state of 1 em0: link = 1 em0: Polling interface state em0: client state of 1 em0: link = 1 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 10 DHCPOFFER from 212.226.167.254 DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 212.226.167.254 bound to 212.226.167.247 -- renewal in 228123 seconds. em0: Polling interface state em0: client state of 5 em0: link = 1 em0: Polling interface state em0: client state of 5 em0: link = 1 ^C phb:~(3)# ifconfig -a fwe0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::39ff:fe34:7ff2%fwe0 prefixlen 64 scopeid 0x1 ether 02:00:39:34:7f:f2 ch 1 dma 0 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet6 fe80::208:dff:feda:ec61%em0 prefixlen 64 scopeid 0x2 inet 212.226.167.247 netmask 0xfff0 broadcast 212.226.167.255 ether 00:08:0d:da:ec:61 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 phb:~(4)# Script done on Tue Aug 19 21:12:19 2003 *** an0 *** Script started on Tue Aug 19 21:13:40 2003 phb:~(1)# ifconfig -a fwe0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::39ff:fe34:7ff2%fwe0 prefixlen 64 scopeid 0x1 ether 02:00:39:34:7f:f2 ch 1 dma 0 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet6 fe80::208:dff:feda:ec61%em0 prefixlen 64 scopeid 0x2 inet 212.226.167.247 netmask 0xfff0 broadcast 212.226.167.255 inet6 2001:670:82:babe:208:dff:feda:ec61 prefixlen 64 tentative autoconf ether 00:08:0d:da:ec:61 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 an0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::240:96ff:fe38:56e7%an0 prefixlen 64 scopeid 0x4 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 ether 00:40:96:38:56:e7 media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) status: associated ssid AsOlA 1:AsOlA stationname phb channel 6 authmode OPEN powersavemode CAM powersavesleep 200 wepmode ON weptxkey 1 wepkey 1:128-bit phb:~(2)# dhclient -d -v an0 Device an0 has 802.11 Internet Software Consortium DHCP Client V3.0.1rc11 Copyright 1995-2002 Internet Software Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP Device an0 has 802.11 Listening on BPF/an0/00:40:96:38:56:e7 Sending on BPF/an0/00:40:96:38:56:e7 Sending on Socket/fallback an0: Polling interface state an0: client state of 2 an0: link = 1 an0: Found Link on interface DHCPDISCOVER on an0 to
Re: an driver / Cisco Aironet 340 stopped working
Hi, DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 212.226.167.254 bound to 212.226.167.247 -- renewal in 228123 seconds. So the first time it works ? You get an IP here ... an0: Found Link on interface DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 15 No DHCPOFFERS received. No working leases in persistent database - sleeping. Why don't you get an IP here ? Does the server see your requests ? If not, the an0 driver is broken for your card. IMHO it's not dhclient fault here. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Martin Blapp writes: Why don't you get an IP here ? Does the server see your requests ? If not, the an0 driver is broken for your card. IMHO it's not dhclient fault here. Martin Did you look Cisco's dump where Windows DHCPDISCOVER appears as 0100.4096.3856.e7 but FreeBSD is 0040.9638.56e7? Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Hi, Did you look Cisco's dump where Windows DHCPDISCOVER appears as 0100.4096.3856.e7 but FreeBSD is 0040.9638.56e7? That's strange indeed. But 0040.9638.56e7 looks correct to me. Can you tell me why the server does not send anything back ? Why does it happen to be 01 before the mac if you use windows ? Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: an driver / Cisco Aironet 340 stopped working
Don't know if anyone replied yet since I don't subscribe to freebsd-current, but I had to add the following line to my /boot/loader.conf file. hw.pci.allow_unsupported_io_range=1 Jack -Original Message- From: Tomi Vainio - Sun Finland [mailto:[EMAIL PROTECTED] Sent: Saturday, August 16, 2003 4:27 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: an driver / Cisco Aironet 340 stopped working I've used my Cisco WLAN with Toshiba Portege 3440 couple years but now it's broken. I just upgraded to new Toshiba Tecra M1 and reinstalled FreeBSD there and now I get an0: record length mismatch -- expected 430, got 440 for Rid ff68 errors. I already tried with old laptop with latest kernel and old kernel from Jun 26th but it's also broken there so I cannot say who long this has been broken. Tomppa fwe0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::39ff:fe34:7ff2%fwe0 prefixlen 64 scopeid 0x1 ether 02:00:39:34:7f:f2 ch 1 dma 0 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet6 fe80::208:dff:feda:ec61%em0 prefixlen 64 scopeid 0x2 inet 212.226.167.247 netmask 0xfff0 broadcast 212.226.167.255 inet6 2001:670:82:babe:208:dff:feda:ec61 prefixlen 64 tentative autoconf ether 00:08:0d:da:ec:61 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 an0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::240:96ff:fe38:56e7%an0 prefixlen 64 scopeid 0x4 ether 00:40:96:38:56:e7 media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) status: associated ssid AsOlA 1:AsOlA stationname phb channel 6 authmode OPEN powersavemode CAM powersavesleep 200 wepmode ON weptxkey 1 wepkey 1:128-bit Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #3: Sat Aug 16 20:28:39 EEST 2003 [EMAIL PROTECTED]:/u/F/local/sup/5.0/sys/i386/compile/PHB acpi_alloc_wakeup_handler: unable to allocate wake memory Preloaded elf kernel /boot/kernel/kernel at 0xc065. Preloaded elf module /boot/kernel/splash_bmp.ko at 0xc06502e4. Preloaded elf module /boot/kernel/vesa.ko at 0xc0650394. Preloaded splash_image_data /boot/splash.bmp at 0xc0650440. Preloaded elf module /boot/kernel/usb.ko at 0xc0650490. Preloaded elf module /boot/kernel/ukbd.ko at 0xc0650538. Preloaded elf module /boot/kernel/ums.ko at 0xc06505e4. Preloaded elf module /boot/kernel/umass.ko at 0xc065068c. Preloaded elf module /boot/kernel/random.ko at 0xc0650738. Calibrating clock(s) ... i8254 clock: 1193183 Hz Timecounter i8254 frequency 1193183 Hz quality 0 Calibrating TSC clock ... TSC clock: 1396507980 Hz CPU: Intel(R) Pentium(R) M processor 1400MHz (1396.51-MHz 686-class CPU) Origin = GenuineIntel Id = 0x695 Stepping = 5 Features=0xa7e9f9bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV ,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE real memory = 536674304 (511 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00677000 - 0x1f692fff, 520208384 bytes (127004 pages) avail memory = 513142784 (489 MB) bios32: Found BIOS32 Service Directory header at 0xc00f0240 bios32: Entry = 0xfc0e3 (c00fc0e3) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xd641 pnpbios: Found PnP BIOS data at 0xc00f0450 pnpbios: Entry = f:9138 Rev = 1.0 pnpbios: Event flag at 510 pnpbios: OEM ID 8938f351 Other BIOS signatures found: wlan: 802.11 Link Layer null: null device, zero device mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 02 00 01 00 01 01 00 00 00 40 00 00 01 00 02 00 02 13 01 00 01 2d 01 00 01 38 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 31 mode(s) found VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc053aca0 (140) VESA: Trident CYBER 2100 VESA: TRIDENT MICROSYSTEMS INC. CYBER 2100 RXT 7.3 (16.28) random: entropy source splash: [EMAIL PROTECTED], size:787506 splash_bmp: beyond screen capacity (1024x768, 255 colors) splash_bmp: beyond screen capacity (1024x768, 255 colors) bmp_start(): splash_mode:261 splash: image decoder found: splash_bmp acpi0: TOSHIB 750 on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=33408086) pcibios: BIOS version 2.10 Using $PIR table, 8 entries at 0xc00f01a0 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded
Re: an driver / Cisco Aironet 340 stopped working
Peter Radcliffe writes: Have you got recent firmware on the cisco card ? The newer windows driver will helpfully upgrade it for you silently. If it has upgraded, downgrade it. The freebsd driver doesn't yet work with the new firmware. Cisco have changed the operation of the card with newer firmware and havn't released docs on working with the newer firmware. [EMAIL PROTECTED] writes: Don't know if anyone replied yet since I don't subscribe to freebsd-current, but I had to add the following line to my /boot/loader.conf file. hw.pci.allow_unsupported_io_range=1 I've tried multiple old firmwares and this loader.conf tweak but no luck yet. Can you say what was the last working firmware? Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Tomi Vainio - Sun Finland [EMAIL PROTECTED] probably said: Peter Radcliffe writes: Cisco have changed the operation of the card with newer firmware and havn't released docs on working with the newer firmware. I've tried multiple old firmwares and this loader.conf tweak but no luck yet. Can you say what was the last working firmware? I don't have any 340 cards, just 350 cards, so no. P. -- pir[EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Peter Radcliffe writes: Tomi Vainio - Sun Finland [EMAIL PROTECTED] probably said: Peter Radcliffe writes: Cisco have changed the operation of the card with newer firmware and havn't released docs on working with the newer firmware. I've tried multiple old firmwares and this loader.conf tweak but no luck yet. Can you say what was the last working firmware? I don't have any 340 cards, just 350 cards, so no. Firmware files are the same for both cards or that's my thought from this filename. 350-340-PCMCIA-LMC-PCI-v52017.exe Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Tomi Vainio - Sun Finland [EMAIL PROTECTED] probably said: Firmware files are the same for both cards or that's my thought from this filename. 350-340-PCMCIA-LMC-PCI-v52017.exe The firmware/driver files I have are labelled 350 only. 350 firmware 5.02.19 does not work. 5.00.03 does work. P. -- pir[EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Tomi Vainio - Sun Finland writes:
| I've used my Cisco WLAN with Toshiba Portege 3440 couple years but now
| it's broken. I just upgraded to new Toshiba Tecra M1 and reinstalled
| FreeBSD there and now I get an0: record length mismatch -- expected
| 430, got 440 for Rid ff68 errors. I already tried with old laptop
| with latest kernel and old kernel from Jun 26th but it's also broken
| there so I cannot say who long this has been broken.
I assume you are using a pccard version.
It only a problem newer firmware. It works ... just noisy!
You can try this patch to -current that should make it quiet.
There is a bug with -current and setting the TX speed that I need
to work on. Looks like things changed in the wlan module.
I may commit this but there is an issue with the mpi-350 support.
They changed the programing paradigm and after 14 packets the
TX engine stalls. I'm still working on tweaks to that.
I had hoped to get that working and commit all of this.
Let me know how this works. It should just work.
Doug A.
Index: sys/dev/an/if_aironet_ieee.h
===
RCS file: /cvs/src/sys/dev/an/if_aironet_ieee.h,v
retrieving revision 1.11
diff -c -r1.11 if_aironet_ieee.h
*** sys/dev/an/if_aironet_ieee.h29 Dec 2002 19:22:06 - 1.11
--- sys/dev/an/if_aironet_ieee.h19 Aug 2003 02:41:06 -
***
*** 63,69
* data, which is 240 words long, so 256 should be a safe
* value.
*/
! #define AN_MAX_DATALEN512
struct an_req {
u_int16_t an_len;
--- 63,69
* data, which is 240 words long, so 256 should be a safe
* value.
*/
! #define AN_MAX_DATALEN4096
struct an_req {
u_int16_t an_len;
***
*** 261,267
u_int32_t an_uptime_usecs;/* 0x178 */
u_int32_t an_uptime_secs; /* 0x17C */
u_int32_t an_lostsync_better_ap; /* 0x180 */
! u_int32_t an_rsvd[10];
};
/*
--- 261,267
u_int32_t an_uptime_usecs;/* 0x178 */
u_int32_t an_uptime_secs; /* 0x17C */
u_int32_t an_lostsync_better_ap; /* 0x180 */
! u_int32_t an_rsvd[15];
};
/*
***
*** 337,342
--- 337,343
u_int8_tan_magic_packet_action; /* 0x98 */
u_int8_tan_magic_packet_ctl;/* 0x99 */
u_int16_t an_rsvd9;
+ u_int16_t an_spare[13];
};
#define AN_OPMODE_IBSS_ADHOC 0x
***
*** 417,422
--- 418,435
charan_ssid3[32];
};
+ struct an_ltv_ssid_entry{
+ u_int16_t an_len;
+ charan_ssid[32];
+ };
+
+ #define MAX_SSIDS 25
+ struct an_ltv_ssidlist_new {
+ u_int16_t an_len;
+ u_int16_t an_type;
+ struct an_ltv_ssid_entry an_entry[MAX_SSIDS];
+ };
+
/*
* Valid AP list.
*/
***
*** 501,507
u_int16_t an_softcaps;/* 0x7C */
u_int16_t an_bootblockrev;/* 0x7E */
u_int16_t an_req_hw_support; /* 0x80 */
! u_int16_t an_unknown; /* 0x82 */
};
/*
--- 514,520
u_int16_t an_softcaps;/* 0x7C */
u_int16_t an_bootblockrev;/* 0x7E */
u_int16_t an_req_hw_support; /* 0x80 */
! u_int16_t an_unknown[31]; /* 0x82 */
};
/*
***
*** 580,586
u_int8_tan_avg_noise_prev_min_db; /* 0x7D */
u_int8_tan_max_noise_prev_min_pc; /* 0x7E */
u_int8_tan_max_noise_prev_min_db; /* 0x7F */
! u_int16_t an_spare[5];
};
#define AN_STATUS_OPMODE_CONFIGURED 0x0001
--- 593,599
u_int8_tan_avg_noise_prev_min_db; /* 0x7D */
u_int8_tan_max_noise_prev_min_pc; /* 0x7E */
u_int8_tan_max_noise_prev_min_db; /* 0x7F */
! u_int16_t an_spare[8];
};
#define AN_STATUS_OPMODE_CONFIGURED 0x0001
Index: sys/dev/an/if_an.c
===
RCS file: /cvs/src/sys/dev/an/if_an.c,v
retrieving revision 1.51
diff -c -r1.51 if_an.c
*** sys/dev/an/if_an.c 28 Jun 2003 06:13:27 - 1.51
--- sys/dev/an/if_an.c 19 Aug 2003 02:41:06 -
***
*** 313,319
device_tdev;
{
struct an_softc *sc = device_get_softc(dev);
! struct an_ltv_ssidlist ssid;
int error;
bzero((char *)ssid, sizeof(ssid));
---
Re: an driver / Cisco Aironet 340 stopped working
Tomi Vainio - Sun Finland writes: | Peter Radcliffe writes: | Tomi Vainio - Sun Finland [EMAIL PROTECTED] probably said: |Peter Radcliffe writes: | Cisco have changed the operation of the card with newer firmware and | havn't released docs on working with the newer firmware. | |I've tried multiple old firmwares and this loader.conf tweak but no |luck yet. Can you say what was the last working firmware? | | I don't have any 340 cards, just 350 cards, so no. | | Firmware files are the same for both cards or that's my thought from | this filename. | | 350-340-PCMCIA-LMC-PCI-v52017.exe I think he is confusing pccard versus mini-pci cards. All pccard cards (4800/340/350) use the same firmware. I have a mix of them. The mini-pci which is currently only a 350 uses totally different firmware. It's the newer 350 firmware that I'm having trouble figuring out how to make it work properly. The older mini-pci firmware works okay. Doug A. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Tomi Vainio - Sun Finland [EMAIL PROTECTED] probably said: I've used my Cisco WLAN with Toshiba Portege 3440 couple years but now it's broken. I just upgraded to new Toshiba Tecra M1 and reinstalled FreeBSD there and now I get an0: record length mismatch -- expected 430, got 440 for Rid ff68 errors. I already tried with old laptop with latest kernel and old kernel from Jun 26th but it's also broken there so I cannot say who long this has been broken. Have you got recent firmware on the cisco card ? The newer windows driver will helpfully upgrade it for you silently. If it has upgraded, downgrade it. The freebsd driver doesn't yet work with the new firmware. Cisco have changed the operation of the card with newer firmware and havn't released docs on working with the newer firmware. P. -- pir[EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
