[SOLVED]No network, no ipv4 when executing ip addr

hiveNzin0 · 2016-06-23 20:26:14

Hi,

I installed Windows last week and I just restored grub today to use Arch again. When I booted, I had no network.

When I execute :
- "ip addr", I don't see any ipv4 address, only ipv6.
- "systemctl status dhcpcd", the service is active (running).
- "systemctl status networkmanager", service is also active (running).

If I boot on the archlinux ISO, I have internet (I could download os-prober without any extra config)

I use dhcp, I have an internet connection on windows so I know it is not a problem with the cable.

Any idea what's wrong with my dhcp service ?

Thank you.

Last edited by hiveNzin0 (2016-06-29 17:50:15)

hiveNzin0 · 2016-06-24 14:47:38

I am really lost, I don't know what kind of logs or tests I should check/do to find what the problem is.

I am open to any suggestion (I don't want to reinstall my system just yet).

I only have a basic knowledge of networking. I can't even ping my router.

I have this connection :

internet -> router (192.168.0.1) -> TP-LINK (I use the LAN port, not the WAN so it is the same network) -> my PC.

I cannot even ping my router (192.168.0.1)

Thank you.

edit : I restarted everything and now I get an ipv4 address but it is not one we can expect on a local network (169.254.217.166/16, brd 169.254.255.255)

Last edited by hiveNzin0 (2016-06-24 14:57:59)

\hbar · 2016-06-24 15:01:46

From what I understood, you see an 'inet6' entry in 'ip addr' but no 'inet4', correct?

Did you disable ipv4?

How do you connect to the network? Do you use netctl? Are there error messages?

ewaller · 2016-06-24 15:07:31

That us a "Self assigned" address. Network Manager made it up.
Is this a wired connection? I think you imply it.

What are the make and model of your NIC? (Check with lpci -nn )

Edit: Hey h-bar. Good to see you

Last edited by ewaller (2016-06-24 15:08:24)

hiveNzin0 · 2016-06-24 17:02:07

\hbar wrote:

From what I understood, you see an 'inet6' entry in 'ip addr' but no 'inet4', correct?
Did you disable ipv4?
How do you connect to the network? Do you use netctl? Are there error messages?

I see several inet6. I have inet now (after several reboot of the computer and the TP-Link "switch") but the ip looks like a public IP address, not a local ip adresse, it is not part of my local network. It should be 192.168.0.X and it is 169.254.217.166

I am sure I didn't disable ipv4, how can I check that ?

The network is wired. I don't think I use netctl, I usually use dhcpcd and networkmanager service. I don't even have the network manager icon at the bottom right of KDE bar, weird.

What log should I check for errors ?

When I run systemctl status dhcpcd, I have active (running) and the following :

waiting for carrier, carrier acquired, soliciting a DHCP lease, probing for an IPv4LL address, using ipv4all address 169... adding default route.
DHCP seems to be working but it doesn't get a correct IP address.

hiveNzin0 · 2016-06-24 17:07:13

ewaller wrote:

That us a "Self assigned" address. Network Manager made it up.
Is this a wired connection? I think you imply it.
What are the make and model of your NIC? (Check with lpci -nn )
Edit: Hey h-bar. Good to see you

Yes, wired connection. I don't have wifi setup.

Assuming NIC is the network card : 00:19.0 Ethernet controller (0200): Intel Corporation Ethernet Connection I217-V (8086:153b) (rev 05)

if that makes any sense

The network worked fine before I installed windows. I used windows for a week or two before fixing the grub that was destroyed by the windows install and now I have this problem that I don't have on the arch live CD from which I could download os-prober.

I am sure it is a configuration problem but I don't know where to look.

Thanks.

Slithery · 2016-06-24 17:10:57

hiveNzin0 wrote:

I usually use dhcpcd and networkmanager service.

This could be the problem, you should only have one service managing your network otherwise they can conflict.

hiveNzin0 · 2016-06-24 17:12:46

slithery wrote:

hiveNzin0 wrote:
I usually use dhcpcd and networkmanager service.
This could be the problem, you should only have one service managing your network otherwise they can conflict.

Okay, which one should I remove ? It used to work without any problem.

Slithery · 2016-06-24 17:14:15

Simple. Remove the one you don't want to use.

hiveNzin0 · 2016-06-25 16:27:38

slithery wrote:

Simple. Remove the one you don't want to use.

I only kept dhcpcd. Now, I don't have ipv6 addresses anymore and I only have one ipv4 but the IP that is assigned is not one from my local network range.

It is 169.X.X.X/16 instead of 192.168.0.X.

Any idea on what config I should check ?

Thank you.

edit : I am trying to follow advices from this thread : https://bbs.archlinux.org/viewtopic.php?id=159274

I checked my settings on windows and I have internet with 192.168.0.18, 255.255.255.0, 192.168.0.1

I tried to assign the address 192.168.0.18 and ping 192.168.0.1 but I get "Destination host unreachable"

I tried to restart dhcpcd@eno1.service but I get "Failed to start dhcpcd on eno1".

It is like my computer is not connected to the network but when I reboot on windows or a live cd, everything works fine.

Last edited by hiveNzin0 (2016-06-25 16:44:05)

\hbar · 2016-06-25 17:32:18

You're not connected to the network. The IP address you get is, as ewaller mentionned earlier, a self-assigned IP.

Try to run dhcpcd manually, and see if you get error messages.

hiveNzin0 · 2016-06-26 09:00:54

\hbar wrote:

You're not connected to the network. The IP address you get is, as ewaller mentionned earlier, a self-assigned IP.
Try to run dhcpcd manually, and see if you get error messages.

I tried "dhcpcd -r 192.168.0.18" and I get a timed out

I tried to restart dhcpcd with the service "systemctl restart dhcpcd, systemctl status dhcpcd" and I get active(running) and started dhcpcd on all interfaces but I still don't get an ip address from the dhcp server (192.168.0.1).

I'll try to plug my network cable directly in my computer instead of going through the TP-Link switch but if it is not that, I have really no idea.

Thanks.

edit : even when I am directly connected to the router (192.168.0.1), I cannot get an ip address from dhcp. Maybe there is a configuration problem somewhere. I only have dhcpcd started as a service (no networkamanger or systemd-dhcpcd).

What kind of software should I uninstall completely and reinstall again ? dhcpcd ? Something else ?

Last edited by hiveNzin0 (2016-06-26 09:04:54)

\hbar · 2016-06-26 13:41:29

There's no need to request an IP address. The point of running dhcpcd manually was to check for error messages, so you should either run it in debug mode, or check the log.

hiveNzin0 · 2016-06-27 17:20:53

\hbar wrote:

There's no need to request an IP address. The point of running dhcpcd manually was to check for error messages, so you should either run it in debug mode, or check the log.

I ran "sudo dhcpcd" and it only looked for ipv6 routers. I switched my modem to ipv4 only mode.

I have the following result :

soliciting an ipv6 router
soliciting a dhcp lease
no ipv6 routers available
timed out
forked to background

Is it possible that I have ipv4 disabled ? I am sure that I never did that on purpose. How can I check that ?

edit : I moved /etc/dhcpcd.conf -> /etc/dhcpcd.backup and restarted dhcpcd (the file is not recreated)

now I have the following :

control_open: connection refused
dev: loaded udev
ipv6 kernel autoconf disabled
adding address (an ipv6 address)
DUID some random alphanumeric characters
IAID 49:ae:50:a4
soliciting an ipv6 router
soliciting a dhcp lease
probing for an ipv4all adress
using ipv4all address 169.254.217.166
adding route to 169.254.0.0/16
adding default route
forked to background

Last edited by hiveNzin0 (2016-06-27 17:24:48)

\hbar · 2016-06-27 21:12:45

And what happens if you run dhcpcd with the '-4' flag?

hiveNzin0 · 2016-06-28 05:15:29

\hbar wrote:

And what happens if you run dhcpcd with the '-4' flag?

soliciting a DHCP lease
timed out
forked to background

Maybe I have a problem with my router but my Synology NAS is connected with a RJ45 and no problem, my TV with a cable sometimes has problem with the cable, a TV box used for HD channels is connecting with a RJ45 and no problem. Windows has no problem with ethernet cable.

I'll bring back my laptop from work and try the dhcp with the same cable tonight, I hope I will have more information.

Thanks.

hiveNzin0 · 2016-06-28 17:43:16

I confirm that there is a only a problem with my desktop computer with arch.

I factory reset the modem : still the same problem
I used my laptop with arch using the same cable and same ethernet port on the modem : it works, I get internet (ipv4 and dhcp from the router)
Windows and arch live CD on the desktop computer : no problem, I have internet.

How can I copy my network settings from my laptop or the arch live cd to my real desktop ?

Could it be that I updated my kernel juste before installing windows and something is broken with this kernel. Since I haven't been able to update to the latest kernel on the desktop (I have my system up to date on my laptop but the laptop has different specs), maybe I am stuck with this problem.

Should I compile the kernel from kernel.org or should I just copy the official linux kernel from arch and try to install it ? Do I need another package than linux 4.6.3-1 ?

Thank you.

\hbar · 2016-06-28 19:16:20

It's not recommended to only update certain packages (https://wiki.archlinux.org/index.php/Sy … nsupported). If your system is not up to date, then I suggest you do that now.

If you suspect your problem is due to a new kernel, you can install the linux-lts package, which is older. You can also check whether ipv4 is enabled in your kernel by running

sysctl -a | grep ipv4

The dhcpcd configuration file is locate in '/etc/dhcpcd.conf'

hiveNzin0 · 2016-06-28 19:55:18

\hbar wrote:

It's not recommended to only update certain packages (https://wiki.archlinux.org/index.php/Sy … nsupported). If your system is not up to date, then I suggest you do that now.
If you suspect your problem is due to a new kernel, you can install the linux-lts package, which is older. You can also check whether ipv4 is enabled in your kernel by running
sysctl -a | grep ipv4
The dhcpcd configuration file is locate in '/etc/dhcpcd.conf'

I installed a LTS kernel but it is not that.

I ran dhcpcd -d to get more information and I can see this :

sending DISCOVER next in xxx
sending DISCOVER next in xxx
sending DISCOVER next in xxx
sending DISCOVER next in xxx
timed out

I can't find the thread again but I found a post here about that and it should be a 4 steps discussion between my computer and the DHCP server and I only have the first step.

Here is the output of the command you wrote, I don't know what I should expect, sorry.

sudo sysctl -a | grep ipv4
net.ipv4.cipso_cache_bucket_size = 10
net.ipv4.cipso_cache_enable = 1
net.ipv4.cipso_rbm_optfmt = 0
net.ipv4.cipso_rbm_strictvalid = 1
net.ipv4.conf.all.accept_local = 0
net.ipv4.conf.all.accept_redirects = 1
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.all.arp_accept = 0
net.ipv4.conf.all.arp_announce = 0
net.ipv4.conf.all.arp_filter = 0
net.ipv4.conf.all.arp_ignore = 0
net.ipv4.conf.all.arp_notify = 0
net.ipv4.conf.all.bootp_relay = 0
net.ipv4.conf.all.disable_policy = 0
net.ipv4.conf.all.disable_xfrm = 0
net.ipv4.conf.all.force_igmp_version = 0
net.ipv4.conf.all.forwarding = 0
net.ipv4.conf.all.igmpv2_unsolicited_report_interval = 10000
net.ipv4.conf.all.igmpv3_unsolicited_report_interval = 1000
net.ipv4.conf.all.ignore_routes_with_linkdown = 0
net.ipv4.conf.all.log_martians = 0
net.ipv4.conf.all.mc_forwarding = 0
net.ipv4.conf.all.medium_id = 0
net.ipv4.conf.all.promote_secondaries = 1
net.ipv4.conf.all.proxy_arp = 0
net.ipv4.conf.all.proxy_arp_pvlan = 0
net.ipv4.conf.all.route_localnet = 0
net.ipv4.conf.all.rp_filter = 1
net.ipv4.conf.all.secure_redirects = 1
net.ipv4.conf.all.send_redirects = 1
net.ipv4.conf.all.shared_media = 1
net.ipv4.conf.all.src_valid_mark = 0
net.ipv4.conf.all.tag = 0
net.ipv4.conf.default.accept_local = 0
net.ipv4.conf.default.accept_redirects = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.default.arp_accept = 0
net.ipv4.conf.default.arp_announce = 0
net.ipv4.conf.default.arp_filter = 0
net.ipv4.conf.default.arp_ignore = 0
net.ipv4.conf.default.arp_notify = 0
net.ipv4.conf.default.bootp_relay = 0
net.ipv4.conf.default.disable_policy = 0
net.ipv4.conf.default.disable_xfrm = 0
net.ipv4.conf.default.force_igmp_version = 0
net.ipv4.conf.default.forwarding = 0
net.ipv4.conf.default.igmpv2_unsolicited_report_interval = 10000
net.ipv4.conf.default.igmpv3_unsolicited_report_interval = 1000
net.ipv4.conf.default.ignore_routes_with_linkdown = 0
net.ipv4.conf.default.log_martians = 0
net.ipv4.conf.default.mc_forwarding = 0
net.ipv4.conf.default.medium_id = 0
net.ipv4.conf.default.promote_secondaries = 1
net.ipv4.conf.default.proxy_arp = 0
net.ipv4.conf.default.proxy_arp_pvlan = 0
net.ipv4.conf.default.route_localnet = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.secure_redirects = 1
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.default.shared_media = 1
net.ipv4.conf.default.src_valid_mark = 0
net.ipv4.conf.default.tag = 0
net.ipv4.conf.eno1.accept_local = 0
net.ipv4.conf.eno1.accept_redirects = 1
net.ipv4.conf.eno1.accept_source_route = 0
net.ipv4.conf.eno1.arp_accept = 0
net.ipv4.conf.eno1.arp_announce = 0
net.ipv4.conf.eno1.arp_filter = 0
net.ipv4.conf.eno1.arp_ignore = 0
net.ipv4.conf.eno1.arp_notify = 0
net.ipv4.conf.eno1.bootp_relay = 0
net.ipv4.conf.eno1.disable_policy = 0
net.ipv4.conf.eno1.disable_xfrm = 0
net.ipv4.conf.eno1.force_igmp_version = 0
net.ipv4.conf.eno1.forwarding = 0
net.ipv4.conf.eno1.igmpv2_unsolicited_report_interval = 10000
net.ipv4.conf.eno1.igmpv3_unsolicited_report_interval = 1000
net.ipv4.conf.eno1.ignore_routes_with_linkdown = 0
net.ipv4.conf.eno1.log_martians = 0
net.ipv4.conf.eno1.mc_forwarding = 0
net.ipv4.conf.eno1.medium_id = 0
net.ipv4.conf.eno1.promote_secondaries = 1
net.ipv4.conf.eno1.proxy_arp = 0
net.ipv4.conf.eno1.proxy_arp_pvlan = 0
net.ipv4.conf.eno1.route_localnet = 0
net.ipv4.conf.eno1.rp_filter = 1
net.ipv4.conf.eno1.secure_redirects = 1
net.ipv4.conf.eno1.send_redirects = 1
net.ipv4.conf.eno1.shared_media = 1
net.ipv4.conf.eno1.src_valid_mark = 0
net.ipv4.conf.eno1.tag = 0
net.ipv4.conf.lo.accept_local = 0
net.ipv4.conf.lo.accept_redirects = 1
net.ipv4.conf.lo.accept_source_route = 1
net.ipv4.conf.lo.arp_accept = 0
net.ipv4.conf.lo.arp_announce = 0
net.ipv4.conf.lo.arp_filter = 0
net.ipv4.conf.lo.arp_ignore = 0
net.ipv4.conf.lo.arp_notify = 0
net.ipv4.conf.lo.bootp_relay = 0
net.ipv4.conf.lo.disable_policy = 1
net.ipv4.conf.lo.disable_xfrm = 1
net.ipv4.conf.lo.force_igmp_version = 0
net.ipv4.conf.lo.forwarding = 0
net.ipv4.conf.lo.igmpv2_unsolicited_report_interval = 10000
net.ipv4.conf.lo.igmpv3_unsolicited_report_interval = 1000
net.ipv4.conf.lo.ignore_routes_with_linkdown = 0
net.ipv4.conf.lo.log_martians = 0
net.ipv4.conf.lo.mc_forwarding = 0
net.ipv4.conf.lo.medium_id = 0
net.ipv4.conf.lo.promote_secondaries = 0
net.ipv4.conf.lo.proxy_arp = 0
net.ipv4.conf.lo.proxy_arp_pvlan = 0
net.ipv4.conf.lo.route_localnet = 0
net.ipv4.conf.lo.rp_filter = 0
net.ipv4.conf.lo.secure_redirects = 1
net.ipv4.conf.lo.send_redirects = 1
net.ipv4.conf.lo.shared_media = 1
net.ipv4.conf.lo.src_valid_mark = 0
net.ipv4.conf.lo.tag = 0
net.ipv4.fwmark_reflect = 0
net.ipv4.icmp_echo_ignore_all = 0
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.icmp_errors_use_inbound_ifaddr = 0
net.ipv4.icmp_ignore_bogus_error_responses = 1
net.ipv4.icmp_msgs_burst = 50
net.ipv4.icmp_msgs_per_sec = 1000
net.ipv4.icmp_ratelimit = 1000
net.ipv4.icmp_ratemask = 6168
net.ipv4.igmp_link_local_mcast_reports = 1
net.ipv4.igmp_max_memberships = 20
net.ipv4.igmp_max_msf = 10
net.ipv4.igmp_qrv = 2
net.ipv4.inet_peer_maxttl = 600
net.ipv4.inet_peer_minttl = 120
net.ipv4.inet_peer_threshold = 65664
net.ipv4.ip_default_ttl = 64
net.ipv4.ip_dynaddr = 0
net.ipv4.ip_early_demux = 1
net.ipv4.ip_forward = 0
net.ipv4.ip_forward_use_pmtu = 0
net.ipv4.ip_local_port_range = 32768    60999
net.ipv4.ip_local_reserved_ports = 
net.ipv4.ip_no_pmtu_disc = 0
net.ipv4.ip_nonlocal_bind = 0
net.ipv4.ipfrag_high_thresh = 4194304
net.ipv4.ipfrag_low_thresh = 3145728
net.ipv4.ipfrag_max_dist = 64
net.ipv4.ipfrag_secret_interval = 0
net.ipv4.ipfrag_time = 30
net.ipv4.neigh.default.anycast_delay = 100
net.ipv4.neigh.default.app_solicit = 0
net.ipv4.neigh.default.base_reachable_time_ms = 30000
net.ipv4.neigh.default.delay_first_probe_time = 5
net.ipv4.neigh.default.gc_interval = 30
net.ipv4.neigh.default.gc_stale_time = 60
net.ipv4.neigh.default.gc_thresh1 = 128
net.ipv4.neigh.default.gc_thresh2 = 512
net.ipv4.neigh.default.gc_thresh3 = 1024
net.ipv4.neigh.default.locktime = 100
net.ipv4.neigh.default.mcast_resolicit = 0
net.ipv4.neigh.default.mcast_solicit = 3
net.ipv4.neigh.default.proxy_delay = 80
net.ipv4.neigh.default.proxy_qlen = 64
net.ipv4.neigh.default.retrans_time_ms = 1000
net.ipv4.neigh.default.ucast_solicit = 3
net.ipv4.neigh.default.unres_qlen = 31
net.ipv4.neigh.default.unres_qlen_bytes = 65536
net.ipv4.neigh.eno1.anycast_delay = 100
net.ipv4.neigh.eno1.app_solicit = 0
net.ipv4.neigh.eno1.base_reachable_time_ms = 30000
net.ipv4.neigh.eno1.delay_first_probe_time = 5
net.ipv4.neigh.eno1.gc_stale_time = 60
net.ipv4.neigh.eno1.locktime = 100
net.ipv4.neigh.eno1.mcast_resolicit = 0
net.ipv4.neigh.eno1.mcast_solicit = 3
net.ipv4.neigh.eno1.proxy_delay = 80
net.ipv4.neigh.eno1.proxy_qlen = 64
net.ipv4.neigh.eno1.retrans_time_ms = 1000
net.ipv4.neigh.eno1.ucast_solicit = 3
net.ipv4.neigh.eno1.unres_qlen = 31
net.ipv4.neigh.eno1.unres_qlen_bytes = 65536
net.ipv4.neigh.lo.anycast_delay = 100
net.ipv4.neigh.lo.app_solicit = 0
net.ipv4.neigh.lo.base_reachable_time_ms = 30000
net.ipv4.neigh.lo.delay_first_probe_time = 5
net.ipv4.neigh.lo.gc_stale_time = 60
net.ipv4.neigh.lo.locktime = 100
net.ipv4.neigh.lo.mcast_resolicit = 0
net.ipv4.neigh.lo.mcast_solicit = 3
net.ipv4.neigh.lo.proxy_delay = 80
net.ipv4.neigh.lo.proxy_qlen = 64
net.ipv4.neigh.lo.retrans_time_ms = 1000
net.ipv4.neigh.lo.ucast_solicit = 3
net.ipv4.neigh.lo.unres_qlen = 31
net.ipv4.neigh.lo.unres_qlen_bytes = 65536
net.ipv4.ping_group_range = 1    0
net.ipv4.route.error_burst = 500
net.ipv4.route.error_cost = 100
net.ipv4.route.gc_elasticity = 8
net.ipv4.route.gc_interval = 60
net.ipv4.route.gc_min_interval = 0
net.ipv4.route.gc_min_interval_ms = 500
net.ipv4.route.gc_thresh = -1
net.ipv4.route.gc_timeout = 300
net.ipv4.route.max_size = 2147483647
net.ipv4.route.min_adv_mss = 256
net.ipv4.route.min_pmtu = 552
net.ipv4.route.mtu_expires = 600
net.ipv4.route.redirect_load = 2
net.ipv4.route.redirect_number = 9
net.ipv4.route.redirect_silence = 2048
net.ipv4.tcp_abort_on_overflow = 0
net.ipv4.tcp_adv_win_scale = 1
net.ipv4.tcp_allowed_congestion_control = cubic reno
net.ipv4.tcp_app_win = 31
net.ipv4.tcp_autocorking = 1
net.ipv4.tcp_available_congestion_control = cubic reno
net.ipv4.tcp_base_mss = 1024
net.ipv4.tcp_challenge_ack_limit = 100
net.ipv4.tcp_congestion_control = cubic
sysctl: net.ipv4.tcp_dsack = 1
reading key "net.ipv6.conf.all.stable_secret"
net.ipv4.tcp_early_retrans = 3
net.ipv4.tcp_ecn = 2
net.ipv4.tcp_ecn_fallback = 1
net.ipv4.tcp_fack = 1
net.ipv4.tcp_fastopen = 1
net.ipv4.tcp_fastopen_key = 00000000-00000000-00000000-00000000
net.ipv4.tcp_fin_timeout = 60
net.ipv4.tcp_frto = 2
net.ipv4.tcp_fwmark_accept = 0
net.ipv4.tcp_invalid_ratelimit = 500
net.ipv4.tcp_keepalive_intvl = 75
net.ipv4.tcp_keepalive_probes = 9
net.ipv4.tcp_keepalive_time = 7200
net.ipv4.tcp_limit_output_bytes = 262144
net.ipv4.tcp_low_latency = 0
net.ipv4.tcp_max_orphans = 65536
net.ipv4.tcp_max_reordering = 300
net.ipv4.tcp_max_syn_backlog = 512
net.ipv4.tcp_max_tw_buckets = 65536
net.ipv4.tcp_mem = 190578    254106    381156
net.ipv4.tcp_min_rtt_wlen = 300
net.ipv4.tcp_min_tso_segs = 2
net.ipv4.tcp_moderate_rcvbuf = 1
net.ipv4.tcp_mtu_probing = 0
net.ipv4.tcp_no_metrics_save = 0
net.ipv4.tcp_notsent_lowat = -1
net.ipv4.tcp_orphan_retries = 0
net.ipv4.tcp_pacing_ca_ratio = 120
net.ipv4.tcp_pacing_ss_ratio = 200
net.ipv4.tcp_probe_interval = 600
net.ipv4.tcp_probe_threshold = 8
net.ipv4.tcp_recovery = 1
net.ipv4.tcp_reordering = 3
net.ipv4.tcp_retrans_collapse = 1
net.ipv4.tcp_retries1 = 3
net.ipv4.tcp_retries2 = 15
net.ipv4.tcp_rfc1337 = 0
net.ipv4.tcp_rmem = 4096    87380    6291456
net.ipv4.tcp_sack = 1
net.ipv4.tcp_slow_start_after_idle = 1
net.ipv4.tcp_stdurg = 0
net.ipv4.tcp_syn_retries = 6
net.ipv4.tcp_synack_retries = 5
net.ipv4.tcp_syncookies = 1
net.ipv4.tcp_thin_dupack = 0
net.ipv4.tcp_thin_linear_timeouts = 0
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_tso_win_divisor = 3
net.ipv4.tcp_tw_recycle = 0
net.ipv4.tcp_tw_reuse = 0
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_wmem = 4096    16384    4194304
net.ipv4.tcp_workaround_signed_windows = 0
net.ipv4.udp_mem = 381159    508212    762318
net.ipv4.udp_rmem_min = 4096
net.ipv4.udp_wmem_min = 4096
net.ipv4.xfrm4_gc_thresh = 2147483647
sysctl: reading key "net.ipv6.conf.default.stable_secret"
sysctl: reading key "net.ipv6.conf.eno1.stable_secret"
sysctl: reading key "net.ipv6.conf.lo.stable_secret"

My interface is eno1.

Last edited by hiveNzin0 (2016-06-29 05:11:42)

\hbar · 2016-06-28 21:45:36

hiveNzin0 wrote:

Here is the output of the command you wrote, I don't know what I should expect, sorry.

That was just in case you wanted to check that ipv4 is enabled in your kernel, which it is. You should use code tags for long output like that.

hiveNzin0 wrote:

sending DISCOVER next in xxx

Odd: when I run 'dhcpcd -d interface_name' I don't see that message. Your system is up to date, right?

I'm starting to run out of ideas. You could monitor your ethernet interface using wireshark to check that the DISCOVER's are actually being sent, and whether the router offers any kind of response. Do you have access to the router logs? Can you confirm that it's receiving something from your computer?

hiveNzin0 · 2016-06-29 04:59:52

Odd: when I run 'dhcpcd -d interface_name' I don't see that message. Your system is up to date, right?
I'm starting to run out of ideas. You could monitor your ethernet interface using wireshark to check that the DISCOVER's are actually being sent, and whether the router offers any kind of response. Do you have access to the router logs? Can you confirm that it's receiving something from your computer?

My system is not up to date (not on my desktop computer where I have the problem). I have a laptop from work with arch and this one is up to date.

This problem is really hard to understand. I booted the arch live cd from which I could reinstall grub (where I downloaded os-prober successfully) and I don't have internet anymore.
I mounted all my directories (/, /boot, /home) and chroot. I was hoping I could do an system upgrade in chroot environment but I don't have internet now.

The arch live cd is from December 2015, I'll try with the latest one tonight.

Thanks for your help.

edit : maybe I never had internet when I booted arch live cd to fix grub. Maybe the package was downloaded from the disk and that's why I thought I had internet.
Should that be the case, I can have internet with everything except my desktop computer with arch even when I run an arch livecd.

Could it be some kind of conflict since I reinstalled windows ? Some kind of setup saved in the router (even if I did a factory reset) that linked my network card to something and I can't have that setup on my arch system ? Maybe it is far fetched, sorry I only have basic knowledge of networking.

edit 2 : if I don't have a solution tonight, I will reinstall everything completely. Thanks for the help.

Last edited by hiveNzin0 (2016-06-29 08:03:37)

rsmarples · 2016-06-29 08:38:48

hiveNzin0 wrote:

I ran dhcpcd -d to get more information and I can see this :
sending DISCOVER next in xxx
sending DISCOVER next in xxx
sending DISCOVER next in xxx
sending DISCOVER next in xxx
timed out

So that means dhcpcd sent a DISCOVER (could be RENEW or REBIND or similar) and not received a reply.
dhcpcd thinks the interface has a working carrier which is good.

This means that (in the likeliest order) either the DHCP server is not running OR has received your request but not sent a reply OR there is some other kind of failure in the middle.

For the middle case, try removing duid in dhcpcd.conf and using clientid instead, or failing that commenting both out. Some nasty DHCP servers are picky about those settings.
For the other two cases, good luck as I can't help there.

Lastly, could you state the dhcpcd version please?
dhcpcd --version

hiveNzin0 · 2016-06-29 09:52:02

rsmarples wrote:

hiveNzin0 wrote:
I ran dhcpcd -d to get more information and I can see this :
sending DISCOVER next in xxx
sending DISCOVER next in xxx
sending DISCOVER next in xxx
sending DISCOVER next in xxx
timed out
So that means dhcpcd sent a DISCOVER (could be RENEW or REBIND or similar) and not received a reply.
dhcpcd thinks the interface has a working carrier which is good.
This means that (in the likeliest order) either the DHCP server is not running OR has received your request but not sent a reply OR there is some other kind of failure in the middle.
For the middle case, try removing duid in dhcpcd.conf and using clientid instead, or failing that commenting both out. Some nasty DHCP servers are picky about those settings.
For the other two cases, good luck as I can't help there.
Lastly, could you state the dhcpcd version please?
dhcpcd --version

Hi,

I am 100% sure that the dhcp server is running because I have internet using it on all other devices (even the same computer with windows).

I'll check the modem logs for point 2 and 3. I already tried to use the clientid instead of the duid and it doesn't work.
I will try to comment both out and see what happens. Thanks for the suggestion.

I'll edit with the dhcpcd version tonight. I am at work at the moment so I don't have access to that info.

\hbar · 2016-06-29 12:14:55

rsmarples wrote:

This means that (in the likeliest order) either the DHCP server is not running OR has received your request but not sent a reply OR there is some other kind of failure in the middle.

Or the DHCP server sent the reply but the computer doesn't see it. Wireshark could help figure out which it is.

So it's after playing around with windows that everything stopped working. Are you using BIOS or EFI? Can you reset the BIOS/EFI variables?

hiveNzin0 · 2016-06-29 12:57:55

\hbar wrote:

rsmarples wrote:
This means that (in the likeliest order) either the DHCP server is not running OR has received your request but not sent a reply OR there is some other kind of failure in the middle.
Or the DHCP server sent the reply but the computer doesn't see it. Wireshark could help figure out which it is.
So it's after playing around with windows that everything stopped working. Are you using BIOS or EFI? Can you reset the BIOS/EFI variables?

That's what I did, I'll give as much info as I can so maybe they are irrelevant :

1) internet works

/dev/sda -> arch (/boot and /)
/dev/sdb -> nothing
/dev/sdc -> /home
/dev/sdd -> /mnt/data

2) no idea about internet on arch
I installed windows 10 on /dev/sdb. At first, I could not install it because Windows wants to be installed on the first hard drive so I had to unlink /dev/sda from the motherboard, boot the windows DVD and install it on the hard drive /dev/sdb, then link again /dev/sda.

Obviously, I couldn't boot on Arch anymore as I needed to fix grub but I didn't do that for like 2 or 3 weeks maybe. I played some online video game during this time.

3) internet does not work
I wanted to do a few things on arch so I decided to fix the grub, I booted the livecd, installed os-prober (don't know if it was installed from the live cd or with internet) and install grub on /dev/sdb.
I could then boot on arch and that's when I saw that I had no internet anymore.

----------

I think I installed arch using EFI, I will need to check that tonight. Should I just run this "efivar -l" ? I also need to find how to reset EFI vars if I am using EFI, it is probably in the documentation so I'll do that tonight too.

Arch Linux

#1 2016-06-23 20:26:14

[SOLVED]No network, no ipv4 when executing ip addr

#2 2016-06-24 14:47:38

Re: [SOLVED]No network, no ipv4 when executing ip addr

#3 2016-06-24 15:01:46

Re: [SOLVED]No network, no ipv4 when executing ip addr

#4 2016-06-24 15:07:31

Re: [SOLVED]No network, no ipv4 when executing ip addr

#5 2016-06-24 17:02:07

Re: [SOLVED]No network, no ipv4 when executing ip addr

#6 2016-06-24 17:07:13

Re: [SOLVED]No network, no ipv4 when executing ip addr

#7 2016-06-24 17:10:57

Re: [SOLVED]No network, no ipv4 when executing ip addr

#8 2016-06-24 17:12:46

Re: [SOLVED]No network, no ipv4 when executing ip addr

#9 2016-06-24 17:14:15

Re: [SOLVED]No network, no ipv4 when executing ip addr

#10 2016-06-25 16:27:38

Re: [SOLVED]No network, no ipv4 when executing ip addr

#11 2016-06-25 17:32:18

Re: [SOLVED]No network, no ipv4 when executing ip addr

#12 2016-06-26 09:00:54

Re: [SOLVED]No network, no ipv4 when executing ip addr

#13 2016-06-26 13:41:29

Re: [SOLVED]No network, no ipv4 when executing ip addr

#14 2016-06-27 17:20:53

Re: [SOLVED]No network, no ipv4 when executing ip addr

#15 2016-06-27 21:12:45

Re: [SOLVED]No network, no ipv4 when executing ip addr

#16 2016-06-28 05:15:29

Re: [SOLVED]No network, no ipv4 when executing ip addr

#17 2016-06-28 17:43:16

Re: [SOLVED]No network, no ipv4 when executing ip addr

#18 2016-06-28 19:16:20

Re: [SOLVED]No network, no ipv4 when executing ip addr

#19 2016-06-28 19:55:18

Re: [SOLVED]No network, no ipv4 when executing ip addr

#20 2016-06-28 21:45:36

Re: [SOLVED]No network, no ipv4 when executing ip addr

#21 2016-06-29 04:59:52

Re: [SOLVED]No network, no ipv4 when executing ip addr

#22 2016-06-29 08:38:48

Re: [SOLVED]No network, no ipv4 when executing ip addr

#23 2016-06-29 09:52:02

Re: [SOLVED]No network, no ipv4 when executing ip addr

#24 2016-06-29 12:14:55

Re: [SOLVED]No network, no ipv4 when executing ip addr

#25 2016-06-29 12:57:55

Re: [SOLVED]No network, no ipv4 when executing ip addr

Board footer