What sets up network interfaces?
in [Suse]
|
Prev: mp3 player
Next: 10.2 and sendmail
From: escra on 13 Mar 2007 16:15 Jim Jones wrote: > 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 How is this relevant when, as I stated in the beginning of this thread, I'm using Suse 10.0 ?
From: Malcolm on 13 Mar 2007 18:13 On Tue, 13 Mar 2007 16:15:55 -0400 escra <escra_junk_email(a)yahoo.com> wrote: > Jim Jones wrote: > > > 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 > > Button>Computer>then > > select networkmanager method of setup. > > > > Jim > > How is this relevant when, as I stated in the beginning of this > thread, I'm using Suse 10.0 ? > Hi Ahh, missed the bit about 10. If your using KDE, try kwifimanager or if not wifiradar to setup a profile to use by default. If you run iwlist <interface> scan is the one that is grabbing your connection more powerful than your local one. Have you tried moving the aerial on your access point/ repositioning the access point? -- Cheers Malcolm °¿° (Linux Counter #276890) SLED 10.0 x86_64 Kernel 2.6.16.27-0.9-smp up 1 day 19:28, 2 users, load average: 0.07, 0.05, 0.00
From: Jim Jones on 13 Mar 2007 23:33 escra wrote: > Jim Jones wrote: > >> 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 > > How is this relevant when, as I stated in the beginning of this thread, I'm > using Suse 10.0 ? > Either you or someone in the thread asked what SLED and NetworkManger was, so I explained. -- Linux Websites Links http://myweb.cableone.net/okieman7/linux.htm
From: JimR on 14 Mar 2007 17:51
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 > Try using Yast, under network devices | network card, select the card you are trying to configure, then click edit to change the settings. I think to get it to keep the settings, select managed mode (not ad-hoc). It's something of a black art, and I had a hell of a time getting mine to work under Suse 10.0, but finally did. Unfortunately, I tried so many things, I can't tell you for sure which was the one that ultimately fixed the problem. Once I got the wireless connection to work, I had to add the AP to the route as my default gw, using: route add default gw 192.168.1.1 wlan1 (yours will probably be wlan0) Write back with the listing of the output when you run iwconfig and also ifconfig. Jim |