I recently switched my virtual private server hehoe.de from Ubuntu to Arch Linux. I am struggling trying to regain IPv6 connectivity. Access via IPv4 is working fine, so the hardware is okay. The server provider instructs me to use 2a00:5080:1:199::1/128 for the server's IPv6 address and fe80::1 as the gateway. They gave me a configuration file to use with netctl for IPv4 connectivity. I added the IPv6 sections: Description='A basic static ethernet connection' Interface=enX0 Connection=ethernet IP=static Address=('84.38.64.200/32') Routes=('172.16.147.1/32 dev eth0') Gateway='172.16.147.1' IP6=static Address6=('2a00:5080:1:199::1') Gateway6='fe80::1' After enabling and starting the profile, the command ip addr list shows this: enX0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:16:3e:4f:7f:20 brd ff:ff:ff:ff:ff:ff inet 84.38.64.200/32 scope global enX0 valid_lft forever preferred_lft forever inet6 2a00:5080:1:199::1/128 scope global valid_lft forever preferred_lft forever inet6 fe80::216:3eff:fe4f:7f20/64 scope link valid_lft forever preferred_lft forever It makes me think the addresses are set-up correctly. The command ip -6 route shows this: 2a00:5080:1:199::1 dev enX0 proto kernel metric 256 pref medium fe80::/64 dev enX0 proto kernel metric 256 pref medium default via fe80::1 dev enX0 metric 1024 pref medium The routes are looking fine to me, too. I can ping -6 fe80::1%enX0 so there is some machine there. Running mtr -6 google.com on the server only shows an empty table. That made me think the gateway is not being considered at all. Observing the ping attempts with tcpdump -e -n -i enX0 "ip6": 18:44:45.981952 00:16:3e:4f:7f:20 > fe:ff:ff:ff:ff:ff, ethertype IPv6 (0x86dd), length 118: 2a00:5080:1:199::1 > 2a00:1450:4001:81c::2003: ICMP6, echo request, id 8, seq 3, length 64 Where 2a00:1450:4001:81c::2003 is the google server I tried to ping. ip neigh shows: 172.16.147.1 dev enX0 lladdr fe:ff:ff:ff:ff:ff REACHABLE fe80::1 dev enX0 lladdr fe:ff:ff:ff:ff:ff router STALE So fe:ff:ff:ff:ff:ff is indeed the router's MAC address. Any ideas how to debug this issue?

I've recently moved to a place with public WiFi (so I don't have access to the router or their DHCP config), and am running into issues connecting with my Arch laptop. I've tried using both NetworkManager and netctl to connect, but both fail at getting a DHCP lease. It should be noted that every other device (Android and iOS phones, Windows and macOS laptops) does so without problems. How do I go about debugging this? Am I missing a package, or am I connecting wrongly? --- ### NetworkManager I use nmcli to connect: $ nmcli dev wifi * SSID MODE CHAN RATE SIGNAL BARS SECURITY ssidOfWifi Infra 1 54 Mbit/s 52 ▂▄__ WPA2 ssidOfWifi Infra 13 54 Mbit/s 34 ▂▄__ WPA2 ssidOfWifi Infra 13 54 Mbit/s 22 ▂___ WPA2 $ nmcli dev wifi connect ssidOfWifi password passwordToWifi Error: Connection activation failed: (5) IP configuration could not be reserved (no available address, timeout, etc.). $ systemctl status NetworkManager ... Jan 09 17:49:43 home NetworkManager: [1483980583.9385] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'ssidOfWifi'. Jan 09 17:49:43 home NetworkManager: [1483980583.9386] device (wlp2s0): state change: config -> ip-config (reason 'none') [50 70 0] Jan 09 17:49:43 home NetworkManager: [1483980583.9390] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) Jan 09 17:50:29 home NetworkManager: [1483980629.0055] dhcp4 (wlp2s0): state changed unknown -> timeout Jan 09 17:50:29 home NetworkManager: [1483980629.0214] dhcp4 (wlp2s0): canceled DHCP transaction Jan 09 17:50:29 home NetworkManager: [1483980629.0215] dhcp4 (wlp2s0): state changed timeout -> done Jan 09 17:50:29 home NetworkManager: [1483980629.0220] device (wlp2s0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Jan 09 17:50:29 home NetworkManager: [1483980629.0223] manager: NetworkManager state is now DISCONNECTED Jan 09 17:50:29 home NetworkManager: [1483980629.0233] device (wlp2s0): Activation: failed for connection 'ssidOfWifi' Jan 09 17:50:29 home NetworkManager: [1483980629.0319] device (wlp2s0): state change: failed -> disconnected (reason 'none') [120 30 0] Jan 09 17:50:29 home NetworkManager: [1483980629.0421] device (wlp2s0): set-hw-addr: set MAC address to AA:BB:CC:DD:EE:FF (scanning) Jan 09 17:50:29 home NetworkManager: [1483980629.0453] sup-iface[0x1d5ec00,wlp2s0]: connection disconnected (reason -3) Jan 09 17:50:29 home NetworkManager: [1483980629.0454] device (wlp2s0): supplicant interface state: completed -> disconnected ### Netctl I use wifi-menu -o to connect. This shows only one "ssidOfWifi", unlike nmcli which shows one for each accesspoint. $ sudo wifi-menu -o Job for netctl@wlp2s0\x2dssidOfWifi.service failed because the control process exited with error code. See "systemctl status "netctl@wlp2s0\\x2dssidOfNetwork.service"" and "journalctl -xe" for details. $ journalctl -xe ... Jan 09 23:10:34 home dhcpcd: wlp2s0: soliciting a DHCP lease Jan 09 23:11:03 home dhcpcd: timed out Jan 09 23:11:03 home dhcpcd: dhcpcd exited Jan 09 23:11:03 home network: DHCP IPv4 lease attempt failed on interface 'wlp2s0' Jan 09 23:11:03 home kernel: wlp2s0: deauthenticating from AA:BB:CC:DD:EE:FF by local choice (Reason: 3=DEAUTH_LEAVING) Jan 09 23:11:03 home network: Failed to bring the network up for profile 'wlp2s0-ssidOfWifi' Jan 09 23:11:03 home systemd: netctl@wlp2s0\x2dssidOfWifi.service: Main process exited, code=exited, status=1/FAILURE

I've got a standard router (192.168.1.1) that is connected to the internet. It also has the following connected to it: - an un-managed switch which all wired devices connect to. - a Tenda Mesh WiFi Router (192.168.1.9 >> 192.168.5.1) connected to it. Devices connected to the Tenda have IPs of 192.168.5.x and I can't connect to them from devices connected to the main router. UPDATE: I've seen some posts referencing 'Routes' within netctl, but I get: Jan 14 22:56:00 deviceX network: Could not add route '192.168.5.0/24 via 192.168.1.9,' to interface 'eno1' Jan 14 22:56:00 deviceX dhclient: receive_packet failed on eno1: Network is down Jan 14 22:56:00 deviceX network: Failed to bring the network up for profile 'mynet-eno1-dhcp' My current netctl profile is: Description='A basic dhcp ethernet connection' Interface=eno1 Connection=ethernet IP=dhcp #Routes=('192.168.5.0/24 via 192.168.1.9', '192.168.1.0/24 via 192.168.1.1') DHCPClient=dhclient #DHCPReleaseOnStop=no ## for DHCPv6 IP6=dhcp DHCP6Client=dhclient ## for IPv6 autoconfiguration #IP6=stateless In order to connect seamlessly between these two networks, how (and where) can I create a Static Route. Also, do I need to do this on multiple machines. My computers are all running Arch Linux, including several Raspberry Pis which are always on, that could server as intermediate points, if that would work.

Would you please tell me, is it possible to encrypt the identity and password values in a netctl profile configuration file? This profile sets up a connection to a WPA2 Enterprise wireless network. Would you please instruct me on how to encrypt the plain text values, if it is possible? My current netctl profile configuration file is: Description='WiFi' Interface=wlan0 Connection=wireless Security=wpa-configsection IP=dhcp WPAConfigSection=( 'ssid="ssid"' 'proto=WPA RSN' 'key_mgmt=WPA-EAP' 'pairwise=CCMP' 'group=CCMP' 'eap=PEAP' 'anonymous_identity="anonymous@domain.name"' 'identity="USERNAME"' 'password="PASSWORD"' 'ca_cert="/path/to/cert.pem"' 'phase2="auth=MSCHAPV2"' 'priority=1' ) USERNAME and PASSWORD in an example above are plain text values. I know it is possible to [obfuscate the wireless passphrase](https://wiki.archlinux.org/title/Netctl#Obfuscate_wireless_passphrase) when using WPA2-PSK. I'm looking for a similar functionality for WPA2 Enterprise.

I have the bare minimum Arch Linux install with a wired connection. I can’t seem to obtain an IP address with netctl. I created an eth0 profile with ethernet-dhcp. I tried to start the profile but the control process exited with error code. When I look at the status of netctl it says it exited with error code. I can restart netctl but it still has the same error. What can I do to figure out why I can’t get an IP with netctl?

I am new to Linux. I am working on a speed up boot-time project. I am using Arch Linux on raspberry pi B+. I am particularly looking into netctl service. To trace down function time, I have edited some of scripts in /usr/lib/network. and I got to know that, it's slow hardware(?) and also stuck up in resolv.conf as it can't find /etc/resolv.conf. [ 17.174115] alarmpi network: Starting network profile 'ethernet-static'... [ 17.190230] alarmpi network: start connection up {network} [ 17.208285] alarmpi network: inside ethernet up [ 17.208285] alarmpi network: test for bring interface up [ 17.443234] alarmpi network: inside bring interface up{network} [ 17.455252] alarmpi network: connection slow or cable is not connectedP{ethernet connection} [ 19.038800] alarmpi network: wait over for carrier whose connection is low or cable not connected {ethernet connection} [ 19.056395] alarmpi network: set ip in IP lib [ 19.056395] alarmpi network: inside ip set {ip} [ 19.112173] alarmpi network: adding static IP routs {set_ip} [ 19.122707] alarmpi network: adding custome gateway {set_ip} [ 19.174517] alarmpi network: start resolvconf [ 21.425880] alarmpi network: /usr/lib/resolvconf/libc: line 230: /etc/resolv.conf: No such file or directory [ 21.901427] alarmpi network: end resolvconf [ 21.913711] alarmpi network: end of IP set [ 21.913711] alarmpi network: set ip function finish P{ethernet connection} [ 21.941763] alarmpi network: Started network profile 'ethernet-static' code snippet for slow hardware(?) is given below. if is_yes "${SkipNoCarrier:-no}"; then SkipDAD=yes else # Some cards are plain slow to come up. Don't fail immediately. if ! timeout_wait "${TimeoutCarrier:-5}" '(( $(< "/sys/class/net/$Interface/carrier") ))'; then report_error "No connection found on interface '$Interface' (timeout)" bring_interface_down "$Interface" return 1 fi fi this is my ethernet profile Description='A basic static ethernet connection' Interface=eth0 Connection=ethernet IP=static Address=('10.152.187.5/24') #Routes=('192.168.0.0/24 via 192.168.1.2') Gateway='0.0.0.0' DNS=('10.152.187.5') #ForceConnect=yes NETCTL_DEBUG=no TimeoutCarrier=2 ## For IPv6 autoconfiguration #IP6=stateless ## For IPv6 static address configuration #IP6=static #Address6=('1234:5678:9abc:def::1/64' '1234:3456::123/96') #Routes6=('abcd::1234') #Gateway6='1234:0:123::abcd' I am using static connection and I have disabled DHCP service and, as of now, I am not interested in IPv6. What could be the solution to speed up boot time? Should I switch to systemd-networkd service?

~ $ echo $EDITOR /usr/bin/kak ~ $ sudo echo $EDITOR /usr/bin/kak ~ $ su Password: /home/myusername $ echo $EDITOR /usr/bin/kak /home/myusername $ cat ~/.profile # nvim editor config # export EDITOR='/usr/bin/nvim' # kakoune editor config export EDITOR='/usr/bin/kak' export PAGER=$HOME/.bin/kakpager export MANPAGER=$HOME/.bin/kakmanpager /home/myusername cat ~/.zshenv # nvim editor config # export EDITOR='/usr/bin/nvim' # kakoune editor config export EDITOR='/usr/bin/kak' export PAGER=$HOME/.bin/kakpager export MANPAGER=$HOME/.bin/kakmanpager ... /home/myusername $ but it still nano

So I can't connect via: ___ * nmtui just asking me to try again endlessly ___ * kde ui no secrets were provided ___ * iwd station wlan0 connect SSID (I enter password and get no output) If I try this command again - I receive no output (even iwd not asking me for password) (and network ofk doesn't connect) ___ * `wpa_supplicant -i wlan0 -c Apr 16 08:22:18 archbtrfs systemd: netctl@wireless\x2dwpa.service: Failed with result 'exit-code'. Apr 16 08:22:18 archbtrfs systemd: Failed to start Networking for netctl profile wireless-wpa.

journalctl -xeu "netctl@wireless\\x2dwpa.service":

Apr 16 08:22:18 archbtrfs systemd: Starting Networking for netctl profile wireless-wpa... ░░ Subject: A start job for unit netctl@wireless\x2dwpa.service has begun execution ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit netctl@wireless\x2dwpa.service has begun execution. ░░ ░░ The job identifier is 1594. Apr 16 08:22:18 archbtrfs network: Profile 'wireless-wpa' does not exist or is not readable Apr 16 08:22:18 archbtrfs systemd: netctl@wireless\x2dwpa.service: Main process exited, code=exited, status=1/FA> ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ An ExecStart= process belonging to unit netctl@wireless\x2dwpa.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Apr 16 08:22:18 archbtrfs systemd: netctl@wireless\x2dwpa.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ The unit netctl@wireless\x2dwpa.service has entered the 'failed' state with result 'exit-code'. Apr 16 08:22:18 archbtrfs systemd: Failed to start Networking for netctl profile wireless-wpa. ░░ Subject: A start job for unit netctl@wireless\x2dwpa.service has failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit netctl@wireless\x2dwpa.service has finished with a failure. ░░ ░░ The job identifier is 1594 and the job result is failed. lines 1-3 ``` ___ Driver for wifi installed from here: https://github.com/bserem/Realtek-RTL8822x-Linux P.S. ssid is broadcasting and I can see it detected

I am using netctl in Arch Linux on Hyper-V. I have two ethernet interfaces eth0 & eth1. IP config: 1. eth0: dhcp (automatic configuration, no involvment of netctl) 2. eth1: static ip (10.10.10.1/8) using netctl profile 3. dhcpcd installed and enabled at startup 4. NetworkManager installed and enabled at startup eth1 netctl profile (/etc/netctl/sth1static):

Description='Static IP config for eth1'
Interface=eth1
Connection=ethernet
IP=static
Address=('10.10.10.1/8')
Gateway='10.10.10.2'
DNS=('10.10.10.2')

To start the interface I am doing as follows:

netctl stop eth1static
ip link set eth1 down
netctl start eth1static
netctl enable eth1static

After following the above steps, I am able to see the static IP configuration applied to the interface using ip a. Also I am able to ping the guest interface from my host OS successfully. However after a minute or so, I see the interface lose its configuration and get a fe80: based IPv6 address only and the ping stops working... Even after reboot, I don't see the IP configurtion on the interface, where as the other interface (eth0) is working fine. Could anyone suggest what's going wrong and how to fix it?

My machine has multiple static IP addresses on the ethernet interface, which are configured with netctl. The configuration file of netctl looks like:

Description='A basic static ethernet connection'
Interface=ens0
Connection=ethernet
IP=static
Address=('6.6.200.5/32' '6.6.100.23/22')
Gateway='6.6.6.1'
DNS=('1.1.1.1')

I would like to make 6.6.200.5/32 the default source IP address for outgoing packets. But the route table always has 6.6.100.23/22 be the default. Then, I have to run

ip route change default via 6.6.6.1 src 6.6.200.5 dev ens0

manually to override it everytime after booting. My question is: it is possible to specify the default source address in the configuration file of netctl?

After a recent Arch Linux update, my ethernet interface somehow got renamed from enp4s0 to enp5s0, as shown by ip link. After correcting this in my profile /etc/netctl/dhcp, and starting sudo netctl dhcp, nothing happens for around 30 seconds and then I get "A dependency job for netctl@dhcp.service failed. See 'journalctl -xe' for details.", which I do and get: [...]systemd: Timed out waiting for device sys-subsystem-net-devices-enp4s0.device. So it seems, netctl ignores my changes to my profile and still tries to use enp4s0. Or maybe the old name is cached somewhere in my system? How can I fix this?

I use a linux host as an IPv4 router and looked into enabling IPv6 (it's the future, I'm told). I already use dhcpcd as a dhcpv4 client to get an address from my ISP, so I figured I'd use it for dhcpv6 as well. Unfortunately, although I can see dhcpcd send a solicit message and I can see the dhcpv6 server respond with 2x dhcpv6 advertise messages, I don't see dhcpcd send a dhcpv6 request. I see the following sequence of three messages repeat 3x times and then dhcpcd times out:

15:41:06.457440 IP6 (flowlabel 0x1e0d7, hlim 1, next-header UDP (17) payload length: 152) fe80::aaaa:aaaa:aaaa:aaaa.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 solicit (xid=bc3d12 (client-ID type 4) (elapsed-time 0) (vendor-class) (rapid-commit) (IA_NA IAID:403318227 T1:0 T2:0) (Client-FQDN) (reconfigure-accept) (option-request DNS-server DNS-search-list Client-FQDN opt_82 opt_83))

15:41:07.168805 IP6 (class 0x48, hlim 56, next-header UDP (17) payload length: 140) 2001:558:4082:7f::1.dhcpv6-server > fe80::aaaa:aaaa:aaaa:aaaa.dhcpv6-client: [udp sum ok] dhcp6 advertise (xid=bc3d12 (client-ID type 4) (server-ID hwaddr/time type 1 time 493924036 40a8f0347664) (IA_NA IAID:403318227 T1:1800 T2:2880 (IA_ADDR 2001:558:600a:7f:bbbb:bbbb:bbbb:bbbb pltime:3600 vltime:3600)) (reconfigure-accept) (DNS-server cdns01.comcast.net cdns02.comcast.net) (Client-FQDN))

15:41:07.168912 IP6 (class 0x48, hlim 56, next-header UDP (17) payload length: 140) 2001:558:4082:7f::1.dhcpv6-server > fe80::aaaa:aaaa:aaaa:aaaa.dhcpv6-client: [udp sum ok] dhcp6 advertise (xid=bc3d12 (client-ID type 4) (server-ID hwaddr/time type 1 time 493924036 40a8f0347664) (IA_NA IAID:403318227 T1:1800 T2:2880 (IA_ADDR 2001:558:600a:7f:bbbb:bbbb:bbbb:bbbb pltime:3600 vltime:3600)) (reconfigure-accept) (DNS-server cdns01.comcast.net cdns02.comcast.net) (Client-FQDN))

Mar 14 15:41:05 router dhcpcd: DUID ...
Mar 14 15:41:05 router dhcpcd: enp8s0: IAID 18:0a:25:d3
Mar 14 15:41:05 router dhcpcd: enp8s0: adding address fe80::aaaa:aaaa:aaaa:aaaa
Mar 14 15:41:05 router dhcpcd: enp8s0: soliciting an IPv6 router
Mar 14 15:41:06 router dhcpcd: enp8s0: Router Advertisement from fe80::2aa:bbff:fecc:102
Mar 14 15:41:06 router dhcpcd: enp8s0: no global addresses for default route
Mar 14 15:41:06 router dhcpcd: enp8s0: soliciting a DHCPv6 lease
Mar 14 15:41:35 router dhcpcd: timed out
Mar 14 15:41:35 router dhcpcd: dhcpcd exited

$ cat /proc/sys/net/ipv6/conf/enp8s0/autoconf
1
$ cat /proc/sys/net/ipv6/conf/enp8s0/accept_ra_pinfo
1
$ cat /proc/sys/net/ipv6/conf/enp8s0/forwarding 
0
$ cat /proc/sys/net/ipv6/conf/enp8s0/accept_ra
0

My immediate goal is to get IPv6 working on this "router" host without doing prefix delegation or any actual IPv6 routing, so forwarding is set to 0 for now. After this host is working as a IPv6 client, then I'll tackle routing. I've tried setting accept_ra to 2, but dhcpcd sets it back to 0. I am invoking dhcpcd via netctl with the following very basic profile. The exact invocation is dhcpcd -6 -q -t 30 enp8s0:

$ cat /etc/netctl/enp8s0 
Interface=enp8s0
Connection=ethernet
IP=dhcp
DHCPClient=dhcpcd
IP6=dhcp
DHCP6Client=dhcpcd

$ dhcpcd --version
dhcpcd 8.1.6
Copyright (c) 2006-2019 Roy Marples
Compiled in features: INET ARP ARPing IPv4LL INET6 DHCPv6 AUTH

$ cat /etc/dhcpcd.conf  | egrep -v '^#'


hostname

duid

persistent

option rapid_commit

option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
option interface_mtu


require dhcp_server_identifier

slaac private
noipv4ll

I wanted to setup wifi on my arch linux machine with

-menu

But it doesn't connect to wifi. It shows no error and it says, that im connected to the internet. But with

8.8.8.8

I get

is unreachable

. Am i missing packets or firmware for my wifi card? btw my wifi card driver is

-pci

. Can someone help?

After installing arch, I wanted to set up wifi. I typed

-menu wlp3s0

and selected my network. After that wifi-menu exited with no error. I typed

- c3 google.com

to verify my internet connection. I got

: google.com: Temporary failure in name resolution

I typed

-menu wlp3s0

again and in front of my wireless network is a

:

(handmade profile present). But i want

*

(active connection present). Can someone help me?

The network topology is as simple as it gets: After some correspondence my ISP flipped some switch to enable the router to get what the router calls a "Default IPv6 Gateway." My Ethernet-connected PC can now use IPv6 without issue: $ ping -q -c 1 ipv6.google.com PING ipv6.google.com(syd15s01-in-x0e.1e100.net (2404:6800:4006:806::200e)) 56 data bytes --- ipv6.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 45.496/45.496/45.496/0.000 ms The laptop, running the same software on the same distro (Arch Linux), is able to connect to IPv4 hosts but not IPv6 ones: $ ping -q -c 1 ipv6.google.com connect: Network is unreachable When asking my ISP about this they responded > Do you have IPv6 configured on the wireless adapter in the computer? How can I tell? The closest I can think if is that the laptop seems to have assigned an internal IP to the network interface: $ ip address show dev wlp1s0 2: wlp1s0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 54:8c:a0:52:3e:a1 brd ff:ff:ff:ff:ff:ff inet 192.168.1.6/24 brd 192.168.1.255 scope global noprefixroute wlp1s0 valid_lft forever preferred_lft forever inet6 fe80::f0ac:8fe:bb0d:619a/64 scope link valid_lft forever preferred_lft forever --- My laptop does not have an Ethernet plug, so I can't check whether it would receive an IPv6 address via Ethernet. --- The closest page I can think of in the router configuration is this: --- I've been in touch further with my ISP, and they maintain that with the current settings it *should* just work. **I just connected to the wireless network with my desktop PC and can confirm that it does indeed receive a DHCPv6 lease.** --- Both machines have identical /etc/dhcpcd.conf and /etc/netconfig files (confirmed using diff -u <(ssh laptop cat /etc/…) /etc/…). Even so, when connecting to Wi-Fi the dhcpcd log is very different. On my PC: $ journalctl --follow --output=cat --unit=dhcpcd | grep ^eno1 eno1: rebinding lease of 192.168.1.2 eno1: leased 192.168.1.2 for 86400 seconds eno1: adding route to 192.168.1.0/24 eno1: adding default route via 192.168.1.1 eno1: soliciting an IPv6 router eno1: Router Advertisement from xxxx::xxxx:xxxx:xxxx:xxxx eno1: adding address xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 eno1: adding route to xxxx:xxxx:xxxx:xxxx::/64 eno1: adding default route via xxxx::xxxx:xxxx:xxxx:xxxx eno1: soliciting a DHCPv6 lease On the laptop: $ journalctl --follow --output=cat --unit=dhcpcd | grep ^wlp1s0 wlp1s0: rebinding lease of 192.168.1.6 wlp1s0: leased 192.168.1.6 for 86400 seconds wlp1s0: adding route to 192.168.1.0/24 wlp1s0: adding default route via 192.168.1.1 wlp1s0: soliciting an IPv6 router wlp1s0: no IPv6 Routers available --- Their Wi-Fi connection configuration is also identical except for the interface name: Description='Automatically generated profile by wifi-menu' Interface=wlo1 Connection=wireless Security=wpa ESSID=… IP=dhcp Key=… --- Wireshark reports that the laptop does indeed receive an ICMPv6 router advertisement from the correct MAC address, supporting the idea that the problem is with the laptop not handling the router advertisement. --- Diffing the IP tables of the two machines seems to have given a clue: There are some rules left over since a UFW installation years ago on my laptop. Diffing the IP tables of the two machines shows this: $ comm -23 <(ssh laptop cat iptable.txt) iptable.txt -P INPUT DROP -P FORWARD DROP -N ufw-after-forward -N ufw-after-input -N ufw-after-logging-forward -N ufw-after-logging-input -N ufw-after-logging-output -N ufw-after-output -N ufw-before-forward -N ufw-before-input -N ufw-before-logging-forward -N ufw-before-logging-input -N ufw-before-logging-output -N ufw-before-output -N ufw-logging-allow -N ufw-logging-deny -N ufw-not-local -N ufw-reject-forward -N ufw-reject-input -N ufw-reject-output -N ufw-skip-to-policy-forward -N ufw-skip-to-policy-input -N ufw-skip-to-policy-output -N ufw-track-forward -N ufw-track-input -N ufw-track-output -N ufw-user-forward -N ufw-user-input -N ufw-user-limit -N ufw-user-limit-accept -N ufw-user-logging-forward -N ufw-user-logging-input -N ufw-user-logging-output -N ufw-user-output … I guess the -P INPUT DROP could be responsible for this issue? IPv6 tables show similar differences: -P INPUT DROP -P FORWARD DROP -N ufw6-after-forward -N ufw6-after-input -N ufw6-after-logging-forward -N ufw6-after-logging-input -N ufw6-after-logging-output -N ufw6-after-output -N ufw6-before-forward -N ufw6-before-input -N ufw6-before-logging-forward -N ufw6-before-logging-input -N ufw6-before-logging-output -N ufw6-before-output -N ufw6-logging-allow -N ufw6-logging-deny -N ufw6-reject-forward -N ufw6-reject-input -N ufw6-reject-output -N ufw6-skip-to-policy-forward -N ufw6-skip-to-policy-input -N ufw6-skip-to-policy-output -N ufw6-track-forward -N ufw6-track-input -N ufw6-track-output -N ufw6-user-forward -N ufw6-user-input -N ufw6-user-limit -N ufw6-user-limit-accept -N ufw6-user-logging-forward -N ufw6-user-logging-input -N ufw6-user-logging-output -N ufw6-user-output

I've got a device that is connected to one network via ethernet and a different network via wifi. I use netctl to manage the interfaces. When both netctl profiles are active, the configuration looks like this: $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether b8:27:eb:eb:ab:dc brd ff:ff:ff:ff:ff:ff inet 192.168.1.200/21 brd 192.168.7.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::ba27:ebff:feeb:abdc/64 scope link valid_lft forever preferred_lft forever 3: wlan0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether b8:27:eb:be:fe:89 brd ff:ff:ff:ff:ff:ff inet 10.10.0.89/23 brd 10.10.1.255 scope global noprefixroute wlan0 valid_lft forever preferred_lft forever inet6 fe80::ba27:ebff:febe:fe89/64 scope link valid_lft forever preferred_lft forever $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 0.0.0.0 10.10.0.1 0.0.0.0 UG 303 0 0 wlan0 10.10.0.0 0.0.0.0 255.255.254.0 U 303 0 0 wlan0 192.168.0.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0 What I have noticed is that, when both netctl profiles are active, I can successfully ping a host (google.com) when I specify the ethernet interface, but pings fail when I specify the wifi interface: $ ping -c4 -Ieth0 google.com PING google.com (74.125.136.100) from 192.168.1.200 eth0: 56(84) bytes of data. 64 bytes from 74.125.136.100 (74.125.136.100): icmp_seq=1 ttl=44 time=21.4 ms 64 bytes from 74.125.136.100 (74.125.136.100): icmp_seq=2 ttl=44 time=21.3 ms 64 bytes from 74.125.136.100 (74.125.136.100): icmp_seq=3 ttl=44 time=21.10 ms 64 bytes from 74.125.136.100 (74.125.136.100): icmp_seq=4 ttl=44 time=37.1 ms --- google.com ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 7ms rtt min/avg/max/mdev = 21.317/25.440/37.086/6.729 ms $ ping -c4 -Iwlan0 google.com PING google.com (74.125.136.138) from 10.10.0.89 wlan0: 56(84) bytes of data. --- google.com ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 154ms When I saw this behavior, I tried pulling out the ethernet cable, after which I still couldn't ping using wlan0, and I noticed that eth0 kept its IP address, gateway, etc. The only thing that changed was that it reported state DOWN rather than state UP. I then ran netctl stop my-ethernet-profile to *actually* stop the profile for real, after which I *could* successfully ping from wlan0. So, ICMP isn't blocked on wlan0... everything seems fine when eth0's profile is actually stopped, just not when it's running (regardless of whether the interface is UP or DOWN). So, I'm trying to understand a couple things: 1. Why would the wifi ping fail when both devices are connected (or, more accurately, when both netctl profiles are active)? 2. Why does the ethernet interface keep its configuration even if the system recognizes that it is not connected? 3. Is there a way to configure netctl to stop the profile if the interface goes down? 4. Is there a way to run an arbitrary script when the state transitions from UP to DOWN? For example, if I need to run netctl stop my-ethernet-profile when the cable becomes disconnected? As a final note, I know that there are ways to do a bonded interface or wifi failover, but this is for a very purpose-built situation. It may sound like I'm reinventing the wheel here, but there is a good reason.

I'm trying to build a script that _auto connects_ to a given network (providing ESSID and Passphrase) and I want to store them, so when ever it's not connected, It searches for the given network, connects. The problem is that I know there is like a _de facto_ uniform way of saving the known networks as _Network Manager_ does, but I can't find it explicitly. I want to save any kind of network and the script will determine the method of connection (if wpa_supplicant or iw-tools, should I use netctl) So the question is: Where can I find this documentation? or What would be the best way to do it (System or User level)? Or if there is a tool that allows me to connect to any network with approximately the same procedure? I'm using _Arch_ <- This is a Meme But I'm interested on this script working also with FreeBSD.

I can't connect to a WiFi network. I tried various methods such as wpa_supplicant and wicd. At the moment I'm trying netctl. When I enter the command: systemctl --type=service I see the following errors: **netctl start wireless-home** Job for netctl@wireless\x2dhome.service failed. See 'systemctl status netctl@wireless\x2dhome.service' and 'journalctl -xn' for details. This is the profile file for wireless-home: Description='A simple WPA encrypted wireless connection' Interface=wlan0 Connection=wireless Security=wpa IP=dhcp ESSID='Pruthenia 3.OG' Key='XXXXXXXXXX' **systemctl status netctl@wireless\x2dhome.service** netctl@wirelessx2dhome.service - Networking for netctl profile wirelessx2dhome Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static) Active: inactive (dead) Docs: man:netctl.profile(5) **journalctl -xn output -->** Dec 12 08:01:01 webcampi CROND: pam_unix(crond:session): session closed for user root Dec 12 09:01:01 webcampi crond: pam_unix(crond:session): session opened for user root by (uid=0) Dec 12 09:01:01 webcampi CROND: (root) CMD (run-parts /etc/cron.hourly) Dec 12 09:01:01 webcampi CROND: pam_unix(crond:session): session closed for user root Dec 12 10:01:01 webcampi crond: pam_unix(crond:session): session opened for user root by (uid=0) Dec 12 10:01:01 webcampi CROND: (root) CMD (run-parts /etc/cron.hourly) Dec 12 10:01:01 webcampi CROND: pam_unix(crond:session): session closed for user root Dec 12 11:01:01 webcampi crond: pam_unix(crond:session): session opened for user root by (uid=0) Dec 12 11:01:01 webcampi CROND: (root) CMD (run-parts /etc/cron.hourly) Dec 12 11:01:01 webcampi CROND: pam_unix(crond:session): session closed for user root How can I fix this?

TL;DR: How can I connect to a VPN with IPSec without writing the password and secret in the config file, but providing it from the outside (in my case a call to my password manager pass)? I already use a combination of netctl, pass, and openconnect to connect to a non-IPSec vpn at work. My netctl profile looks basically like this razr@notebook [~] -> % cat /etc/netctl/my-vpn Description='myVPN' Interface=vpn Connection=tuntap Mode=tun BindsToInterfaces=(tun0) IP=no PIDFILE=/run/openconnect_${Interface}.pid SERVER=my.server.com LOCAL_USERNAME=razr PASS_PATH=com/myserver/razr REMOTE_USERNAME=razr ExecUpPost="echo 'su ${LOCAL_USERNAME} -c "DISPLAY=:0 pass ${PASS_PATH}" | head -n 1' | /usr/bin/openconnect --background --pid-file=${PIDFILE} --interface ${Interface} --user='${REMOTE_USERNAME}' --passwd-on-stdin ${SERVER} ; chmod 644 ${PIDFILE}" ExecDownPre="kill -INT $(cat ${PIDFILE}) ; resolvconf -d ${Interface} ; ip link delete ${Interface}" razr@notebook [~] -> % So when I start the profile my-vpn, pass is invoked to get the password at com/myserver/razr and therefore I am asked to unlock my pgp key (that's why there is the DISPLAY:=0; not ideal yet, I know :)). Now I want to connect to a IPSec VPN. And it seems, that openconnect is not IPSec compatible (please correct me if I'm wrong). So I tried to use vpnc for it. I could already connect in my first tests with a completely filled config file. But I don't want to have my password (and maybe also not the IPSec secret) saved in the configuration file but in pass. So, is it possible to provide the password and secret from the outside in a vpnc config? Or is there maybe another tool to do this, that I can integrate in a netctl profile?

I've recently installed Arch and had some issues with Wired/Wireless, eventually got this fixed, but have a rogue device trying to load on boot: A start job is running for sys-subsystem-net-devices-wlp0s20u3.device, counts up thru 90 secs, then fails. This was created when I plugged in a WiFi dongle to get connectivity whilst installing/configuring, it is no longer in use. I've tried: systemctl disable sys-subsystem-net-devices-wlp0s20u3.device Failed to disable unit: Unit file sys-subsystem-net-devices-wlp0s20u3.device does not exist. netctl disable sys-subsystem-net-devices-wlp0s20u3 No regular unit file found for profile 'sys-subsystem-net-devices-wlp0s20u3' . systemctl reset-failed results in no output, and changes nothing. If I list similar units: systemctl list-units --all | grep subsystem sys-subsystem-net-devices-eno1.device loaded active plugged Ethernet Connection I217-V sys-subsystem-net-devices-wlp0s20u3.device loaded inactive dead sys-subsystem-net-devices-wlp0s20u3.device How can I get rid of this from attempting to load