Re: Need a little help with my network configuration
On Sun, 10 Jun 2007 16:06:17 +0200
Chris <list.hurschler@gmx.de> wrote:
> On Wednesday 06 June 2007 01:54, Celejar wrote:
> > On Sun, 3 Jun 2007 16:34:48 +0200
> >
> > Chris <list.hurschler@gmx.de> wrote:
> > > Hi,
> > >
> > > I have a box with a usb-nic which uses the zd1211rw module. The box is
> > > dist-upgraded to the testing level. I can connect to the router using
> > > network-manager and from kde with network-manager-kde just fine.
> > >
> > > eth1 IEEE 802.11b/g ESSID:"cjwlan" Nickname:"zd1211"
> > > Mode:Managed Frequency:2.437 GHz Access Point:
> > > 00:04:0E:96:0F:37 Bit Rate=11 Mb/s
> > > Encryption key: XXXXXXX Security mode:open
> > > Link Quality=34/100 Signal level=28/100
> > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> > >
> > > Every time I boot, I have to re-enter the passphrase again, but I want it
> > > to
> >
> > What sort of passphrase? What security protocol (WEP, WPA, WPA2, etc)
> > are you using? What does ifconfig show when you boot before you enter
> > the passphrase?
>
> I'm using WEP and entering the passphrase as hex in network-manager-kde. If I
> boot with:
>
> cat /etc/network/interfaces >>
>
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> # allow-hotplug eth0
> # iface eth0 inet dhcp
>
> Then:
>
> ifconfig >>
>
> eth0 Link encap:Ethernet HWaddr 00:02:A5:F7:26:6A
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> eth1 Link encap:Ethernet HWaddr 00:02:72:56:84:A9
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:4368 (4.2 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:12 errors:0 dropped:0 overruns:0 frame:0
> TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:732 (732.0 b) TX bytes:732 (732.0 b)
>
>
>
> After I log in as user and enter the passphrase in network-manager-kde:
>
> ifconfig >>
>
> eth0 Link encap:Ethernet HWaddr 00:02:A5:F7:26:6A
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> eth1 Link encap:Ethernet HWaddr 00:02:72:56:84:A9
> inet addr:192.168.178.27 Bcast:192.168.178.255 Mask:255.255.255.0
> inet6 addr: fe80::202:72ff:fe56:84a9/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:3570 errors:0 dropped:43 overruns:0 frame:0
> TX packets:2092 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:4986730 (4.7 MiB) TX bytes:130461 (127.4 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:57 errors:0 dropped:0 overruns:0 frame:0
> TX packets:57 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:3700 (3.6 KiB) TX bytes:3700 (3.6 KiB)
>
> iwconfig >>
>
> eth1 IEEE 802.11b/g ESSID:"essid" Nickname:"zd1211"
> Mode:Managed Frequency:2.437 GHz Access Point: 00:04:0E:96:0F:37
> Bit Rate=11 Mb/s
> Encryption key:"passphrase" Security mode:open
> Link Quality=99/100 Signal level=32/100
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> And everything is ok. The interface as such works, but I'm having trouble
> getting eth1 up automatically either:
>
> 1) using network-manager which should actually automatically do it, but always
> askes for the passpharse instead; or
>
> 2) by having eth1 start from auto eth1 in /etc/network/interfaces which fails
> either statically or dhcp, why I don't know.
>
> Thanks for any suggestions. I need to be able to have this box come up and
> attach to the network over eth1 without any intervention.
>
> Chris
>
>
> > > connect automatically at boot. I tried to set up an interface
> > > in /etc/network/interfaces (I don't really need network-manager). But I
> > > can't for the life of me get it working! Here is my
> > > /etc/network/interfaces:
> > >
> > > # This file describes the network interfaces available on your system
> > > # and how to activate them. For more information, see interfaces(5).
> > >
> > > # The loopback network interface
> > > auto lo
> > > iface lo inet loopback
> > >
> > > # The primary network interface
> > > # allow-hotplug eth0
> > > # iface eth0 inet dhcp
> > >
> > > iface eth1 inet dhcp
> > > wireless_keymode restricted
> > > wireless_key XXXXXXXXXXXXXXXXXXXXXXX
> > > wireless_essid XXXXXXXXX
> > >
> > > Any suggestions on either getting network-manager-kde to remember the
> > > passphrase, OR getting my normal network/interfaces working would be
> > > really, really appreciated.
> > >
> > > Thanks,
> > >
> > > Chris
> > >
> > > --
> > > C. Hurschler
> >
> > Celejar
> > --
> > mailmin.sourceforge.net - remote access via secure (OpenPGP) email
> > ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
>
> --
> C. Hurschler
If the WEP password is specified in 'interfaces', then 'ifup eth1' or
'auto eth1' in 'interfaces' should bring it up. What error do you get?
When it fails, what do 'ifconfig' and 'iwconfig' say?
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: