linux wireless problem

Yeah, I would recommend aMSN if she is just using MSN.

Just for the recod the `echo "nameserver 208.67.222.222" > /etc/resolv.conf` command I gave you wouldn't return anything, what it basically says is write this into this file. That file defines which servers to use for name lookups, the ip you wrote in there is the ip of the OpenDNS servers, publically available DNS servers for anyone to use.

The fact I have used a single '>' means overwrite the contents of the file, if I had used '>>' then it would append it to the end of the file, in this case we wanted all of the other stuff gone.
Bear in mind DHCP might overwrite this back to use your router so you might need to do it again.
 
Last edited:
thanks
but why is it that it worked through other networks? is it because their routers were directing them to the open dns servers and mine isnt?
could my router or ap be set to do that?

also my next problem is that i cant install anything i download, do i need to get an installer program as there dosent seem to bew one built in?
 
Probably something weird to do with DNS on your setup, i.e. the AP and router combo, if you had a wireless router in one you probably wouldn't have an issue and it's too hard to diagnose the problem without looking at both.

I *think* SUSE uses YAST? You should be able to download the package for YAST then just double click it or alternatively have a read of this:
http://www.linuxforums.org/forum/suse-linux-help/105397-yum-apt-get-equivalent-suse.html
 
thanks skiba.
ive had a quick go at that but it seems very complicated and i dont really know how it all works, why cant it just be like windows were you just download somthing and click to install.
im sure ill get there in the end
 
flash said:
thanks skiba.
ive had a quick go at that but it seems very complicated and i dont really know how it all works, why cant it just be like windows were you just download somthing and click to install.
im sure ill get there in the end
Click to expand...
because it's a better way of doing it than in Windows.

It uses a centralised repository, so you can be sure that you're downloading what you're expecting (as long as you trust the repository) and not some dodgy compromised install.exe from www.dodgysite.com that has been compromised and contains malware.

It also manages dependencies, i.e. if the application foo that you're installing requires version y of application bar but you're running version x, then it'll prompt you to upgrade application bar and do all that for you too.

It can also be run from a console via ncurses, so if for some reason you seriously borked your window manager you can still use YaST to download and install applications, which can be useful to get you back up and running.

Read up on using YaST here and the whole repository-based package management system. Once you've got your head around it you'll much prefer it to the Microsoft way of hoping what you're installing is legit and won't break something else.
 
thanks gareth ill look into that.
i have a new problem now.
after a long time trying i finally got into my ap set up using my mates windows laptop. there is a wizzard for setting up the first time.
when it came to the security bit i selected wpa/wpa2 mixed.
it then asked for a key, i thought it just wanted a random password so i typed in 14 random characters and hit next. it said somthing like uncompatible key.
now i cant access the setup because encryption is now turned on and the key i put in dosent work. if i could get into setup i could do a factory reset.
shall i pop it in the bin?
 
You should be able to do a factory reset if you have physical access to the AP too, as there should be a button that you can depress for a few seconds to force a reset. All of the routers & APs I've used have had that option for exactly this kind of situation.
 
i tried that but it didnt seem to work.
what i have now done is plugged it straight into my pc and have got into setup and retored defaults. at last.

before i try and setup again could someone give any pointers as to what to input this time. here is a bit from the help section...

1、WEP Open: based on WEP Open System protocol.
2、WEP Share:based on WEP share key.
3、WPA_PSK: Support AES,TKIP, 8~63 ASCII characters or 64 HEX character Required to Password.
4、WPA2_PSK: Support AES,A 8~63 ASCII characters or 64 HEX digital Required to Password.
5、WPA_WPA2_Mixed: Support AES,A 8~63 ASCII characters or 64 HEX digital Required to Password.
Key Type: HEX or ASCII

Key Size: WEP-64bits Keywords are equal to 10 HEX digitaless,or 5 ASCII characters. 128bits are equal to 26 HEX digital, or 13 ASCII characters

how confusing is that for someone new to wireless, no wonder there are so many unprotected networks about.

so which one to choose, are they all compatible with linux?
and then what pass key do i put in?

thanks
ashley
 
mixed WPA/WPA2 support would be best, never choose WEP if you can help it.
WEP is horribly broken and can be cracked in minutes, and choose a resonable hard wpa/wpa2 password as its still possible to crack those with dictionary attacks.
something like a longish word and a few numbers perhaps.
 
so it dosent have to be a certain length then, thats what i did last time and it said not compatible. does it matter if i select HEX or ASCII ?

once ive done that should it give me a keycode?
thanks
ashley
 
You must log in or register to reply here.
Back
Top Bottom