wireless connect issue
Ok, so ive got a wireless network setup to share my connection, unfortunately it only supports wep, so im lumbered with that. The connection works (i can use my phone on it), but when I come to hook up my lappy to it dhcp just wont play ball. I can connect unencrypted, dhcp works fine then, and im pretty sure my wep settings are fine, so im stumped.
Ive tried using wlassistant, which finds my network (full signal) and I put the correct settings in there. All seems to go well, but dhcp doesnt get an IP so the connection fails.
Ive also tried the iwconfig way(manually), using these commands:
iwconfig ath0 mode managed channel 6 key restricted s:<my key> essid <my essid>
iwconfig ath0 ap <my AP mac>
then both of these:
dhcpcd -nd ath0
dhclient ath0
Both fail, dhclient claims there were no DHCP offers, but my phone gets connected in a few seconds, so I know it works.
iwconfig for my ath0 interface here: http://pastebin.com/m742eca52
Any help would be appreciated.
Well, it's unlikely that you have one of the newer Atheros cards that still has issues despite the patches on Madwifi. Most likely, it's just a quirk with something other than your wireless connection, whose iwconfig looks fine. Try bringing down any other interfaces (so just ath0 / wifi0 / wlan0 and lo are up), then try the dhcp request again. If that doesn't work, try specifying the default gateway for ath0 in a normal route command; if that doesn't work, specify the route specifically for that interface. If none of that works, see if you can ping anything on the internal network.
On Ubuntu Hardy Heron (8.04) athreos cards were alot of trouble for me, But I solved it by going into the router and just editing the setting in that.
this may help if you can follow it loosely.
http://www.lycoming.edu/acad/linksys%20wireless-g%20broadband%20router.htm
Also, if you set the router to accept you laptops MAC address that may help, But I'm not so sure if that will "fix" your problem.
I had a similar problem with my Ubuntu…What I do now is I use KWifiManager and Wireless Assistant to connect to WEP networks.
Basically you set up KWifiManager with your info and then set up Wireless Assistant too and you have both open while trying to connect via Wireless Assistant. For me, if I close one and keep the other open it doesn't work. Don't ask me why, I have no idea and I've never felt the need to figure it out but it works. I had a friend with a similar problem and this solution worked on his laptop too.
spyware wrote: [quote]ice_sd wrote: I had a similar problem with my Ubuntu…
snip
I have no idea and I've never felt the need to figure it out
Good job on solving your problems. Anyways, I'll be referring to this post for "Ubuntu-people" proof.
Thanks ice_sd![/quote]
Hey, at least I solved it on my own without bothering cocky assholes such as yourself for help.
ice_sd wrote: Hey, at least I solved it on my own without bothering cocky assholes such as yourself for help.
When I said "good job", I actually meant "good job". I was being sincere, not sarcastic. I see how you got those two mixed up though. (Again, I'm not being sarcastic here, -really-!).
Aaaaaaanyway, keep on posting quality stuff ice!
@ice - Thanks for the input, but ive tried that as well unfortunately, as well as using KDE control center to load the settings on start, I wanted to take the non-GUI way, as I understand this stuff pretty well, and would love to get to the bottom of whats gone wrong here.
Saying that I am still utterly stumped :angry:
Yeah, all but adding the default gateway, purely coz im not sure what IP it will be, when I connect my phone I get a 10.0.1.x number, but my ifconfig for my wireless says a 169.x.x.x number. I know the command for adding a default route, so il try both and see what happens. Never normally had to do this before though, including the same connection, just without wep.
A 169.254.x.x address means that your DHCP requests aren't getting a response… but, we know that already. The reasoning behind my post was as follows:
Sometimes, it seems as if the traffic wants to go out of the Ethernet connection only if both Ethernet and wireless are up. Bringing the Ethernet interface down solves that, but may remove some of the default routes associated with it (including the default gateway).
… Before I get too far along: You don't know what IP your gateway will have? How on Earth is it handing out DHCP requests, then? If it's not, what is? How are you getting a connection on your phone if there's no device to serve as a gateway with a set IP?
Okay, two questions about your topology:
- Is the iMac routing to outside your network as well, or just sharing a connection over wireless? (What device is taking the connection from the outside and passing it through to your network?)
- What device is a DHCP server on your network?
Can't really figure anything else out until I know both of those.
Seems like it. Find the IP of the iMac, then assign a static IP just a bit lower/higher than that to your laptop. Try to connect to the AP again and see if that allows you to ping/connect to anything. We'll just go ahead and try to eliminate DHCP problems to narrow down the issue. Also, try pinging the IP of the iMac after you've done that; you won't need to assign a default gateway to ping the 1st hop away from your laptop.
Also, find the MAC (no pun intended) address of the iMac's wireless NIC and assign that as the "ap" parameter when you do iwconfig. So, total, try specifying the essid, mode (managed), ap, key (open/restricted and the key), and IP / mask (with ifconfig) for the WNIC on your laptop.
Post back with how that all goes.