Franck78
commented
1 month ago Cut this morning (11h57).
Wan interface em0_vlan832 was briefly lost causing the 'newwanip' thing to activate.
This time I clearly saw the em2_vlan832 (livebox) disconnected :
| 2024-09-20T11:57:55 | Error | dhclient | unknown dhcp option value 0x7d | |
|---|---|---|---|---|
| 2024-09-20T11:57:55 | Error | dhclient | unknown dhcp option value 0x5a | |
| 2024-09-20T11:57:54 | Notice | dhclient | dhclient-script: Reason ARPCHECK on em0_vlan832 executing | |
| 2024-09-20T11:57:52 | Notice | dhclient | dhclient-script: Reason ARPSEND on em0_vlan832 executing | |
| 2024-09-20T11:57:52 | Error | dhclient | unknown dhcp option value 0x7d | |
| 2024-09-20T11:57:52 | Error | dhclient | unknown dhcp option value 0x5a | |
| 2024-09-20T11:57:37 | Notice | dhclient | dhclient-script: Reason PREINIT on em0_vlan832 executing | |
| 2024-09-20T11:57:37 | Error | dhclient | ^ | |
| 2024-09-20T11:57:37 | Error | dhclient | vlan-id | |
| 2024-09-20T11:57:37 | Error | dhclient | /var/etc/dhclient_opt1.conf line 13: expecting a statement. | |
| 2024-09-20T11:57:37 | Error | dhclient | ^ | |
| 2024-09-20T11:57:37 | Error | dhclient | vlan-parent | |
| 2024-09-20T11:57:37 | Error | dhclient | /var/etc/dhclient_opt1.conf line 11: expecting a statement. | |
| 2024-09-20T11:57:37 | Notice | kernel | <6>vlan1: changing name to 'em2_vlan832' | |
| 2024-09-20T11:57:37 | Notice | kernel | <6>vtnet2: promiscuous mode disabled | |
| 2024-09-20T11:57:36 | Warning | rtsold | ||
| 2024-09-20T11:57:36 | Warning | rtsold | ||
| 2024-09-20T11:57:36 | Notice | kernel | <6>vlan0: changing name to 'em0_vlan832' | |
| 2024-09-20T11:57:36 | Warning | rtsold | ||
| 2024-09-20T11:57:36 | Warning | rtsold | ||
| 2024-09-20T11:57:36 | Critical | dhclient | exiting. | |
| 2024-09-20T11:57:36 | Error | dhclient | connection closed | |
| 2024-09-20T11:57:36 | Critical | dhclient | exiting. | |
| 2024-09-20T11:57:36 | Error | dhclient | No live interfaces to poll on - exiting. | |
| 2024-09-20T11:57:36 | Error | dhclient | Interface em0_vlan832 no longer appears valid. | |
| 2024-09-20T11:57:36 | Error | dhclient | ioctl(SIOCGIFFLAGS) on em0_vlan832: Operation not permitted | |
| 2024-09-20T11:57:36 | Error | dhclient | receive_packet failed on em0_vlan832: Device not configured |
(tcpdump started early) 2024-09-20T08:37:27 | Notice | kernel | <6>em2_vlan832: promiscuous mode enabled |
The problem started at 11h56, the livebox receive no answsers. Then at 11:56:26, the interface disappeared.
11:55:43.883182 IP 192.168.30.10.68 > 192.168.30.2.67: BOOTP/DHCP, Request from a4:3e:51:78:96:d6, length 392
11:55:43.898044 IP 192.168.30.2.67 > 192.168.30.10.68: BOOTP/DHCP, Reply, length 417
11:55:49.850427 ARP, Request who-has 192.168.30.2 tell 192.168.30.10, length 46
11:55:49.850455 ARP, Reply 192.168.30.2 is-at 52:54:00:cd:5f:42, length 28
11:56:01.195833 IP6 fe80::a63e:51ff:fe78:96d6.546 > ff02::1:2.547: dhcp6 solicit
11:56:05.531394 IP 192.168.30.10.42250 > 80.10.246.136.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:06.532677 IP 192.168.30.10.36973 > 81.253.149.6.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:07.533941 IP 192.168.30.10.42250 > 80.10.246.136.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:08.535733 IP 192.168.30.10.36973 > 81.253.149.6.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:09.536008 IP 192.168.30.10.42250 > 80.10.246.136.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:10.538910 IP 192.168.30.10.36973 > 81.253.149.6.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:11.539980 IP 192.168.30.10.42250 > 80.10.246.136.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:12.542119 IP 192.168.30.10.36973 > 81.253.149.6.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:23.651065 IP 192.168.30.10.42250 > 80.10.246.136.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:24.652450 IP 192.168.30.10.36973 > 81.253.149.6.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:25.655207 IP 192.168.30.10.42250 > 80.10.246.136.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:26.656810 IP 192.168.30.10.36973 > 81.253.149.6.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:31.662599 IP 192.168.30.10.42250 > 80.10.246.136.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:32.664134 IP 192.168.30.10.36973 > 81.253.149.6.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:33.668751 IP 192.168.30.10.42250 > 80.10.246.136.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:34.670232 IP 192.168.30.10.36973 > 81.253.149.6.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:47.675791 IP 192.168.30.10.42250 > 80.10.246.136.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:48.677327 IP 192.168.30.10.36973 > 81.253.149.6.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:49.679138 IP 192.168.30.10.42250 > 80.10.246.136.53: 55989+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:56:50.679676 IP 192.168.30.10.36973 > 81.253.149.6.53: 24435+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:57:11.552660 IP 192.168.30.10.43666 > 80.10.246.136.53: 48034+ A? audiphone-lb4-fr.odmtrack.orange.com. (54)
11:57:11.552805 IP 192.168.30.10.53183 > 80.10.246.136.53: 49808+ AAAA? audiphone-lb4-fr.odmtrack.orange.com. (54)
11:57:16.561011 IP 192.168.30.10.43666 > 81.253.149.6.53: 48034+ A? audiphone-lb4-fr.odmtrack.orange.com. (54)
11:57:16.561157 IP 192.168.30.10.53183 > 81.253.149.6.53: 49808+ AAAA? audiphone-lb4-fr.odmtrack.orange.com. (54)
11:57:19.689983 IP 192.168.30.10.39822 > 80.10.246.136.53: 14340+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:57:20.691570 IP 192.168.30.10.44640 > 81.253.149.6.53: 20472+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:57:21.568506 IP 192.168.30.10.39211 > 80.10.246.136.53: 46544+ A? audiphone-lb4-fr.odmtrack.orange.com.VEL.access.orange-multimedia.net. (87)
11:57:21.568650 IP 192.168.30.10.41755 > 80.10.246.136.53: 41337+ AAAA? audiphone-lb4-fr.odmtrack.orange.com.VEL.access.orange-multimedia.net. (87)
11:57:21.693923 IP 192.168.30.10.39822 > 80.10.246.136.53: 14340+ AAAA? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:57:22.695914 IP 192.168.30.10.44640 > 81.253.149.6.53: 20472+ A? epdg.epc.mnc001.mcc208.pub.3gppnetwork.org. (60)
11:57:26.574665 IP 192.168.30.10.39211 > 80.10.246.136.53: 46544+ A? audiphone-lb4-fr.odmtrack.orange.com.VEL.access.orange-multimedia.net. (87)
11:57:26.574757 IP 192.168.30.10.41755 > 80.10.246.136.53: 41337+ AAAA? audiphone-lb4-fr.odmtrack.orange.com.VEL.access.orange-multimedia.net. (87)
tcpdump: pcap_loop: The interface disappeared
From now, the ICSDHCPv4 will never honor em2_vlan832 until restart of dhcp service.
root@opnSense:~ # tcpdump -n -i em2_vlan832
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on em2_vlan832, link-type EN10MB (Ethernet), snapshot length 262144 bytes
12:37:26.208689 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from a4:3e:51:78:96:d6, length 398
12:37:56.550380 IP6 fe80::a63e:51ff:fe78:96d6.546 > ff02::1:2.547: dhcp6 solicit
nothing particular at line 11 & 13, dhclient 'error' in the log
root@opnSense:~ # cat /var/etc/dhclient_opt1.conf
interface "em0_vlan832" {
# DHCP Protocol Timing Values
timeout 8;
retry 3;
# DHCP Protocol Options
send dhcp-class-identifier "sagem";
send user-class "+FSVDSL_livebox.Internet.softathome.Livebox4";
send option-90 f3:3b:ac:b9:a5;
request subnet-mask, routers, domain-name-servers, broadcast-address, dhcp-lease-time, dhcp-renewal-time, dhcp-rebinding-time, domain-search, option-90, option-120, option-125;
vlan-parent "em0";
vlan-pcp 6;
vlan-id 832;
script "/usr/local/opnsense/scripts/interfaces/dhclient-script";
supersede interface-mtu 0;
}
root@opnSense:~ # ls -l /var/etc/dhclient_opt1.conf
-rw-r--r-- 1 root wheel 761 Sep 20 11:57 /var/etc/dhclient_opt1.conf
fichtner
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
DHCP server is not responding to "Request":
To Reproduce Apparently, this is related to when opnSense retrieve the WAN interface or maybe when any interface reappears. not easy to spot the event and link it to the deconnection of ICS Dhcp server (even with a 10minutes lease time).
OpnSense interfaces:
Relevant log files
If applicable, information from log files supporting your claim.
As soon as ICS DHCPv4 is restarted by OpnSense web interface, the livebox gets the lease and everything is ok until some hours:
Environment
OPNsense 24.7.4_1-amd64 FreeBSD 14.1-RELEASE-p4 OpenSSL 3.0.15
OpnSense runs as a VM on Ubuntu server.
The livebox is provided by the ISP Orange. To have the phone working (SIP) the livebox must be online. The trick is connecting the WAN interface of the livebox on a local network port. The port is attributed to a virtual bridge. Then OpnSense is presented thoses virtual interfaces .
The difference between the regular LAN interface and the Livebox interface is mainly the VLAN 832 aspect of the setup. As if when OpnSense recovers from 'some event' at low level interfaces, ICS DCHP is not 'seeing' the new em2_vlan832 interface.
This log is just when I noticed lost of internet connection and yep, the livebox was down just after this (9h30):