VLAN and DHCP

liochan · 2014-07-31 13:00:05

Hello,

I try to connect to a network which is a vlan with dhcp. I have the same effects when I use both wireless or ethernet. If I use a netctl profile with static ip, I am connected.

Description='A basic static ethernet connection'
Interface=wlp3s0
Connection=wireless
Security=wpa
ESSID=CoWorking_Montpellier
Key=blahblah
IP=static
Address=('192.168.10.19/24')
#Routes=('192.168.0.0/24 via 192.168.1.1')
Gateway='192.168.10.1'
DNS=('192.168.10.1')

If I remove static information to use dhcp, I can't connect. After authenticated to the access point (or without auth with ethernet), I see the dhcp discovery in wireshark, but I get no response (ACK packet). The journal is saying dhcp timeout.

Netctl profile

Description='A basic static ethernet connection'
Interface=wlp3s0
Connection=wireless
IP=dhcp
Security=wpa
ESSID=CoWorking_Montpellier
Key=blahblah

journalctl

juil. 31 14:40:52 shikoku network[9820]: Starting network profile 'CoWorking_Montpellier'...
juil. 31 14:40:52 shikoku kernel: iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
juil. 31 14:40:52 shikoku kernel: iwlwifi 0000:03:00.0: Radio type=0x0-0x0-0x3
juil. 31 14:40:52 shikoku kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
juil. 31 14:40:53 shikoku kernel: wlp3s0: authenticate with f8:1a:67:5a:54:12
juil. 31 14:40:53 shikoku kernel: wlp3s0: send auth to f8:1a:67:5a:54:12 (try 1/3)
juil. 31 14:40:53 shikoku kernel: wlp3s0: authenticated
juil. 31 14:40:53 shikoku kernel: wlp3s0: associate with f8:1a:67:5a:54:12 (try 1/3)
juil. 31 14:40:53 shikoku kernel: wlp3s0: RX AssocResp from f8:1a:67:5a:54:12 (capab=0x411 status=0 aid=5)
juil. 31 14:40:53 shikoku kernel: wlp3s0: associated
juil. 31 14:40:53 shikoku kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
juil. 31 14:40:53 shikoku dhcpcd[9857]: version 6.4.2 starting
juil. 31 14:40:53 shikoku dhcpcd[9857]: DUID 00:01:00:01:19:aa:0c:89:78:92:9c:0e:91:24
juil. 31 14:40:53 shikoku dhcpcd[9857]: wlp3s0: IAID 9c:0e:91:24
juil. 31 14:40:53 shikoku dhcpcd[9857]: wlp3s0: soliciting a DHCP lease
juil. 31 14:41:23 shikoku dhcpcd[9857]: timed out
juil. 31 14:41:23 shikoku dhcpcd[9857]: exited
juil. 31 14:41:23 shikoku network[9820]: DHCP IPv4 lease attempt failed on interface 'wlp3s0'
juil. 31 14:41:23 shikoku kernel: wlp3s0: deauthenticating from f8:1a:67:5a:54:12 by local choice (Reason: 3=DEAUTH_LEAVING)
juil. 31 14:41:23 shikoku kernel: cfg80211: Calling CRDA to update world regulatory domain
juil. 31 14:41:23 shikoku network[9820]: Failed to bring the network up for profile 'CoWorking_Montpellier'
juil. 31 14:41:23 shikoku systemd[1]: netctl@CoWorking_Montpellier.service: main process exited, code=exited, status=1/FAILURE
juil. 31 14:41:23 shikoku systemd[1]: Failed to start Networking for netctl profile CoWorking_Montpellier.
juil. 31 14:41:23 shikoku systemd[1]: Unit netctl@CoWorking_Montpellier.service entered failed state.

I also try to create a vlan connection as described in wiki https://wiki.archlinux.org/index.php/VLAN

With static ip, I can't ping gateway :

[ioo@shikoku ~]$ ping 192.168.10.1
PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.
From 192.168.10.19 icmp_seq=1 Destination Host Unreachable

And with dhcp I have a time out again.

[ioo@shikoku ~]$ sudo dhcpcd enp5s0.10
dhcpcd[10092]: version 6.4.2 starting
dhcpcd[10092]: DUID 00:01:00:01:19:aa:0c:89:78:92:9c:0e:91:24
dhcpcd[10092]: enp5s0.10: IAID e9:24:45:0f
dhcpcd[10092]: enp5s0.10: soliciting an IPv6 router
dhcpcd[10092]: enp5s0.10: soliciting a DHCP lease
dhcpcd[10092]: enp5s0.10: no IPv6 Routers available
dhcpcd[10092]: timed out
dhcpcd[10092]: exited

Note that in wireshark I see broadcast traffic as dropbox or other dhcp inform

The last, but not least thing, in the network, we have windows, mac and ubuntu client. Everything is ok, they connect with dhcp, I am the only guy

Thanks.

hydn · 2014-09-16 17:37:00

Same issue here. New install. I tried dhcpd first. disabled that after it didn't work (symlink removed) tried netctl and timesout

hydn · 2014-09-16 18:22:50

When you start new threads, the response is... "USE SEARCH!"

Then when you search the forums and followup on search results you get...
"hydn, rather than bumping multiple old threads by OPs who have not posted for many months, may I suggest that you start a new thread with your specific problem, and link back to these old threads if you think they apply?"

My apologies.

Im not able to post much error output from the laptop with the fresh install attempt.

My error is simlar. I've only tried wired which also results in similar:

dhcpcd[10092]: enp7s0: soliciting an IPv6 router
dhcpcd[10092]: enp7s0: soliciting a DHCP lease
dhcpcd[10092]: enp7s0: no IPv6 Routers available
dhcpcd[10092]: timed out

I will keep an eye on this thread. Will try antergos for now (just to make sure it works with Arch) until solved as I see lots of dead end discussions even outside of the these forums. I tested Xubuntu which connections worked for both wired and wireless, but I want to use Arch.

*subscribed.

Thanks!

Last edited by hydn (2014-09-16 18:40:29)

hydn · 2014-09-17 18:18:35

Got it to work. Even though my other linux laptops, smartphone, tablet, etc were all connecting to network when tested. It seems after exiting chroot and rebooting it the fresh install wouldn't connect. I had to reboot the wireless router. The same this happened when I tested with Antergos, on first usb boot it connected fine and installed everything then on first reboot it wouldn't connect. I'm still loyal to my old school WRT router though.

Don't think this may be OP's issue but just wanted to follow up with what worked for me. I tested multiple times because I restarted the Arch install a few times.

Arch Linux

#1 2014-07-31 13:00:05

VLAN and DHCP

#2 2014-09-16 17:37:00

Re: VLAN and DHCP

#3 2014-09-16 18:22:50

Re: VLAN and DHCP

#4 2014-09-17 18:18:35

Re: VLAN and DHCP

Board footer