Next-in-Thread Next Message

Question Can't ping Wavelan/IEEE in ad-hoc mode 

Forum: PCMCIA Wireless Network Adapter Issues
Date: 2000, Jun 22
From: Alan Ostroff alan

I'm trying to setup a Wavelan/IEEE card in a linux box already configured with IP Masq and an NE2000 card and communicate with a stand alone WIN95 laptop using the same card.

I've configured the WIN95 Wavelan driver with "ANY" as the Network Name and selected Ad-Hoc demo mode.  It's IP address is 192.168.0.5.  To test it, I configured another WIN95 laptop with the same config and was able to ping each machine.

Back to Linux... I've removed the comments and modified the wireless.opts file to:

# Lucent Wavelan IEEE
# Note : wvlan_cs driver only, and version 1.0.4+ for encryption support
*,*,*,00:60:1D:*)
    INFO="Wavelan IEEE example (Lucent default settings)"
    ESSID="ANY"
    MODE="ad-hoc"
    RATE="auto"
    ;;
                                                                                
This seems to work fine because when I run iwconfig (wireless tools.20) I get:

lo        no wireless extensions.
 
eth0      no wireless extensions.
 
ppp0      no wireless extensions.
 
wvlan0    IEEE 802.11-DS  ESSID:""  Nickname:"shell1.alan.com"
          Frequency:2.422GHz  Sensitivity:1/3  Mode:Ad-Hoc
          Access Point: 00:00:00:00:00:00
          Bit Rate:11Mb/s   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  invalid crypt:0  invalid misc:0    

Strangly enought, when I run ifconfig wvlan0 up to bring up the wireless interface, I see:

eth0      Link encap:Ethernet  HWaddr 00:80:AD:A7:FD:32
          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:782 errors:0 dropped:0 overruns:0 frame:0
          TX packets:890 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
 
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:127 errors:0 dropped:0 overruns:0 frame:0
          TX packets:127 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
 
ppp0      Link encap:Point-to-Point Protocol
          inet addr:213.36.65.189  P-t-P:212.155.245.193  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:917 errors:32 dropped:0 overruns:0 frame:32
          TX packets:979 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
 
wvlan0    Link encap:Ethernet  HWaddr 00:60:1D:F1:51:24
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0  

And no IP address is identified for the wvlan0 interface.  However, if I run netcfg and reactive the wvlan0 interface, I get:

wvlan0    Link encap:Ethernet  HWaddr 00:60:1D:F1:51:24
          inet addr:192.168.0.4  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
  
I can ping 192.168.0.4 sucessfully from the linux box. Shouldn't the IP address be assigned to the interface when I run ifconfig wvlan0 up?

Anyway, the real problem is that even at this stage, if I ping from the linux box to 192.168.0.5 I get nothing.  If I ping from the WIN95 box to 192.168.0.4 I get nothing, however if I run iwconfig I see the rx packet counter increase. 

Any ideas?
Thanks,
Alan

Next-in-Thread Next Message

Messages Inline: 1 All Outline: 1 2 All

1. None Looks like it might be a routing issue by David Hinds, 2000, Jun 22
1. Sad Routing?? by Alan Ostroff, 2000, Jun 22
2. Idea Hum... ad-hoc in config.opts might help... by Jean Tourrilhes, 2000, Jun 22
1. Question Ad-hoc mode by Alan Ostroff, 2000, Jun 23
(_ None Jean is leading you astray on this one by David Hinds, 2000, Jun 23
3. Ok Success! by Alan Ostroff, 2000, Jun 23

Add Message to: "Can't ping Wavelan/IEEE in ad-hoc mode"

Members Subscribe Admin Mode Show Frames Help for HyperNews at pcmcia-cs.sourceforge.net 1.10