wireless setup

wiliamvw · 03-14-2016, 05:32 PM

Downloaded and burned and installed the official OS [not the purchased dvd]; installed new on / and able to save /home files and get all woking for all users.
Selected Networkmanager for config and got confirmation that NM was running -- but still no internet [but Firefox and all else running great] nor NM listing anywhere and when tried for data on NM got: Network Manager PID as 644, and its installed size as 0 [ZERO].
In listing Network Interfaces got: Name:lo IP:127.0.0.1 Mask:255.0.0.0 Type:loopback
With still no server found for firefox, I tried some inserts with rc.conf so eth1 read DHCP "yes" and uncommented wlan0 and made that "yes".
Still no wifi access and will next try wicd again unless someone has a suggestion as to how to make work what already have in place.

onebuck · 03-14-2016, 05:51 PM

Hi,

When using network manager, the '/etc/rc.d/rc.intet1.conf' should be in the original install state with no modifications.

bassmadrigal · 03-14-2016, 06:04 PM

As onebuck mentioned, you should keep rc.inet1.conf unedited if you're using Network Manager or wicd. Not doing that will cause conflicts that can prevent you from getting access.

Is your wireless card detected properly? What's the output of the following commands?

Code:

lspci -k | grep -iA3 net
iwconfig

jostber · 03-15-2016, 02:37 AM

Quote:

Originally Posted by wiliamvw

Does wicp give IP? Yes,says: connected to CLP-Main Library Nickname: Go333 at -42 dBm (IP: 10.50.13.158)
Tried browsers Konqueror and Seamonkey and get less than via Firefox.
Problem may well be in /etc/resolv.conf since have no nameservers there. All that shows is:
#Generated by dhcpcd
#/etc/resolv.conf.head can replace this line
#/etc/resolv.conf.tail can replace this line ; then I deleted word tail and what followed and replaced it with: 10.50.13.158 in hopes this might get to local server, but did nothing and likely was not an appropriate entry.

If that line can be replaced by something useful please advise.

As to install medium, I used a dvd from osdisc and first time I used it had no problems until some new installs of dependencies messed it up and had to do this new full install.
As I have everything on 3 partitions [ swap /(with boot) /home] could I safely do a new install deleting and replacing only / and that way fix any systemic problems while retaining all my files and users?

Again, thanks for your time and attention, I know this problem is a real drag.

If you get an IP address in wicd, you should be pretty close. Can you try to connect with wicd again. Don't change anything in resolv.conf or the inet files, as well as in firefox. When connected try to ping www.google.com and post the results here.

genss · 03-15-2016, 09:27 AM

8.8.8.8 is the google DNS, you can put it there as a nameserver

dhcp should give you a DNS address

also run route as root and see if the gateway is set up there

another thing to do is to ping all those things to make sure

wiliamvw · 03-15-2016, 01:30 PM

Firstly, I have not tried anything involving wicd so as not to interfere with other configurations [have installed its app but not activated].
entering "route" gives: Kernel IP routing table:
Destination Gateway Mask Flags Metric R Use Iface
loopback * 255.0.0.0 U 0 0 0 lo
169.254.0.0 * 255.255.0.0 U 302 0 0 eth1
169.254.247.9 localhost 255.255.etc UGH 302 0 0 lo

Entering "dhcp" gives command-not-found

Pinging www.google.com gives "unknown host"
Pinging 8.8.8.8 gives "Network is unreachable"

lspci -k | grep -iA3 net
gives: 02:01.0 Network Controller: Intel Corp PRO/Wireless 2200BG Network Connection (rev 05)
Subsystem: Intel Corp WM3B2300BG Mini-PCI card; Kernel Driver in use: ipw 2200 Kernel modules: ipw 2200

02:02.0 Ethernet controller: Realtek Semiconductor Co Inc RTL-81391etc
Subsystem: Twinhead Intern Corp Device 020b Kernel driver in use: 8139t00 Kernel modules: 8139t00

iwconfig gives:
lo no wireless extension
eth0 no wireless extension
eth1 IEEE 802.11bg Essid: off/any Nickname: "GO333" Mode: Managed Channel:0 Access Point: Not-Associated Bit Rate: 0 kb/s Tx-Power=20dBm Sensitivity=8/0
Retry Limit: 7 RTS thr: off Fragment thr: off Encryption key: off Power Management: off
Link Quality: 0 Signal Level: 0 Noise Level: 0 Rx invalid nwid: 0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries: 0 Invalid misc: 0 Missed beacon: 0

genss · 03-15-2016, 03:34 PM

sry, bad formatting

dhcp is the protocol that one computer uses to get network wiring information from a dhcp server (usually the router)

iwconfig tells you that the network is not connected ( Access Point: Not-Associated )

could be a wrong password, no/wrong firmware, bad driver, some special network or just bad setup

wicd would probably say if it was the wrong password

oh, you said networkmanager worked ?
well just remove or disable wicd then

although there is no reason for wicd not to work

to make sure it's clean first disable all the managers and see if dhcpcd or wpa_supplicant are running
they shouldn't run unless something starts them

you can also try connecting manually
if it is wep you can connect via iwconfig or iw, while for wpa you need to use wpa_supplicant
before that you might need to raise the interface ( ifconfig eth1 up )
then you just run dhcpcd on the interface
(as root ofc, say if you want to know how)

idk what else to say

wiliamvw · 03-15-2016, 05:15 PM

No, NM is running but not working, and no managers working; will wait on wicd until have no other option, since last time it didn't function correctly.

bassmadrigal · 03-15-2016, 06:55 PM

Ok, let's try doing things manually first so we can verify whether or not the hardware/software is working. For now, you can disable Network Manager.

Code:

su
/etc/rc.d/rc.networkmanager stop
chmod -x /etc/rc.d/rc.networkmanager

Now, let's set up a temporary config for wpa_supplicant. Try the following, replacing $SSID and $PASSPHRASE with your router's SSID and the password/passphrase.

Code:

wpa_passphrase $SSID $PASSPHRASE > ~/wpa.conf

You should have something like the following in there.

Code:

network={
        ssid="myrouter"
        #psk="mypassphrase"
        psk=8ada1f8dbea59704ac379538b4d9191f6a72390581b4cd7a72864cea685b1a7f
}

Now, we want to start wpa_supplicant and point it to your config file (yes, that is the correct format... not sure why they decided to not have spaces like most commands). (NOTE: the -Dnl80211 uses the current standard nl80211 driver, however, not all chips support it, so if you have issues with that, you could try switching it to -Dwext)

Code:

wpa_supplicant -Dnl80211 -ieth1 -c~/wpa.conf

There should be some output now, hopefully including something about authenticating with your access point. You should be able to verify this using iwconfig (instead of it saying Access Point: Not-Associated, it should show your access point).

If this works, then you'll need to get an IP address. Now, type the following.

Code:

dhcpcd eth1

It should dump a few lines including your IP address. From this point, try pinging google.

Code:

ping google.com

If this works, great! You're online. If it doesn't let's verify it's connected by looking at the output of iwconfig and verifying your dhcp server populated your resolv.conf file properly by checking cat /etc/resolv.conf. If that looks suspect, we can try pinging google's IP directly, preventing your computer from needing a nameserver.

Code:

ping 74.125.29.101

Let us know what happens with this. If you're able to get it connected, then we're looking at an issue with Network Manager that we can try to figure out. If it doesn't work, past the various output into here (preferably using the [code][/code] tags to improve readability) and we'll try to troubleshoot further.

NOTE: I don't have any Linux systems with wireless, so a lot of this is off the top of my head, but I'm pretty sure my memory hasn't failed me of this just yet

genss · 03-15-2016, 07:07 PM

Quote:

Originally Posted by bassmadrigal

(yes, that is the correct format... not sure why they decided to not have spaces like most commands)

you can put spaces if you want, i do

bassmadrigal · 03-15-2016, 09:32 PM

Quote:

Originally Posted by genss

you can put spaces if you want, i do

Good to know! Thanks. I haven't played around with wireless on Slackware since at least 12.1 (since I know they didn't have wicd when I did, and that was added in 12.2).

onebuck · 03-16-2016, 11:42 AM

Hi,

Quote:

Originally Posted by wiliamvw

Firstly, I have not tried anything involving wicd so as not to interfere with other configurations [have installed its app but not activated].
entering "route" gives: Kernel IP routing table:
Destination Gateway Mask Flags Metric R Use Iface
loopback * 255.0.0.0 U 0 0 0 lo
169.254.0.0 * 255.255.0.0 U 302 0 0 eth1
169.254.247.9 localhost 255.255.etc UGH 302 0 0 lo

Entering "dhcp" gives command-not-found

Pinging www.google.com gives "unknown host"
Pinging 8.8.8.8 gives "Network is unreachable"

lspci -k | grep -iA3 net
gives: 02:01.0 Network Controller: Intel Corp PRO/Wireless 2200BG Network Connection (rev 05)
Subsystem: Intel Corp WM3B2300BG Mini-PCI card; Kernel Driver in use: ipw 2200 Kernel modules: ipw 2200

02:02.0 Ethernet controller: Realtek Semiconductor Co Inc RTL-81391etc
Subsystem: Twinhead Intern Corp Device 020b Kernel driver in use: 8139t00 Kernel modules: 8139t00

iwconfig gives:
lo no wireless extension
eth0 no wireless extension
eth1 IEEE 802.11bg Essid: off/any Nickname: "GO333" Mode: Managed Channel:0 Access Point: Not-Associated Bit Rate: 0 kb/s Tx-Power=20dBm Sensitivity=8/0
Retry Limit: 7 RTS thr: off Fragment thr: off Encryption key: off Power Management: off
Link Quality: 0 Signal Level: 0 Noise Level: 0 Rx invalid nwid: 0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries: 0 Invalid misc: 0 Missed beacon: 0

How are you getting your Internet? Via local modem for DSL or cable modem? ISP and provided equipment to you?

The IP 169.254.0.0 for eth1 is a link-local address, see https://en.wikipedia.org/wiki/Link-local_address
That IP indicates you are not getting a valid dhcp assignment but defaulting to a local link IP;

Quote:

From https://en.wikipedia.org/wiki/Link-local_address In a computer network, a link-local address is a network address that is valid only for communications within the network segment (link) or the broadcast domain that the host is connected to.
Link-local addresses are usually not guaranteed to be unique beyond a single network segment. Routers therefore do not forward packets with link-local addresses.
For protocols that have only link-local addresses, such as Ethernet, hardware addresses that the manufacturer delivers in network circuits are unique, consisting of a vendor identification and a serial identifier.
Link-local addresses for IPv4 are defined in the address block 169.254.0.0/16, in CIDR notation. In IPv6, they are assigned with the FE80::/10 prefix. [1]

Address assignments;

Quote:

Link-local addresses may be assigned manually by an administrator or by automatic operating system procedures. For Internet Protocol (IP) networks, they are assigned most often using stateless address autoconfiguration. In IPv4,[2] they are normally only used to assign IP addresses to network interfaces when no external, stateful mechanism of address configuration exists, such as the Dynamic Host Configuration Protocol (DHCP), or when another primary configuration method has failed. In IPv6,[3] link-local addresses are mandatory and required for the internal functioning of various protocol components.
Automatic address configuration of link-local addresses is often non-deterministic as the resulting address cannot be predicted. However, in IPv6 it is usually derived automatically from the interface media access control (MAC) address in a rule-based method.

Your output above does show that no DHCP assignments or lack of communicating with a server thus the fallback to a link-local assignment.
I have re-read the thread and at one point you stated wicd showed some available SSID and you could select one. That tells me at one time your wireless was able to scan for available SSID thus functional radio.

Do you have a modem that will provide a dhcp server? Tell us what you have on your local network. Equipment list by name/manufacture/model to let us know what to look for. What is your wireless card/chipset manufacture & model number? You should find this via 'lspci -vv' from the cli as root. Or look at 'dmesg' from the cli to see what the kernel recognizes at boot for your devices.

To use DHCP on a LAN there must be a server to provide clients assignments and control.

Please post your current '/etc/rc.d/rc.inet1.conf' file. I do suspect a configuration issue. You stated that fresh install has been done. You did this from a verified ISO?

A good Slackware network reference is AlienBob's; http://alien.slackbook.org/dokuwiki/...ckware:network

You could consider a Static IP setup using the link above.
I am wondering about the wireless assignment as eth1. What card/chipset are you using? Post the content of /etc/udev/rules.d/70-persistent-net.rules This will show the PCI information and kernel driver in use(clue to device in use). You could try disabling the eth0 NIC via BIOS. Delete /etc/udev/rules.d/70-persistent-net.rules then reboot to generate a new /etc/udev/rules.d/70-persistent-net.rules file. This will likely assign the wireless device so any configuration would be for that device. Early Broadcom chip-sets would mangle the setup and use the eth1 as wireless device. If so then you may need to get the current firmware for your wireless device.

Not to throw you off but You should consider using http://taper.alienbase.nl/mirrors/sl...e-live/latest/ ISO for Slackware64 Live. If you download the ISO verify it with the md5sum code(.md5 file) from that site. Burn the image at a low write speed (4 should be alright) to a CD/DVD (this media type will depend on which ISO you download), XFCE is the smallest and would fit on a CD, others would require a DVD and verify the burnt ISO. Note that these ISO are based on '-current' and should provide you with the latest updates and hopefully configure your hardware properly.

A live session should allow you to configure the hardware and provide you with the means to get hardware information to provide back to us.

Hope this helps.
Have fun & enjoy!

onebuck · 03-16-2016, 12:38 PM

Hi,

Eric provides a method to use 'live' without burning image to media.

Quote:

What's new in 0.7.0?

I could not spare as much time as for the previous betas (work comes first because it pays for food and shelter). So the new ISO images are primarily meant to be a showcase of both Slackware -current and the new Plasma 5 version. Still, there are a few things to mention.

The scope of the boot parameter "livemedia" has been extended. It will now also accept an ISO file (containing Slackware Live Edition of course) as parameter value, so that you can more easily test a freshly downloaded ISO without having to copy it to a USB stick or burn it to a DVD first. It's use is quite versatile:
- "livemedia=/dev/sdX1:/path/to/live.iso" points to an ISO file on partition "/dev/sdX1".
- "livemedia=DATA:/path/to/liveslak.iso" points to an ISO file on a filesystem with label "DATA".
- "livemedia="7550954e-3d40-4e46-ae91-d02dce1d52a4:/your/live.iso" points to an ISO file on a partition with a specific UUID.

From blog; http://alien.slackbook.org/blog/new-...dition-beta-7/

Quote:

What’s new in 0.7.0?

I could not spare as much time as for the previous betas (work comes first because it pays for food and shelter). So the new ISO images are primarily meant to be a showcase of both Slackware -current and the new Plasma 5 version. Still, there are a few things to mention.

The scope of the boot parameter “livemedia” has been extended. It will now also accept an ISO file (containing Slackware Live Edition of course) as parameter value, so that you can more easily test a freshly downloaded ISO without having to copy it to a USB stick or burn it to a DVD first. It’s use is quite versatile:
- “livemedia=/dev/sdX1:/path/to/live.iso” points to an ISO file on partition “/dev/sdX1″.
- “livemedia=DATA:/path/to/liveslak.iso” points to an ISO file on a filesystem with label “DATA”.
- “livemedia=”7550954e-3d40-4e46-ae91-d02dce1d52a4:/your/live.iso” points to an ISO file on a partition with a specific UUID.
A new boot parameter “nga” was added. It stands for “no glamor acceleration” and should be useful on hardware (including QEMU virtual hardware) where X.Org refuses to start with the error “EGL_MESA_drm_image required; (EE) modeset(0): glamor initialization failed“. It adds a file to /etc/X11/xorg.conf.d/ to disable glamor 2D acceleration, something which used to be off by default and since X.Org 1.18 seems to be on by default.
The “setup2hd” hard disk installer was polished a little bit.
A wiki-fied version of the README.txt documentation was added to the Slackware Documentation Project. See http://docs.slackware.com/slackware:liveslak.
Documentation on how to customize the Live Edition for your own Slackware derivative was added. This is a work in progress – I still need to separate the syslinux and grub theming from the menu content.
Lots of small improvements and bug fixes were applied to liveslak. Check out the commit log if you are interested.

Download the ISO images

I have created ISO images for the SLACKWARE, XFCE, PLASMA5 and MATE flavours using the latest Slackware64-current packages available (Mon Mar 14 02:18:20 UTC 2016) as well as the latest Plasma 5 release which I yet have to upload to ‘ktown‘… you will see it first on Slackware Live Edition!
You can find the ISO images plus their MD5 checksum and GPG signature at any of the following locations – look in the “0.7.0” subdirectory for ISOs based on the liveslak-0.7.0 scripts. I made a symlink called “latest” which will always point to the latest set of ISO images:

Primary location: http://taper.alienbase.nl/mirrors/slackware-live/ (please do not download from here, use a mirror)
Darren’s mirror (fast!): http://slackware.uk/people/alien-slacklive/ (rsync://slackware.uk/people/alien-slacklive/)
Willy’s mirror: http://repo.ukdw.ac.id/slackware-live/
Ryan’s mirror: https://seattleslack.ryanpcmcquen.or...lackware-live/
Shasta’s mirror: http://ftp.slackware.pl/pub/slackware-live/ (rsync://ftp.slackware.pl/slackware-live/)
Tonus’s mirror: http://ftp.lip6.fr/pub/linux/distrib...ien-slacklive/

These mirror servers will sync up in the next 24 hours – slackware.uk is already uptodate.
Good to know when you boot the ISO

Slackware Live Edition knows two user accounts: root (with password ‘root’) and live (with password ‘live’). My advice: login as user live and use “su” or “sudo” to get root access.
Note: the “su” and “sudo” commands will want the ‘live’ user’s password!
Slackware Live Edition is able to boot both on BIOS-based computers (where syslinux takes care of the boot menu) and UEFI systems (where grub builds the boot menu, which looks quite similar to the syslinux menu):

Hope this helps.
Have fun & enjoy!

wiliamvw · 03-17-2016, 03:19 PM

Will try to answer all questions possible. Regards the request by bassmadrigal for router SSID and router password, since I have only wireless and even that only via library or public site "guest click-in", I don't have either [or not aware of them].

I use GoBook III ix260+ by Itronix {now, General Dynamics}. Memory is 32-bit non-prefetchable.
Intel w. Subsystems by Twinhead Intern. device 3580 and for USB & IDE devices 24cc and c90a.
Modem: Intel, Twinhead device 1009
VGA: AMD/ATI, Twinhead device 0311, Mobility FireGL9000/Radeon 9000.
Network controller: Intel PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05); Subsystem: Intel WM3B2300BG Mini-PCI Card.
Ethernet Controller: Realtek Semic. RTL-8139/8139c/8139c+ Subsystem Twinhead device 020b
CardBus bridge: 02 Micro, Inc. 02711M1/MC1 4-in-1 Memory Card Bus
Firewire Ricoh Co. R5C551 IEEE 1394

Current file of /etc/rc.d/rc.inet1.conf :
Config eth0: all no entry: ""
Config eth1: all no entry except USE__DHCP[1]="yes"
Config eth2 & eth3: all no entry: ""
GATEWAY=""
DEBUG_ETH_UP="no"
IFNAME[4]="wlan0" {this and 4 below only recently entered when had no success with what already there}
IFADDR[4]=""
NETMASK[4]=""
USE_DHCP[4]="yes"
DHCP_HOSTNAME[4]="icculus-wireless"
ALL OTHER LINES ARE COMMENTED OUT.

Contents of /etc/udev/rules.d/70-persistent-net.rules is as follows:
PCI device 0x10ec: /sys/devices/pci0000:00/0000:00:1e.0/0000:02:02.0 (8139too)
SUBSYSTEM="net", ACTION="add", DRIVERS=="?*", ATTR{address}=="00:40:45:26:8e:08" ATTR{dev_id}=="0x0" ATTR{type}=="1" KERNEL=="eth*" NAME="eth0"
or for PCI device 0x8086 have these differences: (ipw2200) ATTR{address}=="00:12:f0:23:2b:06" and NAME="eth1"

When removed /etc/udev/rules.d/70-persistent-net.rules and rebooted, had settings list connection as "wired" in place of wireless as before and suddenly wicd networkmanager came on [but while again found some connections to attach to, could never find server to get on line].

bassmadrigal · 03-18-2016, 09:32 AM

Quote:

Originally Posted by wiliamvw

Config eth1: all no entry except USE__DHCP[1]="yes"

As has been stated several times, if you use Network Manager, you don't make changes to /etc/rc.d/rc.inet1.conf, and that includes the entry for USE_DHCP. Try reverting that and using Network Manager to connect to a network. If you still can't connect to the internet, post the output of the following commands.

Code:

iwconfig
ifconfig
cat /etc/resolv.conf
ping -c 4 google.com
ping -c 4 74.125.29.101

Also, as previously requested, please put the output of those commands within [code][/code] tags to improve the readability of your posts.