LinuxQuestions.org - Slackware 12.2 internet connection via WiFi problems

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Slackware 12.2 internet connection via WiFi problems (https://www.linuxquestions.org/questions/slackware-14/slackware-12-2-internet-connection-via-wifi-problems-693424/)

Aahhhh.... Ich kann das nicht glauben!!!
After a week of suffer I'm in the internet from my Slackware 12.2. I really don't know what was the problem. The file was executable and I've also tried to comment that stuff. It didn't help... But now I've been experimenting with setting the route and the gateway manually after what I've used dhcpcd. It's unbelivable but I got response and now I'm here. So, I guess I'll have to analyse what I've done in the command line.

Aha it's this:

Code:

root@DarkStar:~# ping 216.239.59.104

connect: Network is unreachable

root@DarkStar:~# route add -net 192.168.0.0 netmask 255.255.255.0 wlan0

root@DarkStar:~# route add default gw 192.168.0.1

root@DarkStar:~# route

Kernel IP routing table

Destination    Gateway        Genmask        Flags Metric Ref    Use Iface

root@DarkStar:~# route add -net 192.168.0.0 netmask 255.255.255.0 wlan0

root@DarkStar:~# route add default gw 192.168.0.1

root@DarkStar:~# route

Kernel IP routing table

Destination    Gateway        Genmask        Flags Metric Ref    Use Iface

192.168.0.0    *              255.255.255.0  U    0      0        0 wlan0

default        192.168.0.1    0.0.0.0        UG    0      0        0 wlan0

root@DarkStar:~# ping 216.239.59.104

PING 216.239.59.104 (216.239.59.104) 56(84) bytes of data.

^C

--- 216.239.59.104 ping statistics ---

15 packets transmitted, 0 received, 100% packet loss, time 14024ms



root@DarkStar:~# /etc/rc.d/rc.inet1 restart

/sbin/dhcpcd: not running

/etc/rc.d/rc.inet1:  wlan0 information: 'Any ESSID'

Error for wireless request "Set Nickname" (8B1C) :

    SET failed on device wlan0 ; Operation not supported.

Polling for DHCP server on interface wlan0:

Broadcasting DHCP_DISCOVER

dhcpIPaddrLeaseTime=4294967295 in DHCP server response.

dhcpT1value is missing in DHCP server response. Assuming 2147483647 sec

dhcpT2value is missing in DHCP server response. Assuming 3758096383 sec

DHCP_OFFER received from ÿ (192.168.2.1)

Broadcasting DHCP_REQUEST for 192.168.2.21

dhcpIPaddrLeaseTime=4294967295 in DHCP server response.

dhcpT1value is missing in DHCP server response. Assuming 2147483647 sec

dhcpT2value is missing in DHCP server response. Assuming 3758096383 sec

DHCP_ACK received from ÿ (192.168.2.1)

Broadcasting ARPOP_REQUEST for 192.168.2.21

root@DarkStar:~#

Greetings,
I find it interesting that Puppy Linux installs on a thumbdrive and the Connection Manager is on the desktop and starts and scans a wifi network is seconds. But a 5gig installation like slackware can't preinstall ndiswrapper or include a decent network setup program. And ps where are all those A to Z programs that were installed with the full install on the start menu? I not knocking Slackware, Ubuntu and Opensuse are just as bad. 20 gig of Linux DVDs and the only one that works right is a 92 meg Puppy installation. At least I have internet so I can search the forums for info on all these other worthless systems.
Just my 2 cents worth
tlcstat

ticstat, does what you say helps anybody ? Bad digestion, maybe :scratch:

Greetings,
Depends! It should give them a heads up on a very small distro that runs wifi very well. That will at least give them internet so that they can search for the answers to all these big distro problems without going over to their neighbors pc to use internet.
It makes sense to me that to be usable the GUI should at least have the installed programs on the start menu and a decent network utility. Especially since the synaptic and apt-get need a network connection.
So to answer your question. If the developers are listening then, Yes it should help everybody. Hello! Are you listening!
tlcstat

Quote:

Originally Posted by tlcstat (Post 3391912)

It makes sense to me that to be usable the GUI should at least have the installed programs on the start menu and a decent network utility. Especially since the synaptic and apt-get need a network connection.

FYI:
- Some (most ?) slackers don't use GUI very often.
- E.g. I use a Fluxbox WM without any icon nor visible start menu (though I can access one with a right click). I prefer to access the apps I often use with keyboards shortcuts, it's *a lot* faster.
- Synaptic and apt-get are useless for most slackers, who use Slackware tools for packages management instead.
- I won't speak for other people, but slackware network-scripts package is all I need to connect my laptop to the Internet, be it by wire or wireless.

Thus:
- I believe you've heard about Slackware, but I wouldn't bet you really know it.
- I understand that Puppy Linux fits your needs. Very well, but that doesn't mean it fits everybody's needs and it doesn't -- otherwise why wouldn't everybody use it ?
- If you don't receive an immediate and enthusiastic response from the developers to your last post, may I suggest you contact them directly. To begin with you could write to Patrick Volkerding, who as you probably know is Slackware's creator and still it's main developer. You'll find his email address on following website:
http://slackware.com

Take care,

Greeting,
However, the Slackware 12 does indeed have a GUI and so it should work like one. A GUI isn't something to just to look at until you get to the terminal. I been on computers since MSDOS 1.0 so I know how you feel about the command prompt. I've always liked it myself. Thing is it just isn't very functional for the everyday user. Internet, Checkbook etc are all better in a GUI.
Interesting thing, I downloaded the Knoppix Live CD a few minutes ago. It had Ndiswrapper build in with plenty of other nice software. I copied my Widows drivers to a pendrive and had my wifi going in about ten minutes with the wrapper. Seems to me that slackware could do at least that much on a 4gig DVD. Especially since Ndiswrapper is only about 20k. If the Linux community wants to win over Windows users then they are going to have to build in a workable wifi solution. Thats the modern world. And that means a Graphical Wlan Connection manager that works. If I can get that with Puppy Linux and Knoppix then I should be able to get it from a 4Gig Slackware installation. After all whats a extra hundred kilobytes.
Anyway, enjoyed your comments.
tlcstat

Quote:

Originally Posted by tlcstat (Post 3392061)

Greeting,
However, the Slackware 12 does indeed have a GUI and so it should work like one

Nope. By itself Slackware has no GUI: it provide apps which include one, which is very different.

Quote:

Internet, Checkbook etc are all better in a GUI.

It's *your* opinion. There *are* Internet browsers without GUI, e.g. lynx.

Quote:

I copied my Widows drivers to a pendrive and had my wifi going in about ten minutes with the wrapper.

Configure a wireless connection with Slackware takes me less than 3 minutes. And I have nothing to grab from elsewhere, all is included in the distro.

Quote:

If the Linux community wants to win over Windows users then they are going to have to build in a workable wifi solution.

AFAIK the Linux community has several workable wifi solutions. Side note: I personally don't want to win over Windows users. I only want a system which fit my needs. And Slackware Linux does.

Quote:

And that means a Graphical Wlan Connection manager that works.

Slackware 12.2 *does* include a Graphical Wlan manager that works. It's called wicd. Anybody can use it, if he/she wants to.

Now I don't intend to convince you to use a system you don't like. But you are wasting your time trying to convince me to use another one that Slackware, or that Slackware should be different that what it is.

And may be I'm wasting my time in answering you about that. But that's my fault, not yours :(

Anyway, it'll be a pleasure to try to help you when you'll decide to install Slackware. :cool:

legeipsnelU:

Did you try wicd as suggested in an earlier post? I used to use manual config scripts and wpa_supplicant, etc., but ever since wicd I have found wireless access to be very simple.

Brian

Quote:

Originally Posted by onebuck (Post 3390212)

Hi,

You should look at 'Configuring your network in Slackware'.

What files did you modify in '/etc'? You should make your system changes from the 'cli' instead of your desktop. If you make changes system wide as root then you can restart the 'inet' from the 'cli' by; '/etc/rc.d/rc.inet1 restart'.

This link and others are available from 'Slackware-Links'. More than just Slackware® links!

I finally got my wireless to work, with the help of your link (configure your network in Slackware) thank you.

I installed my slackware full install and did not run netconfig, and then I only modified my /etc/rc.d/rc.inet1.conf. My network used the eth1 interface so I just modified this one to fit my needs, and then I restarted it doing /etc/rc.d/rc.inet1 INTERFACE_RESTART

and it worked! I did spend a long time reading different things but now it's working. I can rest in peace.

Quote:

Originally Posted by Foress_89 (Post 3394248)

That's what you think.