need help with network

apertotes · 2008-07-27 02:10:39

hi, i am trying to leave ubuntu, so i installed Arch Linux. it seems everything went allright on the CD installation, but i am having trouble with the network. i have a dell XPS M1330 with the intel 4965 card, and i believe that the card is recognized by the system.

i can scan for networks, and i can even connect to my network, and when i run "iwconfig" i can see all my network details, including the password, and th signal strenth, noise, etc.

so, everything indicates that i am succesfully connected to my network. but everytime i try a ping it fails misserably, with a host unknown. i've tried google, yahoo, msn... but it doesnt matter. they always fail.

can anybody help me?

btw, i've checked that hostname is the same on rc.conf and hosts

monstermudder78 · 2008-07-27 02:45:36

Can you ping your router or another machine on your network?

megagram · 2008-07-27 02:58:15

Sounds like you haven't given your network interface a suitable IP address...

You have connected to your wireless network (layer 1--akin to plugging in an Ethernet cable) but you haven't set up the addressing yet.

You can do this manually, or preferably--and easier--use a DHCP client. dhcpcd or dhclient both work. I think dhcpcd is installed by default. Find out the name for your wireless device it'll be something like wlan0 or eth0 or whatever. ifconfig will tell you.

Now, type:

sudo dhcpcd wlan0

Where wlan0 is actually the name of your wireless NIC.

Enjoy!

apertotes · 2008-07-27 03:13:16

everytime i do that, i get an error saying that my device is already running and gives me a 4 digit number.

megagram · 2008-07-27 07:02:40

OK. Probably dhcpcd started automatically at boot time when you weren't associated with your wireless network.

You can safely stop it and start it again hoping to get an IP address after you have associated with your network.

To do this type:

sudo kill 1234

Where "1234" is the number that the error message gives you (aka the PID or Process ID).

Now, retype the "sudo dhcpcd..." command as in my previous post.

Also, make sure you are entering the right interface ID for dhcpcd. Use the same ID that iwconfig lists as the active wireless device.

It might be useful for you to paste the outputs of "ifconfig" and "iwconfig" for us to see.

apertotes · 2008-07-27 13:08:17

monstermudder78 wrote:

Can you ping your router or another machine on your network?

no, i cant. it gives me the same error than with google. unknown host or something like that

megagram wrote:

OK. Probably dhcpcd started automatically at boot time when you weren't associated with your wireless network.
You can safely stop it and start it again hoping to get an IP address after you have associated with your network.
To do this type:
sudo kill 1234
Where "1234" is the number that the error message gives you (aka the PID or Process ID).
Now, retype the "sudo dhcpcd..." command as in my previous post.
Also, make sure you are entering the right interface ID for dhcpcd. Use the same ID that iwconfig lists as the active wireless device.
It might be useful for you to paste the outputs of "ifconfig" and "iwconfig" for us to see.

ok, this is what i did.

first of all, after login, "iwconfig", and the output was something along the lines of "no network connection found"

then, i did "modprobe iwl4965", and then "iwconfig" again, and this time i got the regular output with the name of the network (wlan0) and its properties, but no "essid" yet

so i did a "iwconfig wlan0 essid apertotes key xxxxxxxx", and then "iwconfig" again, and then i could see that i was connected to my essid (apertotes) but the password wasnt applied, so i had no access point.

so i did a "ifconfig wlan0 up", then repeated "iwconfig wlan0 essid apertotes key xxxxxxxx", and then, i run "iwconfig" and everything was allright. i could see my essid, the password, and the wifi properties (signal strenth, noise, etc)

then i did "dhcpcd wlan0" and after some seconds (20 or so) i got

"err, wlan0: timed out
warn, wlan0: using IPV4LL address 169.254.79.175"

i repeated "dhcpcd wlan0" and this time, it was inmediate, and the output was

"err, wlan0: dhcpcd already running on pid 2395 (/var/run/dhcpcd-wlan0.pid)"

so i did a "kill 2395", and then i repeated the last 2 steps, but the outcome was exactly the same.

ps: i tried also with "sudo", but since i am loged in as root i guess its the same. in fact, i didnt have any success with "sudo dhcpcd wlan0" either

Last edited by apertotes (2008-07-27 13:14:44)

monstermudder78 · 2008-07-27 18:21:45

Can you post the portion of your /etc/rc.conf that deal with networking and the DAEMONS= section?

Edit: What type of security are you using and is it supported by the driver for your wireless card? Might try and connect with no security first.

Last edited by monstermudder78 (2008-07-27 18:24:46)

gils0040 · 2008-07-27 21:38:45

That network card requires intel's microcode to work properly. First I would check to see if you have it installed by running "pacman -Q | grep iwlwifi-4965-ucode". If any results are returned, then you have it installed. Next try "iwlist wlan0 scan". This will scan for wireless networks...you should see the one that you are trying to connect to. It looks like you are trying to connect to a WEP enabled network. Try disabling the wep encryption or using a program to automate this (like wlassistant).

apertotes · 2008-07-28 07:04:42

monstermudder78 wrote:

Can you post the portion of your /etc/rc.conf that deal with networking and the DAEMONS= section?
Edit: What type of security are you using and is it supported by the driver for your wireless card? Might try and connect with no security first.

yes, i will try to do that when i get home. but i can tell you that it is nothing special. only changes i did to default were to set a hostname ("arch" in my case), and set "eth0=dhcp"

i am using a simple WEP security. i am completely sure it is supported by my wireless card cause it works out of the box on ubuntu, linux mint, PClinusOS and Zenwalk.

gils0040 wrote:

That network card requires intel's microcode to work properly. First I would check to see if you have it installed by running "pacman -Q | grep iwlwifi-4965-ucode". If any results are returned, then you have it installed. Next try "iwlist wlan0 scan". This will scan for wireless networks...you should see the one that you are trying to connect to. It looks like you are trying to connect to a WEP enabled network. Try disabling the wep encryption or using a program to automate this (like wlassistant).

i can tell you that iwlwifi-4965-ucode is installed. i installed it while installing the system, but to be sure i installed it again on friday. when i do a "iwlist wlan0 scan" i get a long list of networks, including mine.

its true i am using WEP, but i write the key when connecting to the network with a "iwconfig wlan0 essid apertotes key xxxxxx", and it connects succesfully, but it seems that i cant get dhcp to work properly.

i would love to use a program like wlassistant or networkmanager, but i do not know how to install them without internet.

megagram · 2008-07-30 06:55:50

Do you know what IP subnet your local network uses? Check a device that has successfully received a DHCP address from your router. It will likely be something like 192.168.1.0 255.255.255.0 or 10.0.0.0 255.255.255.0.

Now, choose an address that is likely unused on your network. Let's say .234 to be random. So 192.168.1.234 for example.

Now find the device name for your wireless card which I think you said is wlan0.

Enter this code:

sudo ifconfig wlan0 192.168.1.234 netmask 255.255.255.0

Now try pinging your router which should likely have an address ending in .1:

ping 192.168.1.1

If this works then we know the problem lies with DHCP. If it doesn't then you have some more serious issues.

apertotes · 2008-07-30 08:49:43

hi, sorry for not updating on some days. i've had some busy times, working full time and studying the rest, and i havent had time to try any more with arch. i hope i find a few hours to try all those things.

fist i'll post the network part of my rc.conf, and then i'll try to force an ip on my wlan0 to see if i can ping the router.

thanks a lot for your help.

apertotes · 2008-07-30 20:10:17

this is /etc/rc.conf

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="arch"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond)

i also tried this

# Wireless: See network profiles below
#
wlan0="dhcp"
eth0="dhcp"
INTERFACES=(wlan0)

and it didnt work either.

this is /etc/hosts

#
# /etc/hosts: static lookup table for host names
#
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain arch
# End of file

tonight i will try to force a ip on my wlan0 to see if it works

apertotes · 2008-07-31 14:45:44

ok, this is what "iwconfig" shows me after connecting to my network via "iwconfig wlan0 essid apertotes key xxxxxx" ("ifconfig wlan0 up" and "modprobe iwl4965" and "dhcpcd wlan0" done before)

wlan0 IEEE 802.11g ESSID: "apertotes"
Mode: Managed Frequency: 2432 Ghz Access Point: 00:17:9A:F7:89:C3
Bit Rate= 54 Mb/s Tx-Power= 27 dBm
Retry min limit: 7 RTS thr: off Fragment thr= 2352 B
Encryption key: xxxxxx
Link Quality= 80/100 Signal level= -54 dBm Noise level= -127 dBm
Rx invalid nwid: 0 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries: 0 Invalid misc: 0 Missed beacon: 0

then, i do "ping -c 3 192.168.0.1" and the outcome is

connect: Network is unreachable

so i rebooted, and instead of "dhcpcd wlan0" i tried this "ifconfig wlan0 192.168.0.221 netmask 255.255.255.0", but the outcome of "iwconfig" was exactly the same.
then i tried a "ping -c 3 192.168.0.1" and then it happenned something different to the other times

PING 192.168.0.1 (192.168.0.1) 56 (84) bytes of data
From 192.168.0.221 icmp_seq= 1 Destination Host Unreachable
From 192.168.0.221 icmp_seq= 2 Destination Host Unreachable
From 192.168.0.221 icmp_seq= 3 Destination Host Unreachable
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 1999 ms, pipe 3

as comparison i have just made the same from my mint partition,

PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1.78 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=1.47 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=1.29 ms
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 1.294/1.519/1.786/0.203 ms

and the "iwconfig" of my mint system

wlan0 IEEE 802.11g ESSID:"apertotes" Nickname:""
Mode:Managed Frequency:2.432 GHz Access Point: 00:17:9A:F7:89:C3
Bit Rate=54 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Power Management:off
Link Quality=75/100 Signal level=-65 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

exactly the same

i am out of ideas. i need help.

Last edited by apertotes (2008-07-31 17:06:07)

monstermudder78 · 2008-07-31 20:19:30

Ok try this:

1. Reboot

2. Edit /etc/rc.conf to look like this:

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="arch"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="dhcp"
wlan0="dhcp"
wlan_wlan0="wlan0 essid <ESSID>"
INTERFACES=(eth0 wlan0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

---> My network does not have a password, you will need to add you key to the end of the 'wlan_wlan0=' line
---> Change any address settings to reflect the settings on your network
3. In DAEMONS the only thing I have different is !netfs
4. Reboot again, try to ping router

Last edited by monstermudder78 (2008-07-31 20:34:49)

sputter · 2008-07-31 21:06:25

apertotes wrote:

so i rebooted, and instead of "dhcpcd wlan0" i tried this "ifconfig wlan0 192.168.0.221 netmask 255.255.255.0", but the outcome of "iwconfig" was exactly the same.
i am out of ideas. i need help.

Alright I have yet to play with wireless, although this has prompted me to go pay for a $20 card to play with now.
But as a thought just to try and get your juices working, what happens if you enable the gateway in your rc.conf?
with wired connections at times you need to specify a broadcast address, what would happen if you ran
"ifconfig wlan0 192.168.0.221 netmask 255.255.255.0 broadcast 192.168.0.255"
Is your wireless module being loaded by the MODULES=() line in your rc.conf?
monstermudder78 seems to have very good suggestions as well, like I said I can't even be called a wireless neophyte, but I figure just spitballing might help a bit.

Last edited by sputter (2008-07-31 21:07:19)

megagram · 2008-08-01 05:37:28

After doing the manual addressing using ifconfig or the manual configuration in rc.conf, can you show us the output of "route"? Just type "route" and hit enter.

The broadcast flag is likely unneeded as a 255.255.255.0 netmask implies a 192.168.0.255 broadcast address. However, it's definitely worth a shot! I just wonder if, for some really really strange reason your router isn't using a 255.255.255.0 netmask. Can you try giving yourself a lower IP address? Try 192.168.0.2 this will guarantee that you are in the same subnet as your router.

Try this!

apertotes · 2008-08-06 18:48:22

EDIT AFTER LAST TRY!!!!!

first of all, i have to say that even though the module is listed on rc.conf, everytime i start the computer i need to do a modprove iwl4965 for the network card to start working, then i have to do "ifconfig wlan0 up" and then is allright.

ok, tonight is the night!!!! lets get going

sputter wrote:

But as a thought just to try and get your juices working, what happens if you enable the gateway in your rc.conf?

how do i do that? right now my rc.conf looks like this

gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

sputter wrote:

with wired connections at times you need to specify a broadcast address, what would happen if you ran
"ifconfig wlan0 192.168.0.221 netmask 255.255.255.0 broadcast 192.168.0.255"

i'll try on a few minutes,

EDIT: nothing special, same result as before

sputter wrote:

Is your wireless module being loaded by the MODULES=() line in your rc.conf?

yes it is, iwl4965 is listed there

MODULES=(tg3 iwl4965 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)

megagram wrote:

After doing the manual addressing using ifconfig or the manual configuration in rc.conf, can you show us the output of "route"? Just type "route" and hit enter.
The broadcast flag is likely unneeded as a 255.255.255.0 netmask implies a 192.168.0.255 broadcast address. However, it's definitely worth a shot! I just wonder if, for some really really strange reason your router isn't using a 255.255.255.0 netmask. Can you try giving yourself a lower IP address? Try 192.168.0.2 this will guarantee that you are in the same subnet as your router.
Try this!

according to my wife's computer and my mint install, our netmask is really 255.255.255.0

i will try those suggestions tonight and post the outcome here, but to begin, this is "route" on my mint install

Tabla de rutas IP del núcleo
Destino Pasarela Genmask Indic Métric Ref Uso Interfaz
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 wlan0
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0

be right back

this is the outcome on arch before doing dhcpcd

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

and this is after doing "dhcpcd wlan0" and getting again the error i posted on my last message

Kernel IP Routing Table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 * 255.255.0.0 U 0 0 0 wlan0

this time i was unable to get a working Access Point although i could connect to my network

Last edited by apertotes (2008-08-06 19:10:24)

apertotes · 2008-08-25 11:58:28

hi, i still have the problem. i am unable to get a working connection. any other ideas?

rooloo · 2008-08-25 12:06:31

yes, you are not using your rc.conf correctly. wireless connections do not get listed the same as wired connections. I do not have wireless so I can not help you, but I do know your using it wrong. why are you using ifconfig, doesn't wireless interfacs get listed under iwconfig? I think you have to use the a network profile, then list that profile in rc.conf IE... NETWORKS=(wireless_wlna0), where wireless_wlan0 is a profile listed in /etc/network.d/

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="dhcp"
wlan0="dhcp"
wlan_wlan0="wlan0 essid <ESSID>"
INTERFACES=(eth0 wlan0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

Last edited by rooloo (2008-08-25 12:13:06)

IMG · 2008-08-25 12:41:06

well , i want to hope that what i am thinking is not happening , but once your network is up, could you check the "dmesg" output?(just type dmesg in command line)

does it have any lines like:

wlan0: beacon TSF higher than local TSF - IBSS merge with BSSID 26:00:9d:76:70:bb
wlan0: Configured IBSS beacon template
phy2: Adding new IBSS station 00:16:b6:a1:0e:6e (dev=wlan0)
wlan0: Configured IBSS beacon template
phy2: Adding new IBSS station 00:16:b6:a1:0e:6e (dev=wlan0)
wlan0: Configured IBSS beacon template

if you see any output like that you could check this http://bugs.archlinux.org/task/11273?pr … &pagenum=4
and see if this applies to you.

Best of luck
IMG

finferflu · 2008-08-25 12:52:26

I had some problems with iwl4965, quite similar to yours, I was connected and all, but I couldn't ping anything. This is probably not the best solution, but I chose to follow the ndiswrapper route (and it works perfectly). You could do the same just to make sure it's a driver problem, and not a configuration problem.

apertotes · 2008-08-25 14:40:58

finferflu wrote:

I had some problems with iwl4965, quite similar to yours, I was connected and all, but I couldn't ping anything. This is probably not the best solution, but I chose to follow the ndiswrapper route (and it works perfectly). You could do the same just to make sure it's a driver problem, and not a configuration problem.

mmm... i am a linux noob, so i may say something stupid, but i thought that to go the ndiswrapper route i need to have windows installed, is that right? if so, then i will not go that route.

OneEyedPimp · 2008-08-25 16:42:08

No, you just need to find the windows driver online somewhere, use wine to extract it, and then install it with ndiswrapper. http://wiki.archlinux.org/index.php/Ndi … supplicant should give you a little bit of an idea...

Arch Linux

#1 2008-07-27 02:10:39

need help with network

#2 2008-07-27 02:45:36

Re: need help with network

#3 2008-07-27 02:58:15

Re: need help with network

#4 2008-07-27 03:13:16

Re: need help with network

#5 2008-07-27 07:02:40

Re: need help with network

#6 2008-07-27 13:08:17

Re: need help with network

#7 2008-07-27 18:21:45

Re: need help with network

#8 2008-07-27 21:38:45

Re: need help with network

#9 2008-07-28 07:04:42

Re: need help with network

#10 2008-07-30 06:55:50

Re: need help with network

#11 2008-07-30 08:49:43

Re: need help with network

#12 2008-07-30 20:10:17

Re: need help with network

#13 2008-07-31 14:45:44

Re: need help with network

#14 2008-07-31 20:19:30

Re: need help with network

#15 2008-07-31 21:06:25

Re: need help with network

#16 2008-08-01 05:37:28

Re: need help with network

#17 2008-08-06 18:48:22

Re: need help with network

#18 2008-08-25 11:58:28

Re: need help with network

#19 2008-08-25 12:06:31

Re: need help with network

#20 2008-08-25 12:41:06

Re: need help with network

#21 2008-08-25 12:52:26

Re: need help with network

#22 2008-08-25 14:40:58

Re: need help with network

#23 2008-08-25 16:42:08

Re: need help with network

Board footer