You are not logged in.

#1 2013-02-05 21:04:02

TheRatze94
Member
Registered: 2012-07-01
Posts: 33

[Solved] Can't get an IP when too far away from router

Hello everyone!

I just installed Arch Linux on my Netbook and configured my internet connection. First everything ran very well but then I tried to establish an internet connection from my room (2 floors above the router). I just wasn't able to get an IP!

I searched for a solution and found out that maybe dhcpcd causes the problem so I decided to install NetworkManager which uses dhclient ( also it's easier to use than running 'wifi-menu' everytime I want to connect to a new network big_smile ).
But there I get the exact same problem.

I used elementary os on this Netbook before and everything worked fine. I got an IP adress everytime and it didn't even take long to get it as it is now. Elementary OS uses NetworkManger too. Does anyone have an idea what I could've done wrong?

I just find an dhclient.conf.example in /etc/ and no dhclient.conf

The content of my /etc/NetworkManger/NetworkManager.conf is:

[main]
plugins=keyfile

Thanks in advance!
TheRatze94

Last edited by TheRatze94 (2013-02-12 12:02:14)

Offline

#2 2013-02-05 22:04:20

olive
Member
From: Belgium
Registered: 2008-06-22
Posts: 1,143

Re: [Solved] Can't get an IP when too far away from router

If the problem appears only when you are far from the router, I would say this is an hardware problem. I know there exists some antenna for wireless but I couldn't say more.

Offline

#3 2013-02-05 22:36:19

the sad clown
Member
From: 192.168.0.X
Registered: 2011-03-20
Posts: 833

Re: [Solved] Can't get an IP when too far away from router

My suggestion is to use a live cd for Elementary OS and look at the dhclient.conf, then translate it to your system so that you are using the same settings.  Alternately, have a look at the dhclient.conf man page and test out various configuration options and see what works for you:

http://linux.die.net/man/5/dhclient.conf


I laugh, yet the joke is on me

Offline

#4 2013-02-05 22:57:18

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [Solved] Can't get an IP when too far away from router

Yes, as the sad clown has already indicated, it would help if we/you knew what the differences were between the settings of the two operating systems you are attempting to connect with.  If no differences are present (that is, elementary os uses defaults), you may be looking at differences in the module being used for your wireless card.  What is your wireless chipset, as I used to have a Realtek, and besides it rather sucking on Linux in general, it did seem to work slightly better on various live media than it did with Arch and the in-tree kernel module.

Offline

#5 2013-02-06 01:44:39

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 5,670

Re: [Solved] Can't get an IP when too far away from router

It would help if you could either change your subject line or re-explain your problem as the issue of distance doesn't seem to come up in the explanation you give and I'm not at all clear if you have 2 problems, 1 problem or some unknown number of problems.


How To Ask Questions The Smart Way | Help Vampires

Arch Linux | x86_64 | GPT | EFI boot | grub2 | systemd | LVM2 on LUKS
Lenovo x121e | Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz GenuineIntel | Intel Centrino Wireless-N 1000 | US keyboard with Euro | 320G 7200 RPM Seagate HDD

Offline

#6 2013-02-06 14:43:00

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,015

Re: [Solved] Can't get an IP when too far away from router

Use something like wicd, and if the router you are connecting to is <50% link you aren't going to get it.  You need another router or a booster/extender.


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#7 2013-02-06 15:01:32

vacant
Member
From: downstairs
Registered: 2004-11-05
Posts: 801

Re: [Solved] Can't get an IP when too far away from router

Hang on, could Arch be using a built-in driver and Elementary a proprietory one?

Offline

#8 2013-02-06 19:43:46

TheRatze94
Member
Registered: 2012-07-01
Posts: 33

Re: [Solved] Can't get an IP when too far away from router

Thanks for the replies! smile

@nomorewindows: I tried wicd before and had the same problem. Also elementary os had no problem with a 50% signal.

@all :
Arch and elementary os load exactly the same kernel module:

 iwlwifi 

The dhclient.conf (which doesn't exist on my system) looks like that:

# Configuration file for /sbin/dhclient, which is included in Debian's
#	dhcp3-client package.
#
# This is a sample configuration file for dhclient. See dhclient.conf's
#	man page for more information about the syntax of this file
#	and a more comprehensive list of the parameters understood by
#	dhclient.
#
# Normally, if the DHCP server provides reasonable information and does
#	not leave anything out (like the domain name, for example), then
#	few changes must be made to this file, if any.
#

option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;

send host-name "<hostname>";
#send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
#send dhcp-lease-time 3600;
#supersede domain-name "fugue.com home.vix.com";
#prepend domain-name-servers 127.0.0.1;
request subnet-mask, broadcast-address, time-offset, routers,
	domain-name, domain-name-servers, domain-search, host-name,
	netbios-name-servers, netbios-scope, interface-mtu,
	rfc3442-classless-static-routes, ntp-servers,
	dhcp6.domain-search, dhcp6.fqdn,
	dhcp6.name-servers, dhcp6.sntp-servers;
#require subnet-mask, domain-name-servers;
#timeout 60;
#retry 60;
#reboot 10;
#select-timeout 5;
#initial-interval 2;
#script "/etc/dhcp3/dhclient-script";
#media "-link0 -link1 -link2", "link0 link1";
#reject 192.33.137.209;

#alias {
#  interface "eth0";
#  fixed-address 192.5.5.213;
#  option subnet-mask 255.255.255.255;
#}

#lease {
#  interface "eth0";
#  fixed-address 192.33.137.200;
#  medium "link0 link1";
#  option host-name "andare.swiftmedia.com";
#  option subnet-mask 255.255.255.0;
#  option broadcast-address 192.33.137.255;
#  option routers 192.33.137.250;
#  option domain-name-servers 127.0.0.1;
#  renew 2 2000/1/12 00:00:01;
#  rebind 2 2000/1/12 00:00:01;
#  expire 2 2000/1/12 00:00:01;
#}

Also the NetworkManager.conf is different to my system (my NetworkManager.conf is in the first post):

[main]
plugins=ifupdown,keyfile
dns=dnsmasq

[ifupdown]
managed=false

There are more plugins loaded. Could that be the reason?

Last edited by TheRatze94 (2013-02-06 19:47:17)

Offline

#9 2013-02-06 23:36:01

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,015

Re: [Solved] Can't get an IP when too far away from router

What kernel and what firmware is it loading?  Even though it uses iwlwifi things may not be quite the same.


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#10 2013-02-10 13:13:12

TheRatze94
Member
Registered: 2012-07-01
Posts: 33

Re: [Solved] Can't get an IP when too far away from router

Sorry for the late reply...

The kernel version is:

 uname -a
Linux elementary 3.2.0-32-generic-pae #51-Ubuntu SMP Wed Sep 26 21:54:23 UTC 2012 i686 i686 i386 GNU/Linux

The firmware version is:

sudo dmidecode -s bios-version
V3.09(DDR3)

Offline

#11 2013-02-10 15:53:01

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 13,424

Re: [Solved] Can't get an IP when too far away from router

Any other differences?  Do you have Bluetooth?  Is it enabled in Arch bit not elementary?

Also, you say you used elementary "Before" without problem.  Is that 5 minutes before, or 5 days before?  Could there be a new router, wireless phone, large metal appliance, etc.. on the intervening floor?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence.  You must not work with the public much. -- Trilby
----
How to Ask Questions the Smart Way

Offline

#12 2013-02-10 19:08:45

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,015

Re: [Solved] Can't get an IP when too far away from router

TheRatze94 wrote:

Sorry for the late reply...

The kernel version is:

 uname -a
Linux elementary 3.2.0-32-generic-pae #51-Ubuntu SMP Wed Sep 26 21:54:23 UTC 2012 i686 i686 i386 GNU/Linux

The firmware version is:

sudo dmidecode -s bios-version
V3.09(DDR3)

What is the Arch kernel version?
What is the firmware for the wireless device (dmesg)?


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#13 2013-02-10 20:25:55

debijan
Member
Registered: 2010-09-14
Posts: 36

Re: [Solved] Can't get an IP when too far away from router

have you tried to increase transmit power?

txpower
    For cards supporting multiple transmit powers, sets the transmit power in dBm. If W is the power in Watt, the power in dBm is P = 30 + 10.log(W). If the value is postfixed by mW, it will be automatically converted to dBm.
    In addition, on and off enable and disable the radio, and auto and fixed enable and disable power control (if those features are available).
    Examples :
    iwconfig eth0 txpower 15
    iwconfig eth0 txpower 30mW
    iwconfig eth0 txpower auto
    iwconfig eth0 txpower off

are you able to transfer data with manual set IP's? Have you captured the traffic and see that the DHCP server sends DHCP offers?

edit:/ the guy below is right. but use -i flag in grep for case insensitiv hits ;-)

Last edited by debijan (2013-02-10 21:20:49)

Offline

#14 2013-02-10 21:00:23

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,277

Re: [Solved] Can't get an IP when too far away from router

Tweaking txpower single-sidedly does not usually do any good, but leads to connection quality problems.
Maybe there are other wifis disturbing now on the channel (like ewaller asks), which were not around when you used elementary?
Maybe its related to IPv6 in your router. Try setting networkmanager to "ignore IPv6".

What does "journalctl -b |grep dhcp" show after it fails to connect?

Offline

#15 2013-02-11 11:20:08

TheRatze94
Member
Registered: 2012-07-01
Posts: 33

Re: [Solved] Can't get an IP when too far away from router

@ewaller My Netbook hasn't got Bluetooth. With before i mean that it worked the last 1,5 years. I didn't notice a new router or any other changes.

@nomorewindows The Arch Kernel Version is:

uname -a
Linux ratze-netbook 3.7.5-1-ARCH #1 SMP PREEMPT Mon Jan 28 10:38:12 CET 2013 i686 GNU/Linux

The firmware for the wireless device on Arch is:

dmesg |grep 'firm'
[    8.752703] iwlwifi 0000:02:00.0: loaded firmware version 39.31.5.1 build 35138

@Strike0 I already disabled IPv6. The output of "journalctl -b|grep -i dhcp":

sudo journalctl -b |grep -i dhcp
Feb 11 11:38:06 ratze-netbook NetworkManager[263]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb 11 11:38:07 ratze-netbook dhclient[281]: Internet Systems Consortium DHCP Client 4.2.4-P2
Feb 11 11:38:07 ratze-netbook dhclient[281]: For info, please visit https://www.isc.org/software/dhcp/
Feb 11 11:38:07 ratze-netbook NetworkManager[263]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
Feb 11 11:38:07 ratze-netbook dhclient[281]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 11:38:14 ratze-netbook dhclient[281]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 11:38:23 ratze-netbook dhclient[281]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 4
Feb 11 11:38:27 ratze-netbook dhclient[281]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 7
Feb 11 11:38:34 ratze-netbook dhclient[281]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 13
Feb 11 11:38:47 ratze-netbook dhclient[281]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 16
Feb 11 11:38:52 ratze-netbook NetworkManager[263]: <warn> (wlp2s0): DHCPv4 request timed out.
Feb 11 11:38:52 ratze-netbook NetworkManager[263]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 281
Feb 11 11:38:55 ratze-netbook NetworkManager[263]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb 11 11:38:55 ratze-netbook dhclient[338]: Internet Systems Consortium DHCP Client 4.2.4-P2
Feb 11 11:38:55 ratze-netbook dhclient[338]: For info, please visit https://www.isc.org/software/dhcp/
Feb 11 11:38:55 ratze-netbook NetworkManager[263]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
Feb 11 11:38:55 ratze-netbook dhclient[338]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 11:39:01 ratze-netbook dhclient[338]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 11:39:11 ratze-netbook dhclient[338]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 4
Feb 11 11:39:15 ratze-netbook dhclient[338]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 5
Feb 11 11:39:15 ratze-netbook dhclient[338]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 11:39:15 ratze-netbook dhclient[338]: DHCPOFFER from 192.168.2.1
Feb 11 11:39:15 ratze-netbook dhclient[338]: DHCPACK from 192.168.2.1
Feb 11 11:39:15 ratze-netbook NetworkManager[263]: <info> (wlp2s0): DHCPv4 state changed preinit -> bound
Feb 11 11:54:00 ratze-netbook NetworkManager[263]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 338
Feb 11 12:00:03 ratze-netbook NetworkManager[263]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb 11 12:00:03 ratze-netbook dhclient[597]: Internet Systems Consortium DHCP Client 4.2.4-P2
Feb 11 12:00:03 ratze-netbook dhclient[597]: For info, please visit https://www.isc.org/software/dhcp/
Feb 11 12:00:03 ratze-netbook NetworkManager[263]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
Feb 11 12:00:03 ratze-netbook dhclient[597]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:00:03 ratze-netbook dhclient[597]: DHCPNAK from 192.168.2.1
Feb 11 12:00:03 ratze-netbook NetworkManager[263]: <info> (wlp2s0): DHCPv4 state changed preinit -> expire
Feb 11 12:00:03 ratze-netbook dhclient[597]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 8
Feb 11 12:00:03 ratze-netbook NetworkManager[263]: <info> (wlp2s0): DHCPv4 state changed expire -> preinit
Feb 11 12:00:05 ratze-netbook dhclient[597]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:00:05 ratze-netbook dhclient[597]: DHCPOFFER from 192.168.2.1
Feb 11 12:00:06 ratze-netbook dhclient[597]: DHCPACK from 192.168.2.1
Feb 11 12:00:06 ratze-netbook NetworkManager[263]: <info> (wlp2s0): DHCPv4 state changed preinit -> bound
Feb 11 12:05:32 ratze-netbook NetworkManager[263]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 597
Feb 11 12:05:37 ratze-netbook NetworkManager[263]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb 11 12:05:37 ratze-netbook dhclient[639]: Internet Systems Consortium DHCP Client 4.2.4-P2
Feb 11 12:05:37 ratze-netbook dhclient[639]: For info, please visit https://www.isc.org/software/dhcp/
Feb 11 12:05:37 ratze-netbook NetworkManager[263]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
Feb 11 12:05:37 ratze-netbook dhclient[639]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:05:44 ratze-netbook dhclient[639]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:05:54 ratze-netbook dhclient[639]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 8
Feb 11 12:06:02 ratze-netbook dhclient[639]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 9
Feb 11 12:06:11 ratze-netbook dhclient[639]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 14
Feb 11 12:06:22 ratze-netbook NetworkManager[263]: <warn> (wlp2s0): DHCPv4 request timed out.
Feb 11 12:06:22 ratze-netbook NetworkManager[263]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 639
Feb 11 12:06:25 ratze-netbook NetworkManager[263]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb 11 12:06:25 ratze-netbook dhclient[645]: Internet Systems Consortium DHCP Client 4.2.4-P2
Feb 11 12:06:25 ratze-netbook dhclient[645]: For info, please visit https://www.isc.org/software/dhcp/
Feb 11 12:06:25 ratze-netbook NetworkManager[263]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
Feb 11 12:06:25 ratze-netbook dhclient[645]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:06:32 ratze-netbook dhclient[645]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:06:45 ratze-netbook dhclient[645]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 6
Feb 11 12:06:51 ratze-netbook dhclient[645]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 12
Feb 11 12:07:03 ratze-netbook dhclient[645]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 15
Feb 11 12:07:11 ratze-netbook NetworkManager[263]: <warn> (wlp2s0): DHCPv4 request timed out.
Feb 11 12:07:11 ratze-netbook NetworkManager[263]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 645
Feb 11 12:12:39 ratze-netbook NetworkManager[263]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb 11 12:12:39 ratze-netbook dhclient[663]: Internet Systems Consortium DHCP Client 4.2.4-P2
Feb 11 12:12:39 ratze-netbook dhclient[663]: For info, please visit https://www.isc.org/software/dhcp/
Feb 11 12:12:39 ratze-netbook NetworkManager[263]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
Feb 11 12:12:39 ratze-netbook dhclient[663]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:12:44 ratze-netbook dhclient[663]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:12:57 ratze-netbook dhclient[663]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 6
Feb 11 12:13:03 ratze-netbook dhclient[663]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 6
Feb 11 12:13:09 ratze-netbook dhclient[663]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 16
Feb 11 12:13:25 ratze-netbook NetworkManager[263]: <warn> (wlp2s0): DHCPv4 request timed out.
Feb 11 12:13:25 ratze-netbook NetworkManager[263]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 663
Feb 11 12:13:28 ratze-netbook NetworkManager[263]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb 11 12:13:28 ratze-netbook dhclient[669]: Internet Systems Consortium DHCP Client 4.2.4-P2
Feb 11 12:13:28 ratze-netbook dhclient[669]: For info, please visit https://www.isc.org/software/dhcp/
Feb 11 12:13:28 ratze-netbook NetworkManager[263]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
Feb 11 12:13:28 ratze-netbook dhclient[669]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:13:32 ratze-netbook dhclient[669]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:13:37 ratze-netbook dhclient[669]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:13:49 ratze-netbook dhclient[669]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 6
Feb 11 12:13:55 ratze-netbook dhclient[669]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 11
Feb 11 12:14:06 ratze-netbook dhclient[669]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 19
Feb 11 12:14:14 ratze-netbook NetworkManager[263]: <warn> (wlp2s0): DHCPv4 request timed out.
Feb 11 12:14:14 ratze-netbook NetworkManager[263]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 669
Feb 11 12:14:17 ratze-netbook NetworkManager[263]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb 11 12:14:17 ratze-netbook dhclient[674]: Internet Systems Consortium DHCP Client 4.2.4-P2
Feb 11 12:14:17 ratze-netbook dhclient[674]: For info, please visit https://www.isc.org/software/dhcp/
Feb 11 12:14:17 ratze-netbook NetworkManager[263]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
Feb 11 12:14:17 ratze-netbook dhclient[674]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:14:21 ratze-netbook dhclient[674]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:14:31 ratze-netbook dhclient[674]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 3
Feb 11 12:14:34 ratze-netbook dhclient[674]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 3
Feb 11 12:14:37 ratze-netbook dhclient[674]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 3
Feb 11 12:14:40 ratze-netbook dhclient[674]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 3
Feb 11 12:14:43 ratze-netbook dhclient[674]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 7
Feb 11 12:14:43 ratze-netbook dhclient[674]: DHCPREQUEST on wlp2s0 to 255.255.255.255 port 67
Feb 11 12:14:43 ratze-netbook dhclient[674]: DHCPOFFER from 192.168.2.1
Feb 11 12:14:43 ratze-netbook dhclient[674]: DHCPACK from 192.168.2.1
Feb 11 12:14:43 ratze-netbook NetworkManager[263]: <info> (wlp2s0): DHCPv4 state changed preinit -> bound
Feb 11 12:15:32 ratze-netbook NetworkManager[263]: <info> (wlp2s0): canceled DHCP transaction, DHCP client pid 674

I hope that could help smile

Offline

#16 2013-02-11 16:06:50

TheRatze94
Member
Registered: 2012-07-01
Posts: 33

Re: [Solved] Can't get an IP when too far away from router

I looked at the elementary os jupiter image and found out that it loads iwlagn.
I tried to load the module in Arch Linux but it isn't available.

Offline

#17 2013-02-11 19:18:07

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,277

Re: [Solved] Can't get an IP when too far away from router

iwlwifi is the successor of iwlagn from kernel 3.2 onwards.
As I read that log it looks like confirming the signal problem. If you look at the last four lines, an IP gets offered from the router, acknowledged, bound, but then it breaks off. Same at 12:05
Try what happens, if you disable wifi-n and bluetooth

modprobe iwlwifi 11n_disable=1 bt_coex_active=0

Offline

#18 2013-02-12 12:01:46

TheRatze94
Member
Registered: 2012-07-01
Posts: 33

Re: [Solved] Can't get an IP when too far away from router

Thank you Strike0!
Now i get an ip instantly smile

For those who have the same problem:

I created a file in /etc/modprobe.d/ :

$ sudo nano wifi.conf
options iwlwifi 11n_disable=1 bt_coex_active=0

Thanks again to everyone! smile

Offline

#19 2013-02-13 00:06:06

debijan
Member
Registered: 2010-09-14
Posts: 36

Re: [Solved] Can't get an IP when too far away from router

wow... congrats :-)
can somebody explain why 802.11n is the problem is here?
because the notebook has no bluetooth :-/

Last edited by debijan (2013-02-13 00:06:37)

Offline

#20 2013-02-13 00:43:06

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 13,424

Re: [Solved] Can't get an IP when too far away from router

If I am not mistaken, the system had been trying to connect on N, presumably in the 5 GHz band.  Disabling N forced the use of G down at 2.5 GHz.  There is less attenuation at the 'lower' frequency.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence.  You must not work with the public much. -- Trilby
----
How to Ask Questions the Smart Way

Offline

#21 2013-02-13 18:14:01

Leonid.I
Member
From: Aethyr
Registered: 2009-03-22
Posts: 949

Re: [Solved] Can't get an IP when too far away from router

Just to clarify, 11n does not imply 5GHz. You can happily use 2.5GHz band with both 11g and 11n.

Having said that, you never mentioned you card, or signal strength in dBm.

For instance, for intel 5101agn iwlwifi sucks big time (I can vaguely remember iwlagn to work even in 11n mode albeit the card temp was ~80C). In linux using 11n mode I am only able to get ~200KiB/s download speed, while in 11g mode -- 2MiB/s. The same card in win7 achieves 5MiB/s speeds over 11n.

Finally, with the above card, signal strength ~ -75 dBm is enough for a proper operation.

Last edited by Leonid.I (2013-02-13 18:14:31)


Arch Linux is more than just GNU/Linux -- it's an adventure

Offline

Board footer

Powered by FluxBB