Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
A lame question: why cannot I access (or even ping) the router's lan ip address, or computers on wired lan from my notebook connected to the router via wi-fi?
It looks like as if the wired lan clients and the wifi lan clients would be completely separated by the router, whilst I triple checked and could not find any related configuration option on the admin interface of the router.
router: tplink tl-wr340g
notebook client: suse 11.1 (uses wpa-psk to connect to the router)
wired lan clients: suse 11.0 and suse 10.1 (the eth0 interfaces of both are configured as external interfaces, and sshd listens on each, ssh can connect to any of them from wired lan)
No. Network mask is 255.255.255.0.
Router lan ip is 192.168.0.1.
Clients on wired network use static ips below 192.168.0.10, and clients on wifi network use dhcp over 192.168.0.100.
Anyway, now I am starting to doubt whether my wifi network has any security: WPA2-PSK and AES are configured on the router, but:
iwlist wlan0 encryption
wlan0 2 key sizes : 40, 104bits
4 keys available :
: B3E5-FE71-7B8F-63BA-B55E-E452-1DC0-BA07 (128 bits)
Current Transmit Key: 
What does "Security modepen" mean? Would access to lan be disabled by the router because the wlan network is open?
In the meantime I could configure WPA2-PSK and made sure it works.
However, the solution is quite different: I have to manually bring down the eth0 "wired interface" each time I use wlan. Eth0 and wlan0 have different ips in the lan network address range, and it seems this caused some problems.
I wonder why the router cannot be configured to have separate wlan and wired lan networks, to avoid such problems, instead of having a single lan network comprising both...