network configuration question (solved)

[quintok]

Hi, I have a wifi network (which works fine...almost).
whenever I reboot the configuration I've set is incorrect and subsequently it's not doing what I thought I asked it to do.
whenever I reboot I have to do these two things:

sudo iwconfig eth1 essid belkin54g
sudo dhclient eth1

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
address 127.0.0.1
netmask 255.0.0.0

# The primary network interface
auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp
   pre-up sudo iwconfig eth1 rate 11M
   wireless_essid belkin54g

auto eth2
iface eth2 inet dhcp

also, as eth0 and eth2 aren't used, should I change their configuration?
Thanks.
-Q

[askrieger]

Re: network configuration question

I suspect (I may be wrong. I know NOTHING about wireless) that your pre-up command is failing because of the "sudo". Does it ask you for a password in a black & white full screen text console before it asks you for a username and password in a graphical login screen? I would try to run the command without the "sudo".

If that doesn't work, you may have to put the two commands, that you have to run every time you log in, into a script. You can either add the script to /etc/init.d and then link to it in /etc/rc2.d, or, preferably, you can put the script into your /home/quintok/.kde/Autostart/ directory. Of course, if you do it that way, you won't have your network if you log into Gnome, but there are lots of other things you won't have if you log into Gnome, anyway.

[Guest]

Re: network configuration question

sudo pico /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
address 127.0.0.1
netmask 255.0.0.0


iface wlan0 inet static

wireless-essid knet-LAN
address 192.168.0.15
gateway 192.168.0.1
netmask 255.255.255.0

auto wlan0

=> sudo /etc/init.d/networking restart
thanks

[quintok]

Re: network configuration question

ahh, I see there were quite a few things I stuffed up... I'll try it when I get home

thanks.

[quintok]

Re: network configuration question

okay, yesterday I tried:

iface eth1 inet dhcp
wireless-essid belkin54g
auto eth1

iface eth1 inet static
wireless-essid belkin54g
address 192.168.0.2
netmask 255.255.255.0
gateway 192.168.0.1
auto eth1

both end up with, after reboot having access point invalid (in iwconfig). However if I re-apply essid (which was already belkin54g after I rebooted), the second one wouldn't let me do the dhclient on eth1 for obvious reasons so I had to actually reload the network with dhcp setup on eth1 before it'd let me connect to the access point of belkin54g (using dhclient). I'm wondering if I should put in wireless-ap or wireless-accesspoint (or whatever it is) into the iface definition like:

iface eth1 inet dhcp
wireless-essid belkin54g
wireless-ap ############
auto eth1

[1richard]

Re: network configuration question

No dashes - - - any place

use underscore

wireless_essid

[quintok]

Re: network configuration question

I found a command list for the interface file and that seems to have been the trick.

iface eth1 inet dhcp
up /sbin/iwconfig eth1 essid belkin54g
up /sbin/dhclient eth1
wireless_essid belkin54g
auto eth1