[driverloader] Netgear 511v2 (Marvell chipset)

[Linuxant support (Jonathan)]

Hi,

this is the first time I see this message from the 'ping' command:

---
wrong data byte #52 should be 0x34 but was 0x0
#8      8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
20 21 22 23 24 25 26 27
#40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 0 0 0 0
---

It could be a problem with either installed Windows XP driver of 
DriverLoader. You could try with different versions of the Windows XP 
driver to see if there is a difference. It is also possible that there 
is a packet altering software on your network and it changed the ping 
reply packets.

For the problem that you are unable to reach machine outside of the 
network, it is quite possible that this is a IP routing issue. According 
to the dump you have sent us, you are running Fedora Core 3 and both 
eth0 (an ethernet interface) and eth1 (the wireless interface driven by 
DriverLoader) are on the same network (192.168.67.0/24).

On distributions based on Red Hat Linux such as Fedora Core 3, when you 
will bring up the wireless interface, the default route will still be 
the ethernet interface since both interfaces are configured to use the 
same network. You could try to bring down the ethernet interface with 
the 'ifdown eth0' or manually alter the routing table with the 'ip 
route' command and try again to ping other machines outside your LAN.

Regards,


Jonathan
Technical specialist / Linuxant
www.linuxant.com
support at linuxant.com



Christian Kalkhoff wrote:
> Hi list,
> 
> i bought a Netgear 511v2 32 bit pcmcia card some days ago. I found 
> information about that card and hoped it was prism chipset. But it 
> isn´t. No problem, i thought. I will use driverloader. :)
> BUT: I cannot use the card. I set up my AP and tried to ping it. I use 
> no encryption at all. When pinging the AP i get
> 
> [root at asterix ~]# ping 192.168.67.2
> PING 192.168.67.2 (192.168.67.2) 56(84) bytes of data.
>  From 192.168.67.35 icmp_seq=0 Destination Host Unreachable
>  From 192.168.67.35 icmp_seq=1 Destination Host Unreachable
>  From 192.168.67.35 icmp_seq=2 Destination Host Unreachable
> 64 bytes from 192.168.67.2: icmp_seq=4 ttl=64 time=1.17 ms
> wrong data byte #52 should be 0x34 but was 0x0
> #8      8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
> 20 21 22 23 24 25 26 27
> #40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 0 0 0 0
> 64 bytes from 192.168.67.2: icmp_seq=5 ttl=64 time=0.910 ms
> wrong data byte #52 should be 0x34 but was 0x0
> #8      8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
> 20 21 22 23 24 25 26 27
> #40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 0 0 0 0
> 64 bytes from 192.168.67.2: icmp_seq=7 ttl=64 time=0.976 ms
> wrong data byte #52 should be 0x34 but was 0x0
> #8      8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
> 20 21 22 23 24 25 26 27
> #40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 0 0 0 0
> 64 bytes from 192.168.67.2: icmp_seq=8 ttl=64 time=1.16 ms
> wrong data byte #52 should be 0x34 but was 0x0
> #8      8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
> 20 21 22 23 24 25 26 27
> #40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 0 0 0 0
> 64 bytes from 192.168.67.2: icmp_seq=9 ttl=64 time=21.5 ms
> wrong data byte #52 should be 0x34 but was 0x0
> #8      8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
> 20 21 22 23 24 25 26 27
> #40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 0 0 0 0
> 64 bytes from 192.168.67.2: icmp_seq=10 ttl=64 time=106 ms
> wrong data byte #52 should be 0x34 but was 0x0
> #8      8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
> 20 21 22 23 24 25 26 27
> #40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 0 0 0 0
> 64 bytes from 192.168.67.2: icmp_seq=12 ttl=64 time=1.23 ms
> wrong data byte #52 should be 0x34 but was 0x0
> #8      8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
> 20 21 22 23 24 25 26 27
> #40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 0 0 0 0
> 64 bytes from 192.168.67.2: icmp_seq=13 ttl=64 time=2.21 ms
> wrong data byte #52 should be 0x34 but was 0x0
> #8      8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
> 20 21 22 23 24 25 26 27
> #40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 0 0 0 0
> 64 bytes from 192.168.67.2: icmp_seq=14 ttl=64 time=1.17 ms
> wrong data byte #52 should be 0x34 but was 0x0
> #8      8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
> 20 21 22 23 24 25 26 27
> #40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 0 0 0 0
> 64 bytes from 192.168.67.2: icmp_seq=15 ttl=64 time=1.12 ms
> wrong data byte #52 should be 0x34 but was 0x0
> #8      8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
> 20 21 22 23 24 25 26 27
> #40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 0 0 0 0
> 64 bytes from 192.168.67.2: icmp_seq=16 ttl=64 time=1.06 ms
> wrong data byte #52 should be 0x34 but was 0x0
> #8      8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
> 20 21 22 23 24 25 26 27
> #40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 0 0 0 0
> 
> --- 192.168.67.2 ping statistics ---
> 19 packets transmitted, 11 received, +3 errors, 42% packet loss, time 
> 18016ms
> rtt min/avg/max/mdev = 0.910/12.641/106.477/30.239 ms, pipe 4
> 
> Pinging anything behind the AP (in the local network or behind) doesn´t 
> even return with a message. I attached a diag file, so you can see my 
> system configuration. I hope that it is an easy to fix issue, but since 
> i haven´t yet found anything regarded on the net, i think it isn´t.
> 
> I hope anybody has a clue about that.
> 
> Regards.
> Christian
> 
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader