Hi, I discovered that Suse named wireless NIC wlanX instead ethX. This it's ok but the problem is that DSL YAST module doesn't give me the possibility to choose it. With Any other distribution is possible to use wireless PCMCIA to use DSL connections. Any ideas? Thanks Andrea
Hi, Am Mittwoch, 31. Dezember 2003 18:26 schrieb Mailing:
I discovered that Suse named wireless NIC wlanX instead ethX. This it's ok but the problem is that DSL YAST module doesn't give me the possibility to choose it. With Any other distribution is possible to use wireless PCMCIA to use DSL connections.
I think you're mixing things up. At least I'm not aware of any DSL modem that is connected via wlan to the computer. Of course their are plenty of those router devices that have a built-in DSL modem. However, the computer that gets connected to such a device (either normal ethernet or wlan) will not see any DSL specific thing. Therefore there is no need to configure PPPoE or PPPoA on your computer. All you need to do is to configure your NIC with a default route to your router. The DSL specific stuff is done within this DSL router. Greetings from Bremen hartmut
Thanks, but I connected my DSL ethernet modem to my access point; after I configured my NIC ethX (ex.) to setup DSL connection ... after I change the config. file and instead ethX I put in wlan0 (ex.). I already made it since Rehat or Mandrake ... with Suse is impossible (I hope no!). YAST DSL module configure my NIC (eth0) for the first time and when I try to change into IFCFG-DSL0 with "wlan0" .... brrrrr. So what I made before with other distribution is possible .... now I'd like make it with Super Suse. Thanks Andrea Il gio, 2004-01-01 alle 19:45, Hartmut Meyer ha scritto:
Hi,
Am Mittwoch, 31. Dezember 2003 18:26 schrieb Mailing:
I discovered that Suse named wireless NIC wlanX instead ethX. This it's ok but the problem is that DSL YAST module doesn't give me the possibility to choose it. With Any other distribution is possible to use wireless PCMCIA to use DSL connections.
I think you're mixing things up. At least I'm not aware of any DSL modem that is connected via wlan to the computer. Of course their are plenty of those router devices that have a built-in DSL modem. However, the computer that gets connected to such a device (either normal ethernet or wlan) will not see any DSL specific thing. Therefore there is no need to configure PPPoE or PPPoA on your computer.
All you need to do is to configure your NIC with a default route to your router. The DSL specific stuff is done within this DSL router.
Greetings from Bremen hartmut
Hi, Am Freitag, 2. Januar 2004 23:43 schrieb Mailing:
Il gio, 2004-01-01 alle 19:45, Hartmut Meyer ha scritto:
Am Mittwoch, 31. Dezember 2003 18:26 schrieb Mailing:
I discovered that Suse named wireless NIC wlanX instead ethX. This it's ok but the problem is that DSL YAST module doesn't give me the possibility to choose it. With Any other distribution is possible to use wireless PCMCIA to use DSL connections.
I think you're mixing things up. At least I'm not aware of any DSL modem that is connected via wlan to the computer. Of course their are plenty of those router devices that have a built-in DSL modem. However, the computer that gets connected to such a device (either normal ethernet or wlan) will not see any DSL specific thing. Therefore there is no need to configure PPPoE or PPPoA on your computer.
All you need to do is to configure your NIC with a default route to your router. The DSL specific stuff is done within this DSL router.
Thanks, but I connected my DSL ethernet modem to my access point; after I configured my NIC ethX (ex.) to setup DSL connection ... after I change the config. file and instead ethX I put in wlan0 (ex.). I already made it since Rehat or Mandrake ... with Suse is impossible (I hope no!). YAST DSL module configure my NIC (eth0) for the first time and when I try to change into IFCFG-DSL0 with "wlan0" .... brrrrr.
So what I made before with other distribution is possible .... now I'd like make it with Super Suse.
I'm not 100% sure I understood you. Anyway, have you configured the wlan connection as such? You won't be able to do that with the YaST2 DSL modul but instead you will need to configure the wlan part with the YaST2 network card module. In ideal case you can test the wlan connection with another computer in your local network befor trying DSL. Does your access point also offer (more than one) ethernet port? If so you should first test DSL with a normal ethernet connection where both your computer and your DSL modem are connected via ethernet to the access point (which would work as a switch in this setup). Once this works and once you also have successfully setup and tested(!) wlan connection with another computer on your local network, you could try and replace the ethX with wlan0 in ifcfg-dsl0. Greetings from Bremen hartmut
Thanks but what you advised me I've already tested. I configured eth0 and DSL0 (by YAST modul) that's ok; after I've setup wlan0 correctly on my network and after I replaced eth0 with wlan0 .... but .... nothing. I got this message from "/var/log/messages" ... ***** Plugin passwordfd.so loaded. unrecognized option 'wlan0' ***** So I tried to do 2 things: 1) renamed ifcfg-wlan-pcmcia to ifcfg-eth1 ... ERROR 2) I've checked IFUP-PPP file and I noticed that this script search available interfaces to add "ifcfg-" before, so I modified "ifcfg-dsl0" and instead "wlan0" ... "wlan-pcmcia" .... nothing. My view is that SuSE limit DSL YaST modul with the ethX interface and does not allow us to use "hotplug" interfaces What you think? Andrea PS. I remember you that with RedHat or Mandrake this operation is more sample because any interface is called ethX so ... Il sab, 2004-01-03 alle 10:12, Hartmut Meyer ha scritto:
Hi,
Am Freitag, 2. Januar 2004 23:43 schrieb Mailing:
Il gio, 2004-01-01 alle 19:45, Hartmut Meyer ha scritto:
Am Mittwoch, 31. Dezember 2003 18:26 schrieb Mailing:
I discovered that Suse named wireless NIC wlanX instead ethX. This it's ok but the problem is that DSL YAST module doesn't give me the possibility to choose it. With Any other distribution is possible to use wireless PCMCIA to use DSL connections.
I think you're mixing things up. At least I'm not aware of any DSL modem that is connected via wlan to the computer. Of course their are plenty of those router devices that have a built-in DSL modem. However, the computer that gets connected to such a device (either normal ethernet or wlan) will not see any DSL specific thing. Therefore there is no need to configure PPPoE or PPPoA on your computer.
All you need to do is to configure your NIC with a default route to your router. The DSL specific stuff is done within this DSL router.
Thanks, but I connected my DSL ethernet modem to my access point; after I configured my NIC ethX (ex.) to setup DSL connection ... after I change the config. file and instead ethX I put in wlan0 (ex.). I already made it since Rehat or Mandrake ... with Suse is impossible (I hope no!). YAST DSL module configure my NIC (eth0) for the first time and when I try to change into IFCFG-DSL0 with "wlan0" .... brrrrr.
So what I made before with other distribution is possible .... now I'd like make it with Super Suse.
I'm not 100% sure I understood you. Anyway, have you configured the wlan connection as such? You won't be able to do that with the YaST2 DSL modul but instead you will need to configure the wlan part with the YaST2 network card module. In ideal case you can test the wlan connection with another computer in your local network befor trying DSL.
Does your access point also offer (more than one) ethernet port? If so you should first test DSL with a normal ethernet connection where both your computer and your DSL modem are connected via ethernet to the access point (which would work as a switch in this setup). Once this works and once you also have successfully setup and tested(!) wlan connection with another computer on your local network, you could try and replace the ethX with wlan0 in ifcfg-dsl0.
Greetings from Bremen hartmut
Hi, Am Montag, 5. Januar 2004 22:29 schrieb Mailing:
Thanks but what you advised me I've already tested. I configured eth0 and DSL0 (by YAST modul) that's ok; after I've setup wlan0 correctly on my network and after I replaced eth0 with wlan0 .... but .... nothing.
I got this message from "/var/log/messages" ... ***** Plugin passwordfd.so loaded. unrecognized option 'wlan0' *****
I see. The problem is that pppd accepts ethX as a device but not wlanX. I believe the wlanX thing is specific to SUSE. There are good reasons for it (just try to set up a laptop with different network profiles for wlan and normal ethernet environment - which module is to be loaded for ethX becomes sort of random - this is much nicer with wlanX). I'm not sure we will stick to it though. At least as of now kernel 2.6 uses ethX for the wireless devices too. I don't know if there are any plans to introduce the wlanX interfaces to the 2.6 kernel. What could be done now is to either patch pppd to accept wlanX (shouldn't be too difficult I would guess) or to use a non-SUSE kernel that doesn't use wlanX.
My view is that SuSE limit DSL YaST modul with the ethX interface and does not allow us to use "hotplug" interfaces
It's not about the YaST2 DSL modul but about the device naming and pppds (missing) ability to accept wlanX as a device. Greetings from Bremen hartmut
participants (2)
-
Hartmut Meyer -
Mailing