Announcement

**Snowhog** · Sep 25, 2007, 10:24 PM

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

Not using wireless (yet), but you may find help at this link: Wireless connectivity solution for 7.04

**jankushka** · Sep 26, 2007, 03:36 AM

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

forgive my asking...
is there a reason for wanting to set a static ip address?

**kbunt** · Sep 26, 2007, 10:16 AM

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

If there is more than one computer on the network, you might want a static ip?

**jankushka** · Sep 27, 2007, 04:06 AM

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

for the sake of testing/debugging could you pls open up a konsole
and post back here the result of:

Code:

ifconfig -a

which gives the list and configuration of the actual network interfaces

Code:

cat /etc/network/interfaces

which renders the content of the system's network interfaces' configuration file

thanks.

**kbunt** · Sep 27, 2007, 06:01 AM

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

# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:13

4

9:2E:45
inet addr:192.168.1.90 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:d4ff:fed9:2e45/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2887 errors:0 dropped:0 overruns:0 frame:0
TX packets:2387 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3258709 (3.1 MiB) TX bytes:414332 (404.6 KiB)
Interrupt:19 Base address:0xa000

eth2 Link encap:Ethernet HWaddr 00:17:3F:B1:EE:F2
inet6 addr: fe80::217:3fff:feb1:eef2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:12267 overruns:0 frame:0
TX packets:456 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:35962 (35.1 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:848 errors:0 dropped:0 overruns:0 frame:0
TX packets:848 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:77344 (75.5 KiB) TX bytes:77344 (75.5 KiB)

# cat /etc/network/interfaces
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

iface eth0 inet static
address 192.168.1.90
netmask 255.255.255.0
gateway 192.168.1.1

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet static
wireless-essid namenet
address 192.168.1.90
netmask 255.255.0.0
gateway 192.168.1.1

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

auto eth0

**jankushka** · Sep 27, 2007, 09:57 AM

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

it's actually kind of funny that you have an eth1 in dmesg and no eth1 in ifconfig.
i would:
a) forget about "system settings -> network settings"
b) quit knetworkmanager
c) if you used the wallet manager, remove the knetworkmanager's entry in there
d) move the current your-user's knetworkmanager's rc file out of the way

Code:

cd
cd .kde/share/config
mv knetworkmanagerrc knetworkmanagerrc.orig

e) edit your /etc/network/interfaces

Code:

sudo nano /etc/network/interfaces

and have it look as follows (let's try dynamic setup first)

Code:

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

then save and exit

f) restart knetworkmanager
g) finally log out of kde and restart your box (we could do otherwise, but this is faster)

see if this changes anything...

**kbunt** · Sep 27, 2007, 08:18 PM

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

Thanks for the instructions, jankushka! Especially quick, too. I actually learned how to edit but I'm not 100% sure of your (c) and (d) steps. I'll google and look into it but if you don't mind, it would be great for a bit more instructions and info. I'm especially in newbie land when it comes to step (d).

The rest I should be fine with trying.

c) if you used the wallet manager, remove the knetworkmanager's entry in there
d) move the current your-user's knetworkmanager's rc file out of the way

**jankushka** · Sep 28, 2007, 09:42 AM

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

Originally posted by kbunt

I'll google and look into it but if you don't mind...

go ahead, no problems

Originally posted by kbunt

...it would be great for a bit more instructions and info

yeah, you're right.
sorry.
i take things for granted.
i shouldn't.

now then...
point c) refers to deleting the entry for knetworkmanager from the passwords wallet.
it's just for cleaning, really.
it shouldn't have anything to do with your issue.
and, in principles, when we get knetworkmanager to ask you the wpa password again,
it should be saved back in the wallet.
so, it shouldn't be a big deal...

point d) refers to knetworkmanager's user's specific configuration (rc) file.
again it's for cleaning purposes.
as you start up knetworkmanager again, a new (clean) rc should be written out there.
anyway, by using the mv command, we're not deleting the current config file.
we're just moving (i.e., renaming) it.
and in case of troubles we can just rename it back and have things back as they were.

so, in theory, we're not doing anything dodgy...in theory...

what i'm hoping to achieve is have a clean environment, with a simple dhcp setup,
for knetworkmanager to operate with...

what puzzles me is the eth1/eth2 thing.
you should really have an eth1, not an eth2.
in the network config file i gave you i put both.

you should also make sure your wireless netid is broadcast by the router.
apparently, setting it to non-broadcast sometimes causes troubles (independent from the os).

also, check that the router be happy with using dhcp.
EDIT: this means checking your router configuration and make sure it's set to dhcp.

think it's all for now...

**kbunt** · Sep 29, 2007, 05:11 PM

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

I followed your instuctions but with no working result as far as I could tell. So, I tried ifup and ifdown commands with eth2. Perhaps, that is the wrong approach? Anyway, now /etc/network/interfaces looks like this:

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp
wireless-essid *name*net
wireless-key s:50C8DC1825

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

*where "namenet" represents name I gave in WEP router settings*
Two things, though. One, I would prefer getting static IP to work eventually due to 2 or more computers on the network. But, dhcp is okay for now until I get to the root of the problem.

Two, I can't help but wonder if part of it has to do with the eth1 and eth2 situation. I don't understand it but how come wireless is being shown to exist on both? Or that is how it appears to me. I don't get it.

The only other possibility which I fear is a genuine problem with the hardware. Although, it might not be, I am not ruling that out just yet.

I made sure the device is still being recognized and shows up with eth1.
$ dmesg | grep 1211
[ 18.100000] zd1211rw 2-3:1.0: firmware version 4725
[ 18.148000] zd1211rw 2-3:1.0: zd1211b chip 050d:705c v4810 high 00-17-3f AL2230_RF pa0 g--N
[ 18.148000] zd1211rw 2-3:1.0: eth1
[ 18.196000] usbcore: registered new interface driver zd1211rw

**jankushka** · Sep 29, 2007, 06:40 PM

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

Originally posted by kbunt

I followed your instuctions but with no working result as far as I could tell. So, I tried ifup and ifdown commands with eth2. Perhaps, that is the wrong approach?

of course you can do that (does it say anything, btw?).
but with knetworkmanager and everything set up alright, that shouldn't be necessary.

Originally posted by kbunt

*where "namenet" represents name I gave in WEP router settings*

...thought we were trying wpa

Originally posted by kbunt

One, I would prefer getting static IP to work eventually due to 2 or more computers on the network. But, dhcp is okay for now until I get to the root of the problem.

for now dhcp should make things easier.
at least we can rule out one part of the connection mechanism.
just make sure your router is set up so as to give out ip addresses with dhcp.

Originally posted by kbunt

Two, I can't help but wonder if part of it has to do with the eth1 and eth2 situation. I don't understand it but how come wireless is being shown to exist on both? Or that is how it appears to me. I don't get it.

you have a usb thing.
it could well be it gets assigned to eth2.
but let's see if and where we get a connection from.
pls, issue:

Code:

sudo iwlist scan

and see what is says.
the iwlist commands gets info from the interfaces.
the scan option will give you info about the access points it finds in the range.
this should give us a clue as to whether or not your wireless card is at least up and running ok.
a working and properly configured wireless interface will respond something like this:

eth1 Scan completed :
Cell 01 - Address: 00:0F:CC:2B

5:60
ESSID:"azazel"
Protocol:IEEE 802.11bg
Mode:Master
Channel:7
Encryption key

n
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Quality=61/100 Signal level=-70 dBm Noise level=-77 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Extra: Last beacon: 160ms ago

as you can see, i have wpa2 with psk working alright.

we could also check that the kernel have the wireless stuff loaded alright.
pls, also issue:

Code:

lsmod | grep 80211

lsmod will list all the currently loaded kernel (driver) modules.
and we're looking for stuff that has to do with wireless.

Originally posted by kbunt

The only other possibility which I fear is a genuine problem with the hardware. Although, it might not be, I am not ruling that out just yet.

easy to test: try your setup with windoze.
or install a fresh linux on a separate partition.
a basic installation shouldn't take you more than 45 minutes.

**kbunt** · Sep 30, 2007, 01:31 PM

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

Originally posted by jankushka

of course you can do that (does it say anything, btw?).
but with knetworkmanager and everything set up alright, that shouldn't be necessary.

It shouldn't. I'm getting really frustrated, though, because some people say to not even use knetwork manager. Some say it has bugs. Some say to use wlassistant, some say use kwikimanager, some say use WICD (can only use in Ubuntu since it's Gnome?) and so on... Arghhhhhhhh...

Originally posted by jankushka

...thought we were trying wpa

I'd MUCH rather use WPA if possible. I thought WEP might be easier to get working, though. Perhaps, neither is harder than the other to get working or configured? I guess I should concentrate on getting WPA working and only have trials specific to WPA? That's what I want to work anyway. Should I only try for a WPA configuration?

Originally posted by jankushka

for now dhcp should make things easier.
at least we can rule out one part of the connection mechanism.
just make sure your router is set up so as to give out ip addresses with dhcp.

Okay, so WPA and dhcp?

Originally posted by jankushka

you have a usb thing.
it could well be it gets assigned to eth2.
but let's see if and where we get a connection from.
pls, issue:

Code:

sudo iwlist scan

and see what is says.

At the moment, there are '4 cells.' Here's mine:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth2 Scan completed :
Cell 02 - Address: 00:0F:66:E3:4E:90
ESSID:"petenet"
Protocol:IEEE 802.11g
Mode:Master
Channel:6
Encryption key

n
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=100/100 Signal level=94/100
Extra: Last beacon: 144ms ago
It's picking up other access points (in the area?) but I only listed my access point.

Originally posted by jankushka

we could also check that the kernel have the wireless stuff loaded alright.
pls, also issue:

Code:

lsmod | grep 80211

$ lsmod | grep 80211
ieee80211_crypt_wep 6144 1
ieee80211softmac 31232 1 zd1211rw
ieee80211 34760 2 zd1211rw,ieee80211softmac
ieee80211_crypt 7040 2 ieee80211_crypt_wep,ieee80211

Originally posted by jankushka

easy to test: try your setup with windoze.
or install a fresh linux on a separate partition.
a basic installation shouldn't take you more than 45 minutes.

It worked out of the box on Windows 2000. In Windows, I installed a driver from online from Belkin. It just worked. You know that Zydas page with the tar .bz2 files? I think that is the last thing to try unless something I provided above gives any ideas. Other than that, if the bz2 file doesn't help, this darn device looks like it's going to require the dreaded ndiswrapper.

I just downloaded and burned a LiveCD copy of Gutsy KDE and it gives the same behavior. In other words, it doesn't work with a newer version of Kubuntu. :-(

As far as I can tell, almost no USB wireless adapters (for the desktop, anyway) work with Linux out of the box. Not yet.

**Snowhog** · Sep 30, 2007, 01:46 PM

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

I know that you have become (totally?) frustrated. You are posting in two different threads, so following all that has been asked/suggested gets a bit hard to follow. No problem though.

Have you already looked at this post concerning setting up wireless in Kubuntu Feisty Fawn?

**kbunt** · Sep 30, 2007, 01:51 PM

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

Yeah, are you talking about the post in 'Gutsy -> Network Support?' That was an accident. Sorry about that! I meant to post in the Feisty - Nework Support forum. I thought I would have more answers and it was more related to Network Support even though I could have posted in 'New User' section.

I came across that post actually. I've bookmarked it. I'll probably need it if I try to use the Zydas driver files from the web page I found (with updated drivers in .bz2 format). Thanks for asking, though.

**kbunt** · Sep 30, 2007, 04:48 PM

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

Update: I have unzipped/uncompressed the bz2 files and they include READMEs. It looks *super* complicated for a newbie such as myself. I'm not even sure I need the files or if it will work. Anyway, I would like to say I would like to strangle people who say Linux is as easy or easier than Windoze.

I might have reached a dead end with respect to this particular usb wireless device. I will try a few more steps but I'm not expecting much. I'll keep on the look out for claims of a usb device working out of the box. If anyone wants to know (why, I don't know...

...perhaps, curious...perhaps, thinking of whether Belkin is a decent device to consider?) what the READMEs state, here's an abbreviated summary of my own:
Copy the firmware files to /lib/firmware/zd1211 (which I would have to create - mkdir

!? The only dir. in /lib/firmware is '2.6.20-15-generic.' There are no other files or directories that I can see there).

The other README states:
zd1211memtool
Firmware must be installed in /lib/firmware/zd1211
(It gives) 'required command line arguments.'
(There is also a comment to not use the utility unless one knows what they're doing. Aside comment: yeah, that helps).

Note: My personal comments below the READMEs are in parantheses.

Announcement

Totally confused - eth0, eth1, eth2, no connection

Totally confused - eth0, eth1, eth2, no connection

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment