Can't PING in ad-hoc mode - Networking

This is a discussion on Can't PING in ad-hoc mode - Networking ; Hi everyone, I'm trying to set up a wireless ad-hoc network between two colibri linux boards (pxa270 arm processor) running linux 2.6.12.4. To do so, I'm using two DWL-G122verC1 USB dongles and the rt73 wireless driver which can be downloaded ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Can't PING in ad-hoc mode

  1. Can't PING in ad-hoc mode

    Hi everyone,

    I'm trying to set up a wireless ad-hoc network between two colibri
    linux boards (pxa270 arm processor) running linux 2.6.12.4. To do so,
    I'm using two DWL-G122verC1 USB dongles and the rt73 wireless driver
    which can be downloaded here: http://www.ralinktech.com/ralink/Hom...ort/Linux.html
    ..

    The problem is that I can't have my two linux boards ping each other
    (100% packet loss) even though I believe everythong else is set
    properly. They are using the same channel (1) and there is no firewall
    issue.

    Any ideas? I'm really stuck here

    Thanks,
    Sabine

    Linux board 1:
    --------------------
    >iwconfig rausb0

    rausb0 RT73 WLAN ESSID:"MAVnet"
    Mode:Ad-Hoc Frequency=2.412 GHz Cell: D6:AA:430:266
    Bit Rate=11 Mb/s
    RTS thrff Fragment thrff
    Encryption keyff
    Link Quality=83/100 Signal level:-56 dBm Noise level:-79
    dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    >ifconfig rausb0

    rausb0 Link encap:Ethernet HWaddr 00:19:5B:6D7:65
    inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:
    255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:5702 errors:0 dropped:0 overruns:0 frame:0
    TX packets:487 errors:0 dropped:80 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:510673 (498.7 KiB) TX bytes:46528 (45.4 KiB)

    >route

    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref
    Use Iface
    192.168.0.0 * 255.255.255.255 UH 0 0
    0 rausb0

    Linux board 2:
    --------------------

    >iwconfig rausb0

    rausb0 RT73 WLAN ESSID:"MAVnet"
    Mode:Ad-Hoc Frequency=2.412 GHz Cell: D6:AA:430:266
    Bit Rate=11 Mb/s
    RTS thrff Fragment thrff
    Encryption keyff
    Link Quality=87/100 Signal level:-52 dBm Noise level:-79
    dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    >ifconfig rausb0

    rausb0 Link encap:Ethernet HWaddr 00:19:5B:6D7:38
    inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:
    255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:20357 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1631 errors:0 dropped:429 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2331371 (2.2 MiB) TX bytes:168872 (164.9 KiB)

    >route

    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref
    Use Iface
    192.168.0.0 * 255.255.255.0 U 0 0
    0 rausb0


  2. Re: Can't PING in ad-hoc mode

    On Thu, 31 May 2007 08:04:20 -0700, sabine.hauert wrote:

    > I'm trying to set up a wireless ad-hoc network between two colibri
    > linux boards (pxa270 arm processor) running linux 2.6.12.4. To do so,
    > I'm using two DWL-G122verC1 USB dongles and the rt73 wireless driver
    > which can be downloaded here: http://www.ralinktech.com/ralink/Hom...ort/Linux.html
    > .
    >
    > The problem is that I can't have my two linux boards ping each other
    > (100% packet loss) even though I believe everythong else is set
    > properly. They are using the same channel (1) and there is no firewall
    > issue.
    >
    > Any ideas? I'm really stuck here



    > Linux board 1:

    ...
    >>route

    > Kernel IP routing table
    > Destination Gateway Genmask Flags Metric Ref Use Iface
    > 192.168.0.0 * 255.255.255.255 UH 0 0 0 rausb0


    ^ That Genmask is wrong and may well be the source of your problem. It
    should be 255.255.255.0 as on board 2. Looks like you did a 'route add
    -host 192.168.0.0 rausb0' instead of 'route add -net 192.168.0.0 netmask
    255.255.255.0 rausb0'.



    > Linux board 2:

    ...
    >>route

    > Kernel IP routing table
    > Destination Gateway Genmask Flags Metric Ref Use Iface
    > 192.168.0.0 * 255.255.255.0 U 0 0 0 rausb0



    Everything else looks to be in order - the devices both have good link
    quality and are sending and receiving packets, presumably with each other.
    I'd guess board 1 is unable to route packets correctly to board 2 due to
    the bad mask.



    --


    --
    Posted via a free Usenet account from http://www.teranews.com


+ Reply to Thread