You are not logged in.

#1 2013-03-07 14:24:44

broi
Member
From: Bosnia & Herzegovina
Registered: 2011-12-10
Posts: 127

[SOLVED]Problem connecting to wired network (dynamic IP) after I moved

Hi,
few days ago I changed the address where I live and my ISP moved Internet antenna and they did other formal things, but since then I can't connect to internet from Linux system. (I have no problems in Windows XP)
I tried booting Lubuntu 11.10 from Live CD just to check if the problem is in my Arch setup, but it did not work, even few days ago (before I moved) I could use internet on any distro I have booted, including Lubuntu I mentoined above and my current Arch.

ping google.com returns me "Unknown host"
ping 8.8.8.8 returns me "connect: Network is unreachable"

My internet worked by enabling dhcpcd@eth0.service but it does not start anymore - > systemctl status dhcpcd@eth0.service:

[ibrahim@broislinux ~]$ sudo systemctl status dhcpcd@eth0.service
[sudo] password for ibrahim: 
dhcpcd@eth0.service - dhcpcd on eth0
	  Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; enabled)
	  Active: failed (Result: exit-code) since Thu 2013-03-07 07:02:01 CET; 3min 34s ago
	 Process: 608 ExecStart=/usr/sbin/dhcpcd -q -w %I (code=exited, status=1/FAILURE)

Mar 07 07:01:31 broislinux dhcpcd[608]: eth0: sending IPv6 Router Solicitation
Mar 07 07:01:31 broislinux dhcpcd[608]: eth0: broadcasting for a lease
Mar 07 07:01:35 broislinux dhcpcd[608]: eth0: sending IPv6 Router Solicitation
Mar 07 07:01:39 broislinux dhcpcd[608]: eth0: sending IPv6 Router Solicitation
Mar 07 07:01:43 broislinux dhcpcd[608]: eth0: sending IPv6 Router Solicitation
Mar 07 07:01:43 broislinux dhcpcd[608]: eth0: no IPv6 Routers available
Mar 07 07:02:01 broislinux dhcpcd[608]: timed out
Mar 07 07:02:01 broislinux systemd[1]: dhcpcd@eth0.service: control process exited, code=exited status=1
Mar 07 07:02:01 broislinux systemd[1]: Failed to start dhcpcd on eth0.
Mar 07 07:02:01 broislinux systemd[1]: Unit dhcpcd@eth0.service entered failed state

journalctl -xn:

[ibrahim@broislinux ~]$ sudo journalctl -xn
-- Logs begin at Sat 2012-12-08 20:52:46 CET, end at Thu 2013-03-07 07:07:42 CET. --
Mar 07 07:07:26 broislinux dhcpcd[655]: control command: dhcpcd[707]: sending commands to master dhcpcd process
Mar 07 07:07:26 broislinux dhcpcd[655]: handle_args: no interface
Mar 07 07:07:26 broislinux dhcpcd[707]: sending commands to master dhcpcd process
Mar 07 07:07:26 broislinux dhcpcd[655]: control command: /usr/sbin/dhcpcd -q -w eth0
Mar 07 07:07:26 broislinux systemd[1]: PID file /run/dhcpcd-eth0.pid not readable (yet?) after start.
Mar 07 07:07:26 broislinux systemd[1]: Failed to start dhcpcd on eth0.
-- Subject: Unit dhcpcd@eth0.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- 
-- Unit dhcpcd@eth0.service has failed.
-- 
-- The result is failed.
Mar 07 07:07:26 broislinux systemd[1]: Unit dhcpcd@eth0.service entered failed state
Mar 07 07:07:26 broislinux sudo[704]: pam_unix(sudo:session): session closed for user root
Mar 07 07:07:42 broislinux sudo[712]: ibrahim : TTY=pts/0 ; PWD=/home/ibrahim ; USER=root ; COMMAND=/usr/bin/journalctl -xn
Mar 07 07:07:42 broislinux sudo[712]: pam_unix(sudo:session): session opened for user root by ibrahim(uid=0)

I contacted my ISP about this problem and they told me that they did not change any of they're device configurations and asked me about how I start internet on Linux system etc. and I told them I use DHCPCD, and in last e-mail, they told me to do

dhclient -r; dhclient

which should renew the ip address but this didn't help eighter...
My ISP and I have "argued" about this in 5-6 six e-mails but they don't seem they're able to help me.

Now I don't know if this is coincidence my internet stopped working in meantime or because I moved.. Maybe it has nothing to do with moving..
Do anyone have a clue what could be wrong?
EDIT: I tried connecting my cable to another laptop with Linux Mint 14 installed and I can use my internet with no problems.
EDIT 2: { I tried using NetworkManager service w/ network-manager-applet and when I click to "Wired Connection 1" from the applet:
"Requesting a wired network address for 'Wired Connection 1'"
and it's about 15-20 seconds, the I get error in notificationbox: "The network connection has been disconnected". }

Sorry for my English and thanks:)

Last edited by broi (2013-03-15 10:11:34)

Offline

#2 2013-03-07 15:06:52

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

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

It might be that your interfaces have changed names.  What is the output of ip link   ??


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Offline

#3 2013-03-07 15:12:38

broi
Member
From: Bosnia & Herzegovina
Registered: 2011-12-10
Posts: 127

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

ewaller wrote:

It might be that your interfaces have changed names.  What is the output of ip link   ??

Thanks for rasponse, but it appears that the interface name did not changed...

[ibrahim@broislinux ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT qlen 1000
    link/ether 00:14:85:b9:22:8a brd ff:ff:ff:ff:ff:ff

Offline

#4 2013-03-07 15:17:54

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

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

Okay,  the only weird thing I saw was that your dhcpcd output only talked about IPv6.  I have seen some weirdness happen when routers pretend to support IPv6, but really don't.  Try disabling IPv6 and see if that helps.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Offline

#5 2013-03-07 17:56:18

broi
Member
From: Bosnia & Herzegovina
Registered: 2011-12-10
Posts: 127

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

ewaller wrote:

Okay,  the only weird thing I saw was that your dhcpcd output only talked about IPv6.  I have seen some weirdness happen when routers pretend to support IPv6, but really don't.  Try disabling IPv6 and see if that helps.

I have tried adding ipv6.disable_ipv6=1 to the kernel line plus adding the

# Disable IPv6
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.eth0.disable_ipv6 = 1

to /etc/sysctl.d/ipv6.conf (as explained in link you gave me) and this is the 'systemctl status dhcpcd@eth0.service' now (no success):

[ibrahim@broislinux ~]$ sudo systemctl status dhcpcd@eth0.service
dhcpcd@eth0.service - dhcpcd on eth0
	  Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; enabled)
	  Active: failed (Result: exit-code) since Thu 2013-03-07 10:20:36 CET; 5s ago
	 Process: 588 ExecStart=/usr/sbin/dhcpcd -q -w %I (code=exited, status=1/FAILURE)

Mar 07 10:20:10 broislinux dhcpcd[588]: eth0: sendmsg: Network is unreachable
Mar 07 10:20:14 broislinux dhcpcd[588]: eth0: sending IPv6 Router Solicitation
Mar 07 10:20:14 broislinux dhcpcd[588]: eth0: sendmsg: Network is unreachable
Mar 07 10:20:18 broislinux dhcpcd[588]: eth0: sending IPv6 Router Solicitation
Mar 07 10:20:18 broislinux dhcpcd[588]: eth0: sendmsg: Network is unreachable
Mar 07 10:20:18 broislinux dhcpcd[588]: eth0: no IPv6 Routers available
Mar 07 10:20:36 broislinux dhcpcd[588]: timed out
Mar 07 10:20:36 broislinux systemd[1]: dhcpcd@eth0.service: control process exited, code=exited status=1
Mar 07 10:20:36 broislinux systemd[1]: Failed to start dhcpcd on eth0.
Mar 07 10:20:36 broislinux systemd[1]: Unit dhcpcd@eth0.service entered failed state

journalctl -xn:

[ibrahim@broislinux ~]$ sudo journalctl -xn
[sudo] password for ibrahim: 
-- Logs begin at Sat 2012-12-08 20:52:46 CET, end at Thu 2013-03-07 10:21:45 CET. --
Mar 07 10:20:42 broislinux systemd[1]: Starting Update UTMP about System Runlevel Changes...
-- Subject: Unit systemd-update-utmp-runlevel.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/7d4958e842da4a758f6c1cdc7b36dcc5
-- 
-- Unit systemd-update-utmp-runlevel.service has begun starting up.
Mar 07 10:20:42 broislinux systemd[1]: Starting Network.
-- Subject: Unit network.target has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/7d4958e842da4a758f6c1cdc7b36dcc5
-- 
-- Unit network.target has begun starting up.
Mar 07 10:20:42 broislinux systemd[1]: Reached target Network.
-- Subject: Unit network.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/39f53479d3a045ac8e11786248231fbf
-- 
-- Unit network.target has finished starting up.
-- 
-- The start-up result is done.
Mar 07 10:20:42 broislinux systemd[1]: Started Update UTMP about System Runlevel Changes.
-- Subject: Unit systemd-update-utmp-runlevel.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/39f53479d3a045ac8e11786248231fbf
-- 
-- Unit systemd-update-utmp-runlevel.service has finished starting up.
-- 
-- The start-up result is done.
Mar 07 10:20:42 broislinux systemd[1]: Startup finished in 3s 539ms 744us (kernel) + 1min 30s 712ms 603us (userspace) = 1min 34s 252ms 347us.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/b07a249cd024414a82dd00cd181378ff
-- 
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- 
-- Kernel start-up required 3539744 microseconds.
-- 
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- 
-- Userspace start-up required 90712603 microseconds.
Mar 07 10:20:48 broislinux sudo[595]: pam_unix(sudo:session): session closed for user root
Mar 07 10:21:31 broislinux sudo[610]: pam_unix(sudo:auth): conversation failed
Mar 07 10:21:31 broislinux sudo[610]: pam_unix(sudo:auth): auth could not identify password for [ibrahim]
Mar 07 10:21:45 broislinux sudo[626]: ibrahim : TTY=pts/0 ; PWD=/home/ibrahim ; USER=root ; COMMAND=/usr/bin/journalctl -xn
:
-- Logs begin at Sat 2012-12-08 20:52:46 CET, end at Thu 2013-03-07 10:21:45 CET. --
Mar 07 10:20:42 broislinux systemd[1]: Starting Update UTMP about System Runlevel Changes...
-- Subject: Unit systemd-update-utmp-runlevel.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/7d4958e842da4a758f6c1cdc7b36dcc5
-- 
-- Unit systemd-update-utmp-runlevel.service has begun starting up.
Mar 07 10:20:42 broislinux systemd[1]: Starting Network.
-- Subject: Unit network.target has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/7d4958e842da4a758f6c1cdc7b36dcc5
-- 
-- Unit network.target has begun starting up.
Mar 07 10:20:42 broislinux systemd[1]: Reached target Network.
-- Subject: Unit network.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/39f53479d3a045ac8e11786248231fbf
-- 
-- Unit network.target has finished starting up.
-- 
-- The start-up result is done.
Mar 07 10:20:42 broislinux systemd[1]: Started Update UTMP about System Runlevel Changes.
-- Subject: Unit systemd-update-utmp-runlevel.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/39f53479d3a045ac8e11786248231fbf
-- 
-- Unit systemd-update-utmp-runlevel.service has finished starting up.
-- 
-- The start-up result is done.
Mar 07 10:20:42 broislinux systemd[1]: Startup finished in 3s 539ms 744us (kernel) + 1min 30s 712ms 603us (userspace) = 1min 34s 252ms 347us.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/b07a249cd024414a82dd00cd181378ff
-- 
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- 
-- Kernel start-up required 3539744 microseconds.
-- 
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- 
-- Userspace start-up required 90712603 microseconds.
Mar 07 10:20:48 broislinux sudo[595]: pam_unix(sudo:session): session closed for user root
Mar 07 10:21:31 broislinux sudo[610]: pam_unix(sudo:auth): conversation failed

then I tried adding ipv6.disable=1 to the kernel line (*again, no success):

[ibrahim@broislinux ~]$ sudo systemctl status dhcpcd@eth0.service
dhcpcd@eth0.service - dhcpcd on eth0
	  Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; enabled)
	  Active: failed (Result: exit-code) since Thu 2013-03-07 10:43:52 CET; 5s ago
	 Process: 595 ExecStart=/usr/sbin/dhcpcd -q -w %I (code=exited, status=1/FAILURE)

Mar 07 10:43:21 broislinux systemd[1]: Starting dhcpcd on eth0...
Mar 07 10:43:21 broislinux dhcpcd[595]: version 5.6.7 starting
Mar 07 10:43:21 broislinux dhcpcd[595]: all: configured as a router, not a host
Mar 07 10:43:21 broislinux dhcpcd[595]: eth0: broadcasting for a lease
Mar 07 10:43:52 broislinux dhcpcd[595]: timed out
Mar 07 10:43:52 broislinux systemd[1]: dhcpcd@eth0.service: control process exited, code=exited status=1
Mar 07 10:43:52 broislinux systemd[1]: Failed to start dhcpcd on eth0.
Mar 07 10:43:52 broislinux systemd[1]: Unit dhcpcd@eth0.service entered failed state

journalctl -nx:

[ibrahim@broislinux ~]$ sudo journalctl -xn
-- Logs begin at Sat 2012-12-08 20:52:46 CET, end at Thu 2013-03-07 10:46:00 CET. --
Mar 07 10:43:52 broislinux dhcpcd[595]: timed out
Mar 07 10:43:52 broislinux systemd[1]: dhcpcd@eth0.service: control process exited, code=exited status=1
Mar 07 10:43:52 broislinux systemd[1]: Failed to start dhcpcd on eth0.
-- Subject: Unit dhcpcd@eth0.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- 
-- Unit dhcpcd@eth0.service has failed.
-- 
-- The result is failed.
Mar 07 10:43:52 broislinux systemd[1]: Unit dhcpcd@eth0.service entered failed state
Mar 07 10:43:52 broislinux sudo[592]: pam_unix(sudo:session): session closed for user root
Mar 07 10:43:57 broislinux sudo[606]: ibrahim : TTY=pts/0 ; PWD=/home/ibrahim ; USER=root ; COMMAND=/usr/bin/systemctl status dhcpcd@eth0.servi
Mar 07 10:43:57 broislinux sudo[606]: pam_unix(sudo:session): session opened for user root by ibrahim(uid=0)
Mar 07 10:43:57 broislinux sudo[606]: pam_unix(sudo:session): session closed for user root
Mar 07 10:46:00 broislinux sudo[626]: ibrahim : TTY=pts/0 ; PWD=/home/ibrahim ; USER=root ; COMMAND=/usr/bin/journalctl -xn
Mar 07 10:46:00 broislinux sudo[626]: pam_unix(sudo:session): session opened for user root by ibrahim(uid=0)

Can this help?

/etc/hosts

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>   <hostname.domain.org>   <hostname>
127.0.0.1       localhost.localdomain   localhost
::1             localhost.localdomain   localhost

# End of file

/etc/resolv.conf

# Google nameservers
nameserver 8.8.8.8
nameserver 8.8.4.4

/etc/dhcpcd.conf

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Inform the DHCP server of our hostname for DDNS.
hostname
# To share the DHCP lease across OSX and Windows a ClientID is needed.
# Enabling this may get a different lease than the kernel DHCP client.
# Some upstream DHCP servers may also require a ClientID, such as FRITZ!Box.
clientid

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier

# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
noipv4ll
nohook resolv.conf

Offline

#6 2013-03-08 15:16:22

broi
Member
From: Bosnia & Herzegovina
Registered: 2011-12-10
Posts: 127

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

After my ISP read this Topic's posts they pointed me at link where it says I should comment the line

 noipv4ll 

in my /etc/dhcpcd.conf and I did it.
Now I have different systemctl status of dhcpcd@eth0 which is, I hope, a good sign:

[ibrahim@broislinux ~]$ sudo systemctl status dhcpcd@eth0
[sudo] password for ibrahim: 
dhcpcd@eth0.service - dhcpcd on eth0
	  Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; enabled)
	  Active: active (running) since Fri 2013-03-08 07:34:12 CET; 17min ago
	 Process: 298 ExecStart=/usr/sbin/dhcpcd -q -w %I (code=exited, status=0/SUCCESS)
	Main PID: 314 (dhcpcd)
	  CGroup: name=systemd:/system/dhcpcd@.service/eth0
		  `-314 /usr/sbin/dhcpcd -q -w eth0

Mar 08 07:34:07 broislinux dhcpcd[298]: eth0: checking for 169.254.26.153
Mar 08 07:34:11 broislinux dhcpcd[298]: eth0: sending IPv6 Router Solicitation
Mar 08 07:34:12 broislinux dhcpcd[298]: eth0: using IPv4LL address 169.254.26.153
Mar 08 07:34:12 broislinux dhcpcd[298]: forked to background, child pid 314
Mar 08 07:34:12 broislinux systemd[1]: Started dhcpcd on eth0.
Mar 08 07:34:15 broislinux dhcpcd[314]: eth0: sending IPv6 Router Solicitation
Mar 08 07:34:15 broislinux dhcpcd[314]: eth0: broadcasting for a lease
Mar 08 07:34:19 broislinux dhcpcd[314]: eth0: sending IPv6 Router Solicitation
Mar 08 07:34:19 broislinux dhcpcd[314]: eth0: no IPv6 Routers available
Mar 08 07:35:01 broislinux systemd[1]: Started dhcpcd on eth0.

but I can't use internet even starting dhcpcd@eth0 was successfull.
Then I tried disabling ipv6 (adding "ipv6.disable=1" to kernel line) with no success, but yet different dhcpcd@eth0 status:

[ibrahim@broislinux ~]$ sudo systemctl status dhcpcd
dhcpcd.service - dhcpcd on all interfaces
	  Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled)
	  Active: active (running) since Fri 2013-03-08 07:59:25 CET; 5s ago
	 Process: 570 ExecStart=/sbin/dhcpcd -q -b (code=exited, status=0/SUCCESS)
	Main PID: 571 (dhcpcd)
	  CGroup: name=systemd:/system/dhcpcd.service
		  `-571 /sbin/dhcpcd -q -b

Mar 08 07:59:25 broislinux systemd[1]: Starting dhcpcd on all interfaces...
Mar 08 07:59:25 broislinux systemd[1]: Started dhcpcd on all interfaces.
Mar 08 07:59:25 broislinux dhcpcd[571]: eth0: checking for 169.254.26.153
Mar 08 07:59:30 broislinux dhcpcd[571]: eth0: using IPv4LL address 169.254.26.153
Mar 08 07:59:35 broislinux dhcpcd[571]: eth0: broadcasting for a lease

Strange, it's active and running but I still can't use internet.
btw. My IP is 178.239.28.236, not 169.254.26.153 which uses IPv4LL above, could that be a problem?

Offline

#7 2013-03-09 18:23:13

broi
Member
From: Bosnia & Herzegovina
Registered: 2011-12-10
Posts: 127

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

With my current Arch Linux I can't connect to internet, nor with Lubuntu LiveCD, but I always could, now I tried with my sister's laptop with Linux Mint 14 and I connected successfully.. Now I really don't understand what's going on..

Offline

#8 2013-03-09 19:16:02

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

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

The 169.* IP address is the result of the problem. Try commenting out

nohook resolv.conf

at the end of your dhcpcd.conf, make a backup of resolv.conf, delete the original conf and try again by restarting the service. Provide us with "ip r" output as well after an unsuccessful connection try.

Offline

#9 2013-03-09 20:23:26

broi
Member
From: Bosnia & Herzegovina
Registered: 2011-12-10
Posts: 127

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

Strike0 wrote:

The 169.* IP address is the result of the problem. Try commenting out

nohook resolv.conf

at the end of your dhcpcd.conf, make a backup of resolv.conf, delete the original conf and try again by restarting the service. Provide us with "ip r" output as well after an unsuccessful connection try.

I commented nohook resolv.conf, made a backup of resolv.conf and then removed the original, then I started the service:

[ibrahim@broislinux ~]$ sudo systemctl status dhcpcd@eth0
dhcpcd@eth0.service - dhcpcd on eth0
	  Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; enabled)
	  Active: active (running) since Sat 2013-03-09 13:19:36 CET; 3s ago
	 Process: 814 ExecStop=/usr/sbin/dhcpcd -x %I (code=exited, status=0/SUCCESS)
	 Process: 829 ExecStart=/usr/sbin/dhcpcd -q -w %I (code=exited, status=0/SUCCESS)
	Main PID: 846 (dhcpcd)
	  CGroup: name=systemd:/system/dhcpcd@.service/eth0
		  `-846 /usr/sbin/dhcpcd -q -w eth0

Mar 09 13:19:31 broislinux systemd[1]: Starting dhcpcd on eth0...
Mar 09 13:19:31 broislinux dhcpcd[829]: version 5.6.4 starting
Mar 09 13:19:31 broislinux dhcpcd[829]: eth0: sending IPv6 Router Solicitation
Mar 09 13:19:31 broislinux dhcpcd[829]: eth0: checking for 169.254.26.153
Mar 09 13:19:35 broislinux dhcpcd[829]: eth0: sending IPv6 Router Solicitation
Mar 09 13:19:36 broislinux dhcpcd[829]: eth0: using IPv4LL address 169.254.26.153
Mar 09 13:19:36 broislinux dhcpcd[829]: forked to background, child pid 846
Mar 09 13:19:36 broislinux systemd[1]: Started dhcpcd on eth0.
Mar 09 13:19:39 broislinux dhcpcd[846]: eth0: sending IPv6 Router Solicitation

ip r:

[ibrahim@broislinux ~]$ ip r
169.254.0.0/16 dev eth0  proto kernel  scope link  src 169.254.26.153  metric 202

and no connection...

Offline

#10 2013-03-09 20:52:56

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

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

Sorry, I have been traveling on business.

ewaller@odin:~ 1014 %whois 169.254.26.153
#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=169.254.26.153?showDetails=true&showARIN=false&ext=netref2
#

NetRange:       169.254.0.0 - 169.254.255.255
CIDR:           169.254.0.0/16
OriginAS:       
NetName:        LINKLOCAL-RFC3927-IANA-RESERVED
NetHandle:      NET-169-254-0-0-1
Parent:         NET-169-0-0-0-0
NetType:        IANA Special Use
Comment:        This is the "link local" block. It was set
Comment:        aside for this special use in the Standards                     
Comment:        Track document, RFC 3927 and was further
Comment:        documented in the Best Current Practice
Comment:        RFC 5735, which can  be found at:
Comment:        http://www.rfc-editor.org/rfc/rfc3927.txt
Comment:        http://www.rfc-editor.org/rfc/rfc5735.txt
Comment:        It is allocated for communication between hosts                     
Comment:        on a single link. Hosts obtain these addresses                     
Comment:        by auto-configuration, such as when a DHCP                     
Comment:        server cannot be found.
Comment:        A router MUST NOT forward a packet with an IPv4                     
Comment:        Link-Local source or destination address,                     
Comment:        irrespective  of the router's default route configuration                     
Comment:        or routes obtained from dynamic routing protocols.                     
Comment:        A  router which receives a packet with an IPv4                     
Comment:        Link-Local source or destination address MUST NOT                     
Comment:        forward the packet. This prevents forwarding of                     
Comment:        packets back onto the network segment from which                     
Comment:        they originated, or to any other segment.
RegDate:        1998-01-27
Updated:        2010-03-15
Ref:            http://whois.arin.net/rest/net/NET-169-254-0-0-1

OrgName:        Internet Assigned Numbers Authority
OrgId:          IANA
Address:        12025 Waterfront Drive
Address:        Suite 300
City:           Los Angeles
StateProv:      CA
PostalCode:     90292
Country:        US
RegDate:        
Updated:        2012-08-31
Ref:            http://whois.arin.net/rest/org/IANA

OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName:   Internet Corporation for Assigned Names and Number
OrgAbusePhone:  +1-310-301-5820 
OrgAbuseEmail:  abuse@iana.org
OrgAbuseRef:    http://whois.arin.net/rest/poc/IANA-IP-ARIN

OrgTechHandle: IANA-IP-ARIN
OrgTechName:   Internet Corporation for Assigned Names and Number
OrgTechPhone:  +1-310-301-5820 
OrgTechEmail:  abuse@iana.org
OrgTechRef:    http://whois.arin.net/rest/poc/IANA-IP-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#

ewaller@odin:~ 1015 %

If you read through that whois record, it describes what is a 169.x.x.x record.  Basically, your machine cannot find a DHCP server, so it picks it's own address and tries to use it.  This is useful in an environment wehre you want to create a simple network of several machines, but have no need to route to the Internet.  It lets machines find each other on things like ad-hoc networks.   It is not appropriate for trying to obtain an IP on a private network that needs to be routable to Internet.

So the problem is that your machine cannot get an IP address from a DHCP server.

Let us take a different tack.  You say it works in XP ?  Is that on this machine, or is it a different computer.  If it is this computer, reboot to XP, prove that the network works, open a console (run cmd) and execute the command ipconfig.   Post the output here (if you can), otherwise take note of the address, mask and gateway information and report back.

Last edited by ewaller (2013-03-09 20:53:57)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Offline

#11 2013-03-09 21:03:47

broi
Member
From: Bosnia & Herzegovina
Registered: 2011-12-10
Posts: 127

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

Thank you for info smile

ipconfig in Windows XP:

Windows IP Configuration

Ethernet adapter Local Area Connection:
	Connection-specific DNS Suffic  . :
	IP Address. . . . . . . . . . . . : 192.168.1.50
	Subnet Mask . . . . . . . . . . . : 255.255.255.0
	Default Gateway . . . . . . . . . : 192.168.1.20

My XP is on the same machine as my Arch (I dual boot).
(I tried connecting my cable to the laptop (other machine, Linux Mint) and internet works just fine, hmmm)

Last edited by broi (2013-03-09 21:07:01)

Offline

#12 2013-03-09 21:13:17

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

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

Then let us try this.  Go back to Linux, and set that address as a static address

ip addr flush dev eth0
ip addr add 192.168.1.50/24 dev eth0

Then, see if you can ping 192.168.1.20.   If that works, we will move on to setting up your routes and get some basic service.

After that, we will know things are working and will go back to fighting with dhcpcd.

EDIT: BTW, you need to run those as root.

Last edited by ewaller (2013-03-09 21:14:03)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Offline

#13 2013-03-09 21:26:34

broi
Member
From: Bosnia & Herzegovina
Registered: 2011-12-10
Posts: 127

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

ewaller wrote:

Then let us try this.  Go back to Linux, and set that address as a static address

ip addr flush dev eth0
ip addr add 192.168.1.50/24 dev eth0

Then, see if you can ping 192.168.1.20.   If that works, we will move on to setting up your routes and get some basic service.

After that, we will know things are working and will go back to fighting with dhcpcd.

EDIT: BTW, you need to run those as root.

(dhcpcd@eth0 service not started:)

[ibrahim@broislinux ~]$ sudo ip addr flush dev eth0
[ibrahim@broislinux ~]$ sudo ip addr add 192.168.1.50/24 dev eth0
[ibrahim@broislinux ~]$ ping 192.168.1.20
connect: Network is unreachable

(dhcpcd@eth0 started, just in case):

[ibrahim@broislinux ~]$ sudo systemctl start dhcpcd@eth0             
[ibrahim@broislinux ~]$ sudo ip addr flush dev eth0
[ibrahim@broislinux ~]$ sudo ip addr add 192.168.1.50/24 dev eth0
[ibrahim@broislinux ~]$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
From 192.168.1.50 icmp_seq=1 Destination Host Unreachable
From 192.168.1.50 icmp_seq=2 Destination Host Unreachable
From 192.168.1.50 icmp_seq=3 Destination Host Unreachable
From 192.168.1.50 icmp_seq=4 Destination Host Unreachable
From 192.168.1.50 icmp_seq=5 Destination Host Unreachable
From 192.168.1.50 icmp_seq=6 Destination Host Unreachable
From 192.168.1.50 icmp_seq=7 Destination Host Unreachable
^C
--- 192.168.1.20 ping statistics ---
7 packets transmitted, 0 received, +7 errors, 100% packet loss, time 6009ms
pipe 4

Offline

#14 2013-03-11 21:51:51

broi
Member
From: Bosnia & Herzegovina
Registered: 2011-12-10
Posts: 127

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

I don't know what of a solution it would be, but maybe I should consider to risk by reinstalling Arch from scratch...

Offline

#15 2013-03-12 11:32:20

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

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

If it worked before, it is more likely your new ISP's DHCP server requires some extra twirk. Re-installing would be a last resort really.  In any case before re-installing you can try if you can connecting using the current Arch ISO. No need to install it first to test. 

You started the try to manual assignment of an IP as per wiki: https://wiki.archlinux.org/index.php/Ne … assignment
1. Try that again according to wiki, also assigning a default route to 192.168.1.20. Ask here if you have questions about it.
2 .From your first post I understand that you tried the Ubuntu 11.10 live CD and that did not connect either?

Offline

#16 2013-03-15 10:10:57

broi
Member
From: Bosnia & Herzegovina
Registered: 2011-12-10
Posts: 127

Re: [SOLVED]Problem connecting to wired network (dynamic IP) after I moved

I've been searching in Windows network settings to check whether my ISP changed ANYTHING so I can do the same on Lin system, I was a bit sceptical about them claiming they did not change anything, and yes, I've found that, I found that Ethernet speed is not set on automatic anymore, but it was, now it's "10 MB, Half Duplex".
So I did a bit googling on how to change ethernet speed on Linux and I found post on some forum that I can do it in few ways:

in grub it would be a line like
ether=0,0,0,0x10
buth then with the settings specific for your driver.

else and easier, you can run ethtools with a line like:

ethtool -s eth0 speed 10 duplex full autoneg off

and if you add the same line to your rc.local it will automatically run at boottime

Usage:
ethtool DEVNAME
ethtool -i DEVNAME
ethtool -s DEVNAME \
[ speed {10,100,1000} ] \
[ duplex {half,full} ] \
[ port {tp,aui,mii,fibre} ] \
[ autoneg {on,off} ] \
[ phyad %d ] \
[ xcvr {internal,external} ] \
[ wol [pumbagsd]+ ] \
[ sopass %x:%x:%x:%x:%x:%x ]

so I ran

 ethtool -s eth0 speed 10 duplex full autoneg off 

and now I can connect to internet with no problems using NetworkManager, but dhcpcd@eth0:

[ibrahim@broislinux ~]$ sudo systemctl status dhcpcd@eth0
dhcpcd@eth0.service - dhcpcd on eth0
	  Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; enabled)
	  Active: active (running) since Fri 2013-03-15 03:06:19 CET; 7s ago
	 Process: 819 ExecStop=/usr/sbin/dhcpcd -x %I (code=exited, status=0/SUCCESS)
	 Process: 824 ExecStart=/usr/sbin/dhcpcd -q -w %I (code=exited, status=0/SUCCESS)
	Main PID: 843 (dhcpcd)
	  CGroup: name=systemd:/system/dhcpcd@.service/eth0
		  `-843 /usr/sbin/dhcpcd -q -w eth0

Mar 15 03:06:13 broislinux dhcpcd[824]: eth0: sending IPv6 Router Solicitation
Mar 15 03:06:13 broislinux dhcpcd[824]: eth0: rebinding lease of 192.168.1.50
Mar 15 03:06:13 broislinux dhcpcd[824]: eth0: acknowledged 192.168.1.50 from 192.168.1.20
Mar 15 03:06:13 broislinux dhcpcd[824]: eth0: checking for 192.168.1.50
Mar 15 03:06:17 broislinux dhcpcd[824]: eth0: sending IPv6 Router Solicitation
Mar 15 03:06:19 broislinux dhcpcd[824]: eth0: leased 192.168.1.50 for 3600 seconds
Mar 15 03:06:19 broislinux systemd[1]: Started dhcpcd on eth0.
Mar 15 03:06:21 broislinux dhcpcd[843]: eth0: sending IPv6 Router Solicitation
Mar 15 03:06:25 broislinux dhcpcd[843]: eth0: sending IPv6 Router Solicitation
Mar 15 03:06:25 broislinux dhcpcd[843]: eth0: no IPv6 Routers available

it assigns correct IP but even after enabling it I can't use ping, etc. but good thing is I can connect via NetworkManager(applet+service) with no problems.
I guess this is solved. Thank you all for your will to help me smile

Offline

Board footer

Powered by FluxBB