WLAN find

[casp]

I find SSID on the wireless lan . And when I connect that ssid i cannot ping any ip-addr. WHY?

[[Syntax]]

Most AP's will let you connect to them reguardless of what you enter as a WEP key. If you connected to a WEP enabled AP, without entering a key, or entered the wrong key, that could be one reason.

[TheCotMan]

I find SSID on the wireless lan . And when I connect that ssid i cannot ping any ip-addr. WHY?

SSID found by the client likely means you have associated with an Access Point. This suggests that have started the process to make a layer2 connection.

Ping is ICMP which for arg sake, we'll say live in layer 3/4 (combined). It most commonly requires that you have layer 3/4 information such as an IP address, subnetmask, and some sort of default gateway (router IP address for default route.)

This is where you should look. Find your IP address on the client. Find the IP Address of the DHCP server (which is often the Access Point) then try to ping the IP Address of the access point or at least the DHCP Server.

If you can pick the access point by IP address, how about the gateway that you were assigned?

If so, then how about the DNS you were given by DHCP? Can you ping them?

If you can ping DNS, can you perform lookups of names to IP with nslookup or dig?

Check out and use traceroute or tracert for specific IP addresses.

Possible reasons for this:
Access point is not on the Internet and/or has not Internet Access.
A Filter exists on the client or the Access Point to drop packets
Your Driver for your client sucks.

What I outlined is not a complete list. What it should show you is a list of steps when working on such a problem.

Start with the most basic things. Start with the most basic, first links in a chain.

Verify you are associated. If you have a sniffer, verify your frames show layer 2 communications with associated accesspoint MAC address in the header along with SRC and DST MAC.

When you verify Layer 2, move up to Layer 3/4 between you and only the access point, then move beyond.

Eventually, you may find there is an application layer authentication like as found with things like NoCat, or something else. (The WEP issue was mentioned, so is omitted here)

[converge]

I think this one is quite a bit more simple, since casp did not actually mention needing to get out to the internet for this problem.

1) Check your info. ifconfig/ipconfig and make certain that you have actually placed yourself on the same segment as the physical devices you are trying to ping. this includes making sure that the AP has a good physical connection to your hub/switch (testing to see if you can actually temporarily ping the AP from one of your boxen could be a good idea to verify the AP is set up correctly)

2) Check your AP/client setting. If you have enabled WEP, make sure you have a valid key configured. When you associate (likely via iwconfig) be sure that the AP's MAC address shows up as a solid association between your client and the point. Make sure you are not filtering out any needed protocols throught he AP and make sure that you are actually bridging the connection to your network. Keep in mind that APs are generally dumb bridges that communicate on a hardware level, not routers (generally)

Casp: If I am assuming incorrectly and this is not your wlan, then contact the owner of the wlan and they can help you get connected.

[skroo]

I think this one is quite a bit more simple, since casp did not actually mention needing to get out to the internet for this problem.

While I'm not disagreeing with any of the points mentioned above, the cause of his problem may even be simpler than that. Assuming that he is actually successfully associating with and connecting via the AP, the network he's on could very well be statically-addressed. No DHCP server, no IP address, etc. Granted, it'd be relatively uncommon in a wireless environment for that to be the case, but I have seen it done more than once.

[casp]

I used tool "stumbler".
My wireless device centrino Intel PRO
AP wireless device Cisco
WEP --- disable, and i know MAC address from this tool (stumbler).
How i can will know IP in my situation?

[skroo]

AP wireless device Cisco

There's your answer. It's a Cisco AP, and most likely running (first one's free) LEAP. AFAIK, no other third-party vendors are supporting LEAP in their wireless clients, so you're screwed.

WEP --- disable, and i know MAC address from this tool (stumbler).
How i can will know IP in my situation?

Assuming that LEAP is enabled at the AP, you'll never get one unless you have a LEAP-compatible client.

[casp]

exist emulator protocol LEAP?

[mr_g]

exist emulator protocol LEAP?

AS skroo pointed out, you'll need:
a LEAP-compatible client adapter
(I think the Xircom CreditCard CWE-1120 can be configured for LEAP and
possibly some of the Dell TrueMobile cards as well ( note: there are specific
requirements to get LEAP to work correctly with any client hardware.
So you must ensure you use the specific version of the TrueMobile card,
not all will be LEAP compatible).
and probably client software such as Funk Odyssey
(recently, Cisco began working with other vendors to make their software LEAP
compliant. There are now at least four other RADIUS solutions that support LEAP)

more here:
http://www.lanarchitect.net/Articles/Wireless/index.htm

and more about Odyssey client software:
http://www.xiologix.com/funksofteodyclient.htm

[casp]

Intel Centrino mobile technology also provides third-party security enhancement support for Cisco* Compatible Extensions (such as LEAP and CKIP.)§ With a PC manufacturers' certification, this feature enables interoperability with Cisco Aironet* wireless LAN infrastructure and other Cisco* Compatible* validated products.§ For more information about......


http://www.intel.com/network/connect...ess_mobile.htm

[skroo]

Intel Centrino mobile technology also provides third-party security enhancement support for Cisco* Compatible Extensions (such as LEAP and CKIP.)

*sigh*

Look, this has been explained to you twice already by different people. If they're running LEAP, you need a LEAP-compatible client to connect to the AP. If you don't have one, you won't. It's that simple. Yes, your Centrino will support LEAP, but so will damn near any other platform that a client has been written for. Google is your friend.

[Chris]

Don't connect to APs you aren't authorized to connect to. If you were authorized, the network admin would get you the needed hardware. Thread closed.