|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Wireless Questions about wireless networking setup, use, and wireless specific applications |
![]() |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
IP addresses change (though I seem to usually get 26). MAC is used to limit access to the WAP. MAC is used to set trusted workstations. IP reservation is not being used.
|
|
|||
|
Still no dice. I turned off IPv6, rebooted and still no change. Exact same problem. No access to the WAN, but I get data from the router.
I also tried booting live disk from Ubuntu, and had the same problem. |
|
|||
|
Ouch. Ok. Thanks for the attempt.
|
|
||||
|
It's just that you said your hardware was ok. We have not looked at what you have. But from what you say it does seem to be working. It might be worth giving us the info.
__________________
Box: openSUSE 11.2 | (KDE4.3.3) | M2N4-SLI | AMD 64 X2 5200+ | nVidia 8500GT | 4GB RAM Lap: openSUSE 11.2 | Celeron 550 | (KDE4.3.3)"3" | Intel 965 GM | Lenovo R61e | 3GB RAM |
|
|||
|
Quote:
|
|
||||
|
Look here. Some of the info here is a little outdated. But I notice a comment re: 11.1 works out of the box ( I think you can ignore any reference to ndiswrapper, which uses xp drivers)
HCL/Network Adapters (Wireless) - openSUSE It certainly sounds like your device is working properly. I think I did say, I have never worked in quite the same fashion as you describe.
__________________
Box: openSUSE 11.2 | (KDE4.3.3) | M2N4-SLI | AMD 64 X2 5200+ | nVidia 8500GT | 4GB RAM Lap: openSUSE 11.2 | Celeron 550 | (KDE4.3.3)"3" | Intel 965 GM | Lenovo R61e | 3GB RAM |
|
|||
|
Choosing the correct kmp-package for your installation - openSUSE Forums
Software.openSUSE.org - compat-wireless
__________________
“Never attribute to malice that which can be adequately explained by stupidity.” (R.J. Hanlon) |
|
|||
|
Hello
I read this thread and might have an idea, well actually I do have an idea and here it is. This chap is geting info from his ap, just like he says. But he can't get any where past it. I suspect this means he needs to add a default gateway in the routing table. Usually this is done with the connection to the ap. So try this. Become root, use sudo -s or what ever you like, and run route from the command line (don't freak at a command line it is actually very nice). When route runs it will show you the routing table. Usually the last line will have a header named default and in the column next to it will be the gateways IP. If you do not have a defalt gateway you will never connect. Also if the IP is incorrect you will never connect. Sometimes route take a few moments to finish so be patient and wait for it. To add a defalt route use something like this: route add default gw mango-gw (This was taken right out of the man page, you should read it !!! ) I would change the "mango-gw" to the ap's IP. to use mango-gw your DNS has to be working and you can't get to it the way you are, so use the IP. A thought just poped into my head (amazing it still works after all it's been through). Maybe your sysadmin has set the defalt gateway to a different IP then your ap. Some sort of security attempt. Give him/her a call and chat about routing tables. He/She will bable on for hours about them. With all that said this might not be your problem and this is just wasted bandwidth. But from what I read I suspect you have a routing problem. Why you have a routing problem, probably it's the fault of the ap or I don't know but this should help if the defalt gateway is wrong in the routing table. |
![]() |
|
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|