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
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 ?
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
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
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
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
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
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
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
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
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
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
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.
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
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.
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
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.
|
|
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
18 matches
Mail list logo
