What sets up network interfaces?
in [Suse]
|
Prev: mp3 player
Next: 10.2 and sendmail
From: escra on 12 Mar 2007 19:46 What makes this happen during bootup? (From boot.msg) ----------------------- Setting up network interfaces: lo lo IP address: 127.0.0.1/8 doneWaiting for mandatory devices: wlan-bus-pci-0000:00:10.0 __NSC__ 17 15 wlan0 device: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01) wlan0 configuration: wlan-bus-pci-0000:00:10.0 wlan0 DHCP client (dhcpcd) is running ----------------------- The reason I'm asking is because: - It makes my wireless card connect to first thing it sees and not the SSID I specifically told it to connect with using YaST / NetApplet. - I also want to know how to have wpa_supplicant automatically run at boot because my SSID uses WPA2. Everyime I boot SuSE (10), it is always connected to someone else's (open) SSID until I manually disconnect (using netapplet), manually run wpa_supplicant by: # wpa_supplicant -B -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd ....and then re-connect. How do you make this happen automatically at boot? And more important, how do tell the "whatever-does-it-at-boot" to : NEVER, EVER, under ANY circumstances connect to ANY SSID other than the one you tell it to. Thanks
From: escra on 12 Mar 2007 20:19 escra wrote: > What makes this happen during bootup? > (From boot.msg) > > ----------------------- > Setting up network interfaces: > lo > lo IP address: 127.0.0.1/8 > doneWaiting for mandatory devices: wlan-bus-pci-0000:00:10.0 __NSC__ > 17 15 > wlan0 device: Atheros Communications, Inc. AR5212 802.11abg NIC > (rev > 01) > wlan0 configuration: wlan-bus-pci-0000:00:10.0 > wlan0 DHCP client (dhcpcd) is running > ----------------------- > > The reason I'm asking is because: > > - It makes my wireless card connect to first thing it sees and not the > SSID I specifically told it to connect with using YaST / NetApplet. > > - I also want to know how to have wpa_supplicant automatically run at boot > because my SSID uses WPA2. > > Everyime I boot SuSE (10), it is always connected to someone else's (open) > SSID until I manually disconnect (using netapplet), manually run > wpa_supplicant by: > > # wpa_supplicant -B -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd > > ...and then re-connect. > > How do you make this happen automatically at boot? > > And more important, how do tell the "whatever-does-it-at-boot" to : > > NEVER, EVER, under ANY circumstances connect to ANY SSID other than the > one you tell it to. > > Thanks I thought this idea might work, but it also doesn't. (There are bunch of different things in Suse that are used to config wireless. Who knows which one is the one you are supposed to use?) Setup in Control Center --> Internet and Network ---> Wireless Network + All four "config" tabs to point to the SSID I want it to use. + Encryption turned off because that configureator only allows for WEP, not + In the "Execute Script on Connect", got an idea that this would work --> + Pointed this to a permission-executable file I made called: + /usr/local/sbin/WPAd + which contains one line: wpa_supplicant -B -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd In YaST2 Config Network Settings (Click on the Netapplet thingy and select Config) + For the wireless card, the intended SSID is entered + WPA is selected, along with correct passphrase + Everything else is right Now when I boot, wpa_supplicant does load: ---------- # psg wpa root 4794 0.0 0.2 2900 1264 ? S<s 20:00 0:00 wpa_supplicant -iwlan0 -c/var/run/wpa_supplicant-wlan0.conf -Dndiswrapper -P/var/run/wpa_supplicant/wlan0.pid -B ---------- But the damn card is STILL connecting to the neighbor's open SSID until I manually disconnect and reconnect. Its like the wpa_supplicant was started too early or something. Probably need to be started before the ... : > ----------------------- > Setting up network interfaces: > lo > lo IP address: 127.0.0.1/8 > doneWaiting for mandatory devices: wlan-bus-pci-0000:00:10.0 __NSC__ > 17 15 > wlan0 device: Atheros Communications, Inc. AR5212 802.11abg NIC > (rev > 01) > wlan0 configuration: wlan-bus-pci-0000:00:10.0 > wlan0 DHCP client (dhcpcd) is running > ----------------------- .... thing happens. Anyone, anyone, anyone??? Thanks
From: Malcolm on 12 Mar 2007 21:46 On Mon, 12 Mar 2007 20:53:26 -0400 escra <escra_junk_email(a)yahoo.com> wrote: <snip> > Yes. I'm pissed. Hi I'm running 10.2 and SLED no problems with 3 other access points in the neighbourhood. One thing to remember is to keep at least 2 channel separation from other access points. What channel is yours on compared to other ones about? I'm using the networkmanager on 10.2, but normal ifup/ifdown on SLED. -- Cheers Malcolm °¿° (Linux Counter #276890) SLED 10.0 x86_64 Kernel 2.6.16.27-0.9-smp up 23:06, 2 users, load average: 0.17, 0.08, 0.01
From: escra on 12 Mar 2007 22:08 Malcolm wrote: > On Mon, 12 Mar 2007 20:53:26 -0400 > escra <escra_junk_email(a)yahoo.com> wrote: > > <snip> >> Yes. I'm pissed. > Hi > I'm running 10.2 and SLED no problems with 3 other access points in the > neighbourhood. One thing to remember is to keep at least 2 channel > separation from other access points. What channel is yours on compared > to other ones about? I'm using the networkmanager on 10.2, but normal > ifup/ifdown on SLED. > Channels are seperated fine. I don't what you are talking about. # sled bash: sled: command not found # networkmanager bash: networkmanager: command not found
From: Jim Jones on 12 Mar 2007 23:46
escra wrote: > Malcolm wrote: > >> On Mon, 12 Mar 2007 20:53:26 -0400 >> escra <escra_junk_email(a)yahoo.com> wrote: >> >> <snip> >>> Yes. I'm pissed. >> Hi >> I'm running 10.2 and SLED no problems with 3 other access points in the >> neighbourhood. One thing to remember is to keep at least 2 channel >> separation from other access points. What channel is yours on compared >> to other ones about? I'm using the networkmanager on 10.2, but normal >> ifup/ifdown on SLED. >> > > Channels are seperated fine. > > I don't what you are talking about. > > # sled > bash: sled: command not found > # networkmanager > bash: networkmanager: command not found SLED is another Suse variation, Suse Linux Enterprise Desktop, it is a business version of Suse that comes with paid support packages. You can access networkmanager in Suse 10.2 from Start Button>Computer>Adminstrator Settings>Network Devices>Network Card then select networkmanager method of setup. Jim -- Linux Websites Links http://myweb.cableone.net/okieman7/linux.htm |