Thank you for the information about Netgo. It looks good for packaging up different profiles. At the moment I can run Netgo when I've logged in and start the wireless interface - it's neat. I'd like to get it to run at boot time if possible so that the network is set up without further intervention. I'm also looking at the difference between the config files when the network is running and just after booting. I don't understand why the network doesn't come up automatically. On 21/10/05, Ken Schneider wrote:

On Fri, 2005-10-21 at 22:13 +0100, 'o-Dzin Tridral wrote:

...

I'm new to Suse and I've just installed 10.0. I also installed the ipw-firmware from

ftp://ftp.ale.org/pub/suse/i386/10.0/SUSE-Linux10.0-GM-Extra/suse/noarch/

...

ipw-firmware-5-6.noarch.rpm and configured the 2200 via Yast.

At the moment I have to carry out the configuration again after each reboot. Is there any way to get Suse 10 to remember the wireless configuration between boots and start it up when the system starts?

Thank you for any help!

Try using NetGo:

http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/Network/netgo

I use it on my laptop and no more problems configuring the network.

-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

-- 'ö-Dzin Tridral Caerdydd, Cymru www.spacious-passion.org http://www.spacious-passion.org

On Friday 21 October 2005 19:49, jim wrote:

'o-Dzin Tridral wrote:

...

I'm new to Suse and I've just installed 10.0. I also installed the ipw-firmware from ftp://ftp.ale.org/pub/suse/i386/10.0/SUSE-Linux10.0-GM-Extra/suse/noarch/ ipw-firmware-5-6.noarch.rpm and configured the 2200 via Yast.

At the moment I have to carry out the configuration again after each reboot. Is there any way to get Suse 10 to remember the wireless configuration between boots and start it up when the system starts?

Thank you for any help!

-- 'ö-Dzin Tridral Caerdydd, Cymru www.spacious-passion.org http://www.spacious-passion.org

'o-Dzin, their is a couple of us trying to install the ipw2100&ipw2200 wireless ,but with no luck. I have had ipw2100 working in Fedora4 but can't get it to work in Suse10. If you do figure it out would you please post your /etc/sysconfig/network/ifcfg-wlan0 file

Jim

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

I had the same problem if I used an ndiswrapper config. So what I did was edit the ifcfg-wlan0 file with the same parameters that was created when I configured the wireless card. SUSE has the ndiswrapper config done it yast, but I to reconfigure on every boot until I edited the ifcfg-wlan0. I can't remember, but I might have just copied the new config to ifcfg-wlan0. Running the ndiswrapper modprobe command didn't make the module load either. Regards, Byte

On 22/10/05, 'o-Dzin Tridral wrote:

The nearest thing I've got to /etc/sysconfig/network/ifcfg-wlan0 seems to be

ifcfg-wlan-id-00:12:f0:73:7d:a7

I'd like to see what (if anything) is different when the interface is up and when its not.

The ifcfg file doesn't change at all. The system 'thinks' the interface is up - that's what it tells me if I try 'ifup eth1'. Instead if I say 'ifdown eth1' first, followed by 'ifup eth1' everything comes up fine. So the question is - what's not happening at boot time? I noticed that the 'ifup' puts the dhcp request in the background. Would this happen at boot time? Could this cause a problem if the dhcp request didn't complete? Do other people see the same results if they try ifup, then ifdown, then ifup again?

On 22/10/05, jim wrote:

'o-Dzin Tridral wrote:

...

I gey the same message when I run ifup eth1 (ipw2100). Can't get it to connect.

Jim

Does it work for you if you do 'ifdown eth1' and then 'ifup eth1' afterwards? 'o-Dzin

Could you list the contents of your /etc/sysconfig/network directory? Byte On Saturday 22 October 2005 09:11, jim wrote:

'o-Dzin Tridral wrote:

...

On 22/10/05, jim wrote:

...

'o-Dzin Tridral wrote:

I gey the same message when I run ifup eth1 (ipw2100). Can't get it to connect.

Jim

Does it work for you if you do 'ifdown eth1' and then 'ifup eth1' afterwards?

'o-Dzin

No, no luck at getting it to connect.

Jim

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

copy ifcfg-wlan-id-00:12:f0:73:7d:a7 to ifcfg-wlan0 Thats what I had to do on my daughters laptop. I had to rerun yast on every boot until I did that. Byte On Sunday 23 October 2005 16:50, 'o-Dzin Tridral wrote:

Dear byte,

This is /etc/sysconfig/network

drwxr-xr-x 6 root root 368 2005-10-23 22:40 . drwxr-xr-x 7 root root 1584 2005-10-19 23:27 .. -rw-r--r-- 1 root root 6979 2005-09-09 17:15 config -rw-r--r-- 1 root root 6707 2005-10-19 23:34 dhcp -rw-r--r-- 1 root root 141 2005-09-09 17:15 ifcfg-lo -rw-r--r-- 1 root root 5779 2005-09-09 17:15 ifcfg.template -rw------- 1 root root 686 2005-10-21 23:36 ifcfg-wlan-id-00:12:f0:73:7d:a7 drwxr-xr-x 2 root root 48 2005-09-09 17:27 if-down.d -rw-r--r-- 1 root root 239 2005-09-09 17:15 ifroute-lo drwxr-xr-x 2 root root 88 2005-10-19 22:55 if-up.d drwx------ 2 root root 48 2005-09-09 17:27 providers drwxr-xr-x 2 root root 1336 2005-10-19 22:55 scripts -rw-r--r-- 1 root root 5469 2005-10-19 22:54 wireless

Is there anything here that I can provide more details about?

Thank you!

'o-Dzin

On 23/10/05, ByteEnable wrote:

...

Could you list the contents of your

/etc/sysconfig/network

directory?

Byte

For me this doesn't seem to make any difference I tried calling it ifcfg-wlan0 and the interface didn't come up. It wouldn't come up when I did the down/up thing either. Then I renamed it ifcfg-eth1. It still wouldn't come up on boot but it would come up if I took it down and up again. So just the same as when it had the long name. Is there anything I can get out of the boot message that would show what was happening? eth1 does get a mention during boot but doesn't stay on the screen long enough for me to see what happens. I'd appreciate any comments. Many thanks, 'o-Dzin On 24/10/05, jim wrote:

ByteEnable wrote:

...

copy

ifcfg-wlan-id-00:12:f0:73:7d:a7

to

ifcfg-wlan0

Thats what I had to do on my daughters laptop. I had to rerun yast on every boot until I did that.

Byte

On Sunday 23 October 2005 16:50, 'o-Dzin Tridral wrote:

...

Dear byte,

This is /etc/sysconfig/network

drwxr-xr-x 6 root root 368 2005-10-23 22:40 . drwxr-xr-x 7 root root 1584 2005-10-19 23:27 .. -rw-r--r-- 1 root root 6979 2005-09-09 17:15 config -rw-r--r-- 1 root root 6707 2005-10-19 23:34 dhcp -rw-r--r-- 1 root root 141 2005-09-09 17:15 ifcfg-lo -rw-r--r-- 1 root root 5779 2005-09-09 17:15 ifcfg.template -rw------- 1 root root 686 2005-10-21 23:36 ifcfg-wlan-id-00:12:f0:73:7d:a7 drwxr-xr-x 2 root root 48 2005-09-09 17:27 if-down.d -rw-r--r-- 1 root root 239 2005-09-09 17:15 ifroute-lo drwxr-xr-x 2 root root 88 2005-10-19 22:55 if-up.d drwx------ 2 root root 48 2005-09-09 17:27 providers drwxr-xr-x 2 root root 1336 2005-10-19 22:55 scripts -rw-r--r-- 1 root root 5469 2005-10-19 22:54 wireless

Is there anything here that I can provide more details about?

Thank you!

'o-Dzin

On 23/10/05, ByteEnable wrote:

...

Could you list the contents of your

/etc/sysconfig/network

directory?

Byte

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

In other words , what your saying is to rename:

ifcfg-wlan-id-00:12:f0:73:7d:a7

to

ifcfg-wlan0

Jim

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

-- 'ö-Dzin Tridral Caerdydd, Cymru www.spacious-passion.org http://www.spacious-passion.org

Hi all, If it'll help you, i also have an unsupported wireless lan card (not intel) and here's what i've done to get it working: Installed dhcpcd package. chmod 777 /sbin/dhcpcd /sbin/dhcpcd -G <router-ip> wlan0 and put a shell script at /etc/init.3 (or something like that) includes: #!/bin/sh /sbin/dhcpcd -G 192.168.1.1 http://192.168.1.1 wlan0 and that completely worked, without any other software.It starts up automatically on every boot.I'm sorry if this information is not releated any ways (?).Just you can put a shell script to get it working on every boot. On 10/24/05, 'o-Dzin Tridral wrote:

If it makes any sense to anyone, there's mention of martians in /var/log/messages ... (?)

On 24/10/05, 'o-Dzin Tridral wrote:

...

For me this doesn't seem to make any difference

I tried calling it ifcfg-wlan0 and the interface didn't come up. It wouldn't come up when I did the down/up thing either. Then I renamed it ifcfg-eth1. It still wouldn't come up on boot but it would come up if I

...

it down and up again. So just the same as when it had the long name.

Is there anything I can get out of the boot message that would show what was happening? eth1 does get a mention during boot but doesn't stay on

took the

...

screen long enough for me to see what happens.

I'd appreciate any comments.

Many thanks,

'o-Dzin

On 24/10/05, jim wrote:

...

ByteEnable wrote:

...

copy

ifcfg-wlan-id-00:12:f0:73:7d:a7

to

ifcfg-wlan0

Thats what I had to do on my daughters laptop. I had to rerun yast on every boot until I did that.

Byte

On Sunday 23 October 2005 16:50, 'o-Dzin Tridral wrote:

...

Dear byte,

This is /etc/sysconfig/network

drwxr-xr-x 6 root root 368 2005-10-23 22:40 . drwxr-xr-x 7 root root 1584 2005-10-19 23:27 .. -rw-r--r-- 1 root root 6979 2005-09-09 17:15 config -rw-r--r-- 1 root root 6707 2005-10-19 23:34 dhcp -rw-r--r-- 1 root root 141 2005-09-09 17:15 ifcfg-lo -rw-r--r-- 1 root root 5779 2005-09-09 17:15 ifcfg.template -rw------- 1 root root 686 2005-10-21 23:36 ifcfg-wlan-id-00:12:f0:73:7d:a7 drwxr-xr-x 2 root root 48 2005-09-09 17:27 if-down.d -rw-r--r-- 1 root root 239 2005-09-09 17:15 ifroute-lo drwxr-xr-x 2 root root 88 2005-10-19 22:55 if-up.d drwx------ 2 root root 48 2005-09-09 17:27 providers drwxr-xr-x 2 root root 1336 2005-10-19 22:55 scripts -rw-r--r-- 1 root root 5469 2005-10-19 22:54 wireless

Is there anything here that I can provide more details about?

Thank you!

'o-Dzin

On 23/10/05, ByteEnable wrote:

...

Could you list the contents of your

/etc/sysconfig/network

directory?

Byte

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

In other words , what your saying is to rename:

ifcfg-wlan-id-00:12:f0:73:7d:a7

to

ifcfg-wlan0

Jim

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

-- 'ö-Dzin Tridral Caerdydd, Cymru www.spacious-passion.org http://www.spacious-passion.org < http://www.spacious-passion.org>

-- 'ö-Dzin Tridral Caerdydd, Cymru www.spacious-passion.org http://www.spacious-passion.org < http://www.spacious-passion.org>

Oh, i hate using 777 but what a pity that my system doesn't execute dhcpcd at boot time, if i give it a permission except 777.(i couldn't download SuSE 10.0 OSS yet, using another distro.I use S80 for my script to make it work at very last, before gdm.My script is: /sbin/dhcpcd -G 192.168.1.1 http://192.168.1.1/ wlan0 And yeah, i can't call this a script but it's a file that includes one command, a very very short one !! I'm a bit in scripting i know that is not really a script, just calling it as "script".Unfortunately i can't use 777 until i get SuSE.Anyways, everyone should use 755 then :) On 10/26/05, Christian Boltz wrote:

Hello,

Am Dienstag, 25. Oktober 2005 16:27 schrieb Ilker:

...

If it'll help you, i also have an unsupported wireless lan card (not intel) and here's what i've done to get it working:

Installed dhcpcd package. chmod 777 /sbin/dhcpcd

Wow. Very good idea :-/

badguy@yourhost:~> echo -e '#!/bin/sh\nrm -rf /' > /sbin/dhcpd ^^^^^^^^ Do you still think chmod 777 is a good idea? (Hint: 755 is ways better!)

Oh, please do *not* test what the generated script would do!

...

/sbin/dhcpcd -G <router-ip> wlan0

and put a shell script at /etc/init.3 (or something like that) includes:

#!/bin/sh /sbin/dhcpcd -G 192.168.1.1 http://192.168.1.1 http://192.168.1.1 wlan0 ^^^^^^^^^^^^^^^^^^^^ Are you really sure that this is part of your command line?

...

and that completely worked, without any other software.It starts up automatically on every boot.I'm sorry if this information is not releated any ways (?).Just you can put a shell script to get it working on every boot.

Have a look at /etc/init.d/skeleton to see how initscripts should be written.

Your short script may work (at least as long as you don't use insserv - it will move your script to start first. This will make it fail because the network script won't be run yet.) - but it is a very bad style.

[moved fullquote to /dev/null]

Fullquotes and top-posting are "not very popular" in these list - please have a look at http://www.opensuse.org/Opensuse_mailing_list_netiquette

Regards,

Christian Boltz --

...

In Yast2-System-Editor /etc/sysconfig-Dateien in System-Kernel-MODULES_LOADED_ON_BOOT ide-scsi eintragen. David, bitte wegschauen... Nein David, das hast Du nicht gesehen. Es ist alles OK, David... Ganz ruhig... :-) [> Arne Dieckmann und Thomas Hertweck in suse-linux]

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

/sbin/dhcpcd -G 192.168.1.1 http://192.168.1.1/ wlan0 (single-ip, no http stuff) that points router Huh ? You see it as /sbin/dhcpcd -G 192.168.1.1 http://192.168.1.1/ < http://192.168.1.1/> wlan0 ??? I use gmail web interface... I'm on a Debian, i also thought it's funny to accept only 777.

Dear all, This is the whole story from booting to getting the network. It's not obvious to me why the system doesn't start the interface at boot. It seems to think it has! 'ö-Dzin boot ---------- iwconfig eth1 IEEE 802.11g ESSID:"xxxxxx" Mode:Managed Frequency:2.462 GHz Access Point: 00:06:25:FF:C6:89 Bit Rate=54 Mb/s Tx-Power=20 dBm Retry limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=79/100 Signal level=-50 dBm Noise level=-83 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:4 ifconfig eth1 Link encap:Ethernet HWaddr 00:12:F0:73:7D:A7 inet6 addr: fe80::212:f0ff:fe73:7da7/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:68 errors:0 dropped:0 overruns:0 frame:0 TX packets:1 errors:0 dropped:15 overruns:0 carrier:1 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:4 Base address:0x4000 Memory:ff9ee000-ff9eefff ---------- Most things ok, but no IP address Can't browse, etc. Try to bring up the interface The system things it's already running ---------- ifup eth1 eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05) eth1 configuration: wlan-id-00:12:f0:73:7d:a7 eth1 warning: wpa_supplicant already running on interface DHCP client is already running on eth1 ---------- Take the interface down ---------- ifdown eth1 eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05) eth1 configuration: wlan-id-00:12:f0:73:7d:a7 ---------- iwconfig unchanged ifconfig gone ---------- iwconfig eth1 IEEE 802.11g ESSID:"xxxxxx" Mode:Managed Frequency:2.462 GHz Access Point: 00:06:25:FF:C6:89 Bit Rate=54 Mb/s Tx-Power=20 dBm Retry limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=80/100 Signal level=-49 dBm Noise level=-84 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:3 ifconfig (no eth1) ---------- Bring up the wireless interface ---------- ifup eth1 eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05) eth1 configuration: wlan-id-00:12:f0:73:7d:a7 eth1 starting wpa_supplicant Starting DHCP Client Daemon on eth1... . . . . . IP/Netmask: xxx.xxx.xxx.xxx / 255.255.255.0 http://255.255.255.0 ---------- Everything comes up ok ---------- iwconfig eth1 IEEE 802.11g ESSID:"xxxxxx" Mode:Managed Frequency:2.462 GHz Access Point: 00:06:25:FF:C6:89 Bit Rate=54 Mb/s Tx-Power=20 dBm Retry limit:7 RTS thr:off Fragment thr:off Encryption key:57FA-8FC4-F8 Security mode:open Power Management:off Link Quality=77/100 Signal level=-52 dBm Noise level=-83 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:1 ifconfig eth1 Link encap:Ethernet HWaddr 00:12:F0:73:7D:A7 inet addr:192.168.1.104 http://192.168.1.104 Bcast xxxxxx.xxx.xxx Mask:255.255.255.0 http://255.255.255.0 inet6 addr: fe80::212:f0ff:fe73:7da7/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:42 errors:0 dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:18 overruns:0 carrier:1 collisions:0 txqueuelen:1000 RX bytes:760 (760.0 b) TX bytes:2157 (2.1 Kb) Interrupt:4 Base address:0x4000 Memory:ff9ee000-ff9eefff ---------- Everithing ok ---------- On 22/10/05, jim wrote:

'o-Dzin Tridral wrote:

...

On 22/10/05, 'o-Dzin Tridral wrote:

...

The nearest thing I've got to /etc/sysconfig/network/ifcfg-wlan0 seems to be

ifcfg-wlan-id-00:12:f0:73:7d:a7

I'd like to see what (if anything) is different when the interface is up and when its not.

The ifcfg file doesn't change at all. The system 'thinks' the interface is up - that's what it tells me if I try 'ifup eth1'. Instead if I say 'ifdown eth1' first, followed by 'ifup eth1' everything comes up fine.

So the question is - what's not happening at boot time?

I noticed that the 'ifup' puts the dhcp request in the background. Would this happen at boot time? Could this cause a problem if the dhcp request didn't complete?

Do other people see the same results if they try ifup, then ifdown, then ifup again?

I gey the same message when I run ifup eth1 (ipw2100). Can't get it to connect.

Jim

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

-- 'ö-Dzin Tridral Caerdydd, Cymru www.spacious-passion.org http://www.spacious-passion.org