Tim McGaha - 2005-01-23

I am having trouble with both rc3 and rc4. RC2 works fine. Here is what I am getting in both dmesg and from dhclient wlan0

[root@TIMSFC3 ndiswrapper-1.0rc4]# dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

/sbin/dhclient-script: configuration for wlan0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 47: wlan0: No such file or directory
Listening on LPF/wlan0/00:0d:88:c8:69:e9
Sending on LPF/wlan0/00:0d:88:c8:69:e9
Sending on Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
ip length 576 disagrees with bytes received 1482.
accepting packet with data after udp payload.
DHCPNAK from 192.168.1.1
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
ip length 576 disagrees with bytes received 1482.
accepting packet with data after udp payload.
DHCPOFFER from 192.168.1.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
ip length 576 disagrees with bytes received 1482.
accepting packet with data after udp payload.
DHCPACK from 192.168.1.1
/sbin/dhclient-script: configuration for wlan0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 47: wlan0: No such file or directory
bound to 192.168.1.103 -- renewal in 34535 seconds.

diswrapper version 1.0rc2 loaded (preempt=no,smp=no)
ndiswrapper (wrapper_init:1494): loadndiswrapper failed (1792); check system log for messages from 'loadndisdriver'
ndiswrapper version 1.0rc4 loaded (preempt=no,smp=no)
ndiswrapper: driver netr33x (D-Link,10/30/2003,5.162.1030.2003) added
PCI: Found IRQ 9 for device 0000:00:10.0
PCI: Sharing IRQ 9 with 0000:00:07.2
ndiswrapper: using irq 9
divert: allocating divert_blk for wlan0
wlan0: ndiswrapper ethernet device 00:0d:88:c8:69:e9 using driver netr33x
wlan0: encryption modes supported: WEP, WPA with TKIP, WPA with AES/CCMP
wlan0: no IPv6 routers present

I get an ip address but it looks like theres a problem with the mtu or packet size??