SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm using an Edimax EW-7128G PCI Wireless Card. I've looked in the slackbook regarding wireless: http://www.slackbook.org/html/networ...-wireless.html
And followed those instructions. I tried both editing the generic section of rc.wireless.conf, including my 'essid' and 'key', as well as
To the end of the previous iwconfig code. This has created another problem for me. It makes it VERY slow to initialize an ssh session with the slackware machine, After entering
Code:
ssh user@darkstar
it takes about 25 seconds before prompting me for a password, as opposed to the previously 'instantaneous' response time. I tried deleting /dhcpcd-wlan0.info and /dhcpcd-wlan0.cache in /etc/dhcpcd/, but this has not helped. If anyone knows how to help even with JUST this part, I'd be thrilled.
Here are some more details. The appropriate driver is rt61pci:
(though this could have just been /etc/rc.d.rc.inet1 wlan0_start)
I didn't change anything else, but connection times out now when I try to ssh into this machine. Would setting up wireless have effected the eth0 connection? or somehow affect ssh requests? I can't help but think this is related to what I did earlier:
Code:
# dhcpcd wlan0
which made sending the initial ssh request so slow.
Can you ssh based on IP address?
Just look for the IP address that ifconfig reports, and put that in the place of "darkstar"
If ssh based on IP works, the issue maybe is DNS related...
And just to be sure: are the wireless and ethernet card connected to the same network or to different networks?
I cannot ssh/ping based on IP address either (I have the IP and the alias in /etc/hosts, and it has not been a problem until I set up wireless).
Code:
# ssh root@192.168.1.200
ssh: connect to host 192.168.1.200 port 22: Connection timed out
ping just hangs interminably without anything more than:
Code:
# ping 192.168.1.200
PING 192.168.1.200 (192.168.1.200) 56(84) bytes of data.
Here's a crude picture of the network:
(((-wireless--> Slackware desktop <--crossover cable--> linux laptop <--wireless-)))
both machines are wirelessly connecting to the internet on the same network. This setup worked fine before, the only change being the wireless connectivity of the slackware desktop.
The wireless IP addresses are dynamically assigned; and eth0 is statically assigned on both machines. (I think that is what you were asking.)
No, I was asking wheter it was a 192.168.1.0/24 network, or a 10.0.0.0/8 or something else. I should have been a little clearer when I asked my question, sorry for that.
Quote:
Originally Posted by noviciado
On the Slackware Desktop:
Code:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0
On the laptop:
Code:
/sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0
From this output, I can see you wirless network is a 192.168.1.0/24 network, with possible IP ranges from 192.168.1.1 to 192.168.1.254 . Your little wired network (over the crossover cable) is also a 192.168.1.0/24 network.
What happends is that when you try to connect to 192.168.1.200, your request is sent over the wrong link (wlan0 instead of eth0) or worse, it is dropped. (I don't know that much about routing)
As a rule of thumb, never allow network ranges to overlap.
If you configure your static IPs (on the wired interfaces) to something from another IP range (like 192.168.3.0/24), things should work. e.g. change the IP from the slackware box to 192.168.3.200 and from the laptop to 192.168.3.202)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
