Totally confused - eth0, eth1, eth2, no connection

[jankushka]

Re: Totally confused - eth0, eth1, eth2, no connection

my experience (confirmed by attending this forum) is that wep is pretty troublesome.
in any case, it's obsolete and too easy to break, so better go with wpa.
mine works like a charm both in psk and enterprise mode.

as for knetworkmanager and the other tools...
i don't know.
i guess you can try other stuff, but this is the one that should work.
before knetworkmanager i used wlassistant.
then came 7.04 with wpa support and knetworkmanager.
everything worked out of the box for me (well, as soon as intel patched their microcode).
actually, you could simply use iwlist and iwconfig from command line.
or ifdown and ifup...
you don't need the guis.

gutsy beta is no benchmark.
it's beta.
my virtual machine (just upgraded) doesn't even boot anymore...

so...to sum up:
your hardware works alright.
your driver looks alright.
your iwlist scan gives the expected result (on eth2...so that's what you should have in your config file).
your signal is excellent.
sorry, but i don't see why it shouldn't work.

oh, alright, we haven't checked if wpasupplicant is installed...
pls, issue:

dpkg-query -l '*wpa*'

that's something you need to have installed if you want to use wpa.
once you've made sure wpasupplicant is installed,
remove everything from /etc/network/interfaces
and only leave lo, eth0 and eth2 (the rest is useless):

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto eth0
iface eth0 inet dhcp

auto eth2
iface eth2 inet dhcp

make sure your router be set up to use wpa-psk.
make sure you've entered a passphrase for it.
make sure you've set it up to use dhcp.
start your box, log in kde, start knetworkmanager.

if it doesn't work...i don't know...
the only other thing that comes to mind is to remove all security and try and connect.
if that doesn't work either, then at least we know your issue is not the encryption
and you can move from there.

sorry!

[kbunt]

Re: Totally confused - eth0, eth1, eth2, no connection

Wireless SSID Broadcast: - enable or diable?

$ dpkg-query -l '*wpa*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==================-==================-================================================== ==
ii wpasupplicant 0.5.7-0ubuntu2 Client support for WPA and WPA2 (IEEE 802.11i)


I have enabled and configured WPA-PSK in my Linksys WRT54G router but now I'm at the very beginning again (if I use WPA) since I don't know how to configure WPA in Kubuntu! Please don't tell me to use Knetwork Manager unless you tell me how to totally re-install so that it doesn't behave the same. It will NOT allow me to configure using WPA to save my life. When I first tried wireless, I had an elaborate Knetwork Manager that allowed either WEP or WPA but now that is gone for some reason. I can only manually configure and only using WEP. If I try to configure using Knetwork Manager now, it does nothing. Nothing happens. I have to select the icon in the corner and it only lists 'manually configure' as an option along with:
Wired Devices (x)
Manual Configuration
Options
Help
Quit

I think these events would provoke any sane person to totally abandon Kubuntu.

Is this a bug? I am only doing a simple 'Window-sy' process of going through the 'KDE start menu' (not sure what to call it) and try to start Knetwork Manager. But, nothing happens. I have to go to the icon.

Perhaps, there is another program to use? Or I can forget having wireless with this device and Kubutu?

This doesn't help?:
iwconfig gives:
eth2 IEEE 802.11b/g ESSID:"petenet" Nickname:"zd1211"
Mode:Managed Frequency:2.437 GHz Access Point: Invalid
Bit Rate=1 Mb/s
Link Quality=91/100 Signal level=35/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

My /etc/network/interfaces file now looks like:

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto eth0
iface eth0 inet dhcp

auto eth2
iface eth2 inet dhcp
wireless-essid namenet
wireless-key s:50C8DC1825

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

[kbunt]

Re: Totally confused - eth0, eth1, eth2, no connection

Sorry to doublepost but my only idea left is to try installing WICD but would that work on KDE?

I tried to install it via dpkg but I was left with this msg:
# dpkg -i wicd_1.3.4-all.deb
Selecting previously deselected package wicd.
dpkg: regarding wicd_1.3.4-all.deb containing wicd:
wicd conflicts with network-manager
network-manager (version 0.6.4-6ubuntu7) is installed.
dpkg: error processing wicd_1.3.4-all.deb (--install):
conflicting packages - not installing wicd
Errors were encountered while processing:
wicd_1.3.4-all.deb

I then looked at Adept Manager and the requirements/requests include conflicts with three programs:
network-manager (daemon)
wifi-radar (not installed anyway so no prob. there?)
gt--something or other... I forget but those were the three 'conflicts.'

Would it hurt to try this or will this ultimately fail? Anyone know? I don't want to break my connection but maybe I don't need those three programs?

Anyone try wicd in Kubuntu?

[Snowhog]

Re: Totally confused - eth0, eth1, eth2, no connection

Found this Googling. It's a consolidated list of links based on my Google search of
feisty 7.04 wireless wpa howto Something may be helpful in this, maybe not.
wireless+HOWTO

[kbunt]

Re: Totally confused - eth0, eth1, eth2, no connection

Nope, sorry, it's of no help. Most of the links are relative to ndiswrapper.

Linux is just not ready for wireless unless you have a pci card and even then, it's trial and error. But, for all the usb adapters out there, Linux is way behind.

[jankushka]

Re: Totally confused - eth0, eth1, eth2, no connection

are you able to connect without wireless security?
'cause that would be helpful.
at least you would know you can connect and it's just the encryption thing that causes troubles.
on the contrary, if you can't connect, then, well, maybe the problem is elsewhere...

Wireless SSID Broadcast: - enable or disable?

it has to be set to broadcast on the router.
setting it to non-broadcast causes troubles (and it's useless anyway).

I have enabled and configured WPA-PSK in my Linksys WRT54G router but now I'm at the very beginning again (if I use WPA) since I don't know how to configure WPA in Kubuntu...

well, that's the whole point, isn't it?
there's nothing to do in kubuntu in order to configure wpa.
maybe that's your trouble...you're trying to do too much...
just kidding.
but, yeah...
once you've cleaned /etc/network/interfaces as i suggested in my previous post
actually, you should be able to connect even if your interfaces file simply looked like this:

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

once you've started knetworkmanager, you should see the wireless networks available
(if iwlist picks them up, knetworkmanager will have to pick them up too)
and by clicking on your network, knetworkmanager should ask you your password (which
gets saved in the password wallet, if you use it) and that's it...
but it won't work unless you remove the wireless directives from the interfaces file.

and, if it still doesn't work, then, two possibilities:
a) try a fresh install (there's a good chance you'll have messed up your installation, anyway, by now)
b) ditch it (it doesn't make sense to waste all this time for a stupid wireless connection).
in case of b, then come back once 7.10 is out and stable and try again.

if you want to try and uninstall knetworkmanager (or anything else) and reinstall it,
you can do it by issueing:

sudo apt-get autoremove knetworkmanager --purge

there's a point and click way of doing it, of course, but is this a lot faster.