5 Feb
2006
5 Feb
'06
11:40 a.m.
Hi
I'm using suse10.0 on my laptop an connect on web using centrino chip, so by using
command iwconfig; this works nicely except if I use key for encryption. Does I need a
specific package to provide authentification mechanism? Or Is there something to do in the
FireWall configuration? Actually allowed services are DNS and DHCP servers but also IPSec,
HTTP, HTTPS and SSH....
Thank you in advance for any suggestion
Regards
M.
5 Feb
5 Feb
3:37 p.m.
On Sunday 05 February 2006 12:40, Michel Maria-Sube wrote:
Hi
Hi Michel
I'm using suse10.0 on my laptop an connect on
web using centrino chip, so
by using command iwconfig; this works nicely except if I use key for
encryption. Does I need a specific package to provide authentification
mechanism? Or Is there something to do in the FireWall configuration?
No. Simply
setup in Yast.
Actually allowed services are DNS and DHCP servers but
also IPSec, HTTP,
HTTPS and SSH.... Thank you in advance for any suggestion
Regards
M.
Afaik, WPA doesn't work on all wireless devices, so use WEP instead.
I use here a WLAN with a D-LINK Airplus 650+ card. WPA doesn't work.
Google is your friend :-)
Al
6 Feb
6 Feb
7:06 a.m.
Hi,
On Sun, Feb 05, 2006 at 03:40:22AM -0800, Michel Maria-Sube wrote:
I'm using suse10.0 on my laptop an connect on
web using centrino chip, so
by using command iwconfig; this works nicely except if I use key for
encryption.
Does I need a specific package to provide authentification mechanism? Or Is
there something to do in the FireWall configuration? Actually allowed
services are DNS and DHCP servers but also IPSec, HTTP, HTTPS and SSH....
I guess you didn't receive any answers so far because your question is
not entirely clear.
If I understood correctly, you want to simply use your Wireless LAN with
encryption? The question then is, which type of encryption - WEP or WAP?
I don't have any experience myself for WAP, but I'd guess configuration-
wise, it shouldn't be that different from WEP, if it is at all supported
by your WLAN-card's driver. AFAIK, some cards don't support WAP yet.
In the case of WEP, you just tell your interface's driver the ESSID and
WEP-key you want to use ("iwconfig wlan0 essid whatever" for the ESSID
and "iwconfig wlan0 key xxxxx..." for the WEP key) and then you should
"see" the access point's MAC address when looking at the output of
iwconfig wlan0 (btw, adapt to your interface name of course). At this
point, you can configure the IP part.
For WEP at least, there's nothing whatsoever to be done with firewalling,
this is all below the IP layer.
Greetings & hth, Eric
7:26 a.m.
On Mon, February 6, 2006 08:06, Eric Dondelinger wrote:
Hi,
On Sun, Feb 05, 2006 at 03:40:22AM -0800, Michel Maria-Sube wrote:
There's a module in Yast exactly doing this. The commandline doesn't work,
I don't know why. (SuSE!!!). I had problems with the configuration by line
in the LGL, all config seemed correct but I couldn't see the access point.
I changed the parameters with yast and all goes fine. Strange!!!
I also found a little tool that is very useful. You can define different
wlan configurations and switch between them. See Control Center->Internet
and network->Wireless Network. If you don't see such a thing, install the
package kdenetwork3-wireless in Yast.
Al
I'm using suse10.0 on my laptop an connect
on web using centrino chip,
so
by using command iwconfig; this works nicely except if I use key for
encryption.
Does I need a specific package to provide authentification mechanism? Or
Is
there something to do in the FireWall configuration? Actually allowed
services are DNS and DHCP servers but also IPSec, HTTP, HTTPS and
SSH....
I guess you didn't receive any answers so far because your question is
not entirely clear.
If I understood correctly, you want to simply use your Wireless LAN with
encryption? The question then is, which type of encryption - WEP or WAP?
I don't have any experience myself for WAP, but I'd guess configuration-
wise, it shouldn't be that different from WEP, if it is at all supported
by your WLAN-card's driver. AFAIK, some cards don't support WAP yet.
In the case of WEP, you just tell your interface's driver the ESSID and
WEP-key you want to use ("iwconfig wlan0 essid whatever" for the ESSID
and "iwconfig wlan0 key xxxxx..." for the WEP key) and then you should
"see" the access point's MAC address when looking at the output of
iwconfig wlan0 (btw, adapt to your interface name of course). At this
point, you can configure the IP part.
For WEP at least, there's nothing whatsoever to be done with firewalling,
this is all below the IP layer.
Greetings & hth, Eric _______________________________________________
Lilux-help mailing list
Lilux-help(a)lilux.lu
http://lilux.lu/mailman/listinfo/lilux-help
--
Thanx
Al
7:34 a.m.
Hello Alex,
in SuSE, you have to execute SuSEConfig after a much of changes in your
configuration...
There are scripts in, which writes your config on the right places.
SuSE is generally not good, if you want to change things yourself.
It is possible too under some circumstances, that Yast owerwrites your
own config when it executes SuSEConfig...
Regards,
Michel
Alex schrieb:
On Mon, February 6, 2006 08:06, Eric Dondelinger
wrote:
Hi,
On Sun, Feb 05, 2006 at 03:40:22AM -0800, Michel Maria-Sube wrote:
There's a module in Yast exactly doing this. The commandline doesn't work,
I don't know why. (SuSE!!!). I had problems with the configuration by line
in the LGL, all config seemed correct but I couldn't see the access point.
I changed the parameters with yast and all goes fine. Strange!!!
I also found a little tool that is very useful. You can define different
wlan configurations and switch between them. See Control Center->Internet
and network->Wireless Network. If you don't see such a thing, install the
package kdenetwork3-wireless in Yast.
Al
I'm using suse10.0 on my laptop an connect
on web using centrino chip,
so
by using command iwconfig; this works nicely except if I use key for
encryption.
Does I need a specific package to provide authentification mechanism? Or
Is
there something to do in the FireWall configuration? Actually allowed
services are DNS and DHCP servers but also IPSec, HTTP, HTTPS and
SSH....
I guess you didn't receive any answers so far because your question is
not entirely clear.
If I understood correctly, you want to simply use your Wireless LAN with
encryption? The question then is, which type of encryption - WEP or WAP?
I don't have any experience myself for WAP, but I'd guess configuration-
wise, it shouldn't be that different from WEP, if it is at all supported
by your WLAN-card's driver. AFAIK, some cards don't support WAP yet.
In the case of WEP, you just tell your interface's driver the ESSID and
WEP-key you want to use ("iwconfig wlan0 essid whatever" for the ESSID
and "iwconfig wlan0 key xxxxx..." for the WEP key) and then you should
"see" the access point's MAC address when looking at the output of
iwconfig wlan0 (btw, adapt to your interface name of course). At this
point, you can configure the IP part.
For WEP at least, there's nothing whatsoever to be done with firewalling,
this is all below the IP layer.
Greetings & hth, Eric
_______________________________________________
Lilux-help mailing list
Lilux-help(a)lilux.lu
http://lilux.lu/mailman/listinfo/lilux-help
8:09 a.m.
Hi,
On Mon, Feb 06, 2006 at 08:34:50AM +0100, Michel Kohl wrote:
in SuSE, you have to execute SuSEConfig after a much
of changes in your
configuration...
There are scripts in, which writes your config on the right places.
That's correct for when you do changes in the SuSE configuration file(s).
SuSE is generally not good, if you want to change
things yourself.
It is possible too under some circumstances, that Yast owerwrites your
own config when it executes SuSEConfig...
ACK, that's precisely when you edit configuration files directly and don't
tell SuSE / yast not to touch them.
Theoretically though, there's nothing that should prevent you from setting
parameters directly, such as in the network case, using ifconfig/iwconfig.
The only thing that comes to mind would be a DHCP client daemon that'd
reset your network values (as happened in the mailserver tutorial during
LinuxDays), so you'd have to kill that first.
Greetings, Eric (no, not getting into distro wars)
8:25 a.m.
Eric Dondelinger wrote:
This used to be a problem with *way* old SuSE distributions (until
6.x?). Nowadays, SuSE keeps an checksum of those files that it
generated, and if that checksum no longer matches, the files are not
overwritten.... which can be just as puzzling though, if you actually
*want* to change things using YaST after you first did a manual change.
Moreover, nowadays the configuration is much more modular (config
_directories_ rather than files: /etc/xinetd.d, /etc/apache2/conf.d,
...) so this is even less of an issue.
In the LLL highschools, we modify certain settings manually, and others
via YaST, and we rarely run into problems. But yes, a couple of years
ago, this overwriting of config files used to be a huge problem.
Nowadays it is solved for most cases.
Regards,
Alain
SuSE is
generally not good, if you want to change things yourself.
It is possible too under some circumstances, that Yast owerwrites your
own config when it executes SuSEConfig...
ACK, that's precisely when you edit configuration files directly and don't
tell SuSE / yast not to touch them. 
7:21 p.m.
Alain Knaff wrote:
In the LLL highschools, we modify certain settings
manually, and others
via YaST, and we rarely run into problems. But yes, a couple of years
ago, this overwriting of config files used to be a huge problem.
Nowadays it is solved for most cases.
Well, last time I changed something in xorg.conf in SuSE 10, I was
unable to change apparently unrelated things in YaST, for example the
keyboard settings. I clicked, and nothing happened, no error message.
It appears that those functions all use SaX2. When I ran SaX2 from the
command line, it complained about an invalid checksum. I had to run
`sax2 -r` to rebuild the checksums, after which that part of YaST worked
again.
So I believe that you can still run into those troubles today.
Regards,
-pu
6857
days inactive
6857
days old
7 comments
7 participants
participants (7)
-
Alain Knaff -
Alex -
Alex -
Eric Dondelinger -
Michel Kohl -
Michel Maria-Sube -
Patrick Useldinger