cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
747
Views
0
Helpful
1
Replies

RV320 dhcp and linux client

liochan_cisco
Level 1
Level 1

Hi,

We install a new network with a RV320, a HP switch 1910-8G and an access point TP-Link TL-WDR4900 which was our old routeur.

Main network is 192.168.1.0/24

We created 2 vlans, id 10 192.168.10.0/24 and id 20 192.168.20.0/24

Each windows or mac client connects to wifi ap with an SSID and a wpa2 key. RV320 is providing all informations related to the vlan, give an ip address with dhcp, give gateway and dns server. We do not have problems with thoses clients, like with tablets, iphone or android.

When we tried connection with linux client, it didn't work.

 

Here is the log with a archlinux client using netctl and dhcpcd client.

juil. 29 14:21:47 shikoku network[8701]: Starting network profile 'CoworkInMontpellier'...
juil. 29 14:21:47 shikoku kernel: iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
juil. 29 14:21:47 shikoku kernel: iwlwifi 0000:03:00.0: Radio type=0x0-0x0-0x3
juil. 29 14:21:47 shikoku kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
juil. 29 14:21:48 shikoku kernel: wlp3s0: authenticate with f8:1a:67:5a:54:12
juil. 29 14:21:48 shikoku kernel: wlp3s0: send auth to f8:1a:67:5a:54:12 (try 1/3)
juil. 29 14:21:48 shikoku kernel: wlp3s0: authenticated
juil. 29 14:21:48 shikoku kernel: wlp3s0: associate with f8:1a:67:5a:54:12 (try 1/3)
juil. 29 14:21:48 shikoku kernel: wlp3s0: RX AssocResp from f8:1a:67:5a:54:12 (capab=0x411 status=0 aid=5)
juil. 29 14:21:48 shikoku kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
juil. 29 14:21:48 shikoku kernel: wlp3s0: associated
juil. 29 14:21:48 shikoku dhcpcd[8732]: version 6.4.2 starting
juil. 29 14:21:48 shikoku dhcpcd[8732]: DUID 00:01:00:01:19:aa:0c:89:78:92:9c:0e:91:24
juil. 29 14:21:48 shikoku dhcpcd[8732]: wlp3s0: IAID 9c:0e:91:24
juil. 29 14:21:49 shikoku dhcpcd[8732]: wlp3s0: soliciting a DHCP lease

juil. 29 14:22:18 shikoku dhcpcd[8732]: timed out
juil. 29 14:22:18 shikoku dhcpcd[8732]: exited
juil. 29 14:22:18 shikoku network[8701]: DHCP IPv4 lease attempt failed on interface 'wlp3s0'
juil. 29 14:22:18 shikoku kernel: wlp3s0: deauthenticating from f8:1a:67:5a:54:12 by local choice (Reason: 3=DEAUTH_LEAVING)
juil. 29 14:22:18 shikoku kernel: cfg80211: Calling CRDA to update world regulatory domain
juil. 29 14:22:18 shikoku network[8701]: Failed to bring the network up for profile 'CoworkInMontpellier'
juil. 29 14:22:18 shikoku systemd[1]: netctl@CoworkInMontpellier.service: main process exited, code=exited, status=1/FAILURE
juil. 29 14:22:18 shikoku systemd[1]: Failed to start Networking for netctl profile CoworkInMontpellier.
juil. 29 14:22:18 shikoku systemd[1]: Unit netctl@CoworkInMontpellier.service entered failed state.

 

With wireshark we saw the dhcp request from linux to router, but we did not receive the ACK response.

 

We connect the linux client directly to the RV320 with an ethernet cable. And we retried to connect. Same issue.

 

If we configure the client connection with a static ip address 192.168.10.19, the router address as gateway and dns server 192.168.10.1, the client was connected and could browse the network and internet.

So we tried the same configuration with the wireless interface, and it worked.

We have 2 linux clients, one with archlinux, the other with ubuntu and we have the same effects. We can connect with static ip, but not with dhcp.

Any suggestions ? Thank you.

1 Reply 1

arthurcrmp
Level 1
Level 1

Hi,

There is a bug in the dhcp server of the RV320, it fails to attribute an ip if the dhcp client send an unknow dhcp client identifier. A solution is to set this id as an empty string like that :

vim etc/dhcp/dhclient.conf

send dhcp-client-identifier = "";

 

more info : https://bugzilla.redhat.com/show_bug.cgi?id=1154200