Re: dhcpleased: interface "stalls" during Renewing
Thanks Sebastian, and this situation seems different from the thread that informed me, as my "stall" starts immediately at the Renewing transition and lasts nearly 30 minutes until the client broadcasts. I believe Florian's fix was for a 20 second or so dropout at the end, where my situation starts right at the Renewing process. Also, I don't know how to apply a diff, heh. Looks like I would use sysupgrade(8) to apply the snapshot and that is worth a try. Best, Pete On 11/14/2021 4:23 PM, Sebastian Benoit wrote: Peter Gorsuch(gorsu...@cfw.com) on 2021.11.13 08:25:00 -0500: Hi All, As [Renewing] begins and during the renewing cycle (as I view configuration with dhcpleasectl -l fxp0) about halfway through the ISP'one hour dhcp lease, the external interface seems to become "stalled". "Stalled" is a term that describes the experience of using a host on the lan, as one's video is fine, then stops, then starts up again after some period of time. This on a dual homed i386 GENERIC installation planned to be a router and run unbound and dhcp for the lan. Subject to my understanding, I'm informed by https://www.mail-archive.com/misc@openbsd.org/msg180064.html and I imagine there is some interplay with the dhcp rebinding/renewing timer(s) and name resolution. Have you tried the fix suggested by florian@ in that thread? If not you can upgrade to the latest snapshot, that change was commited yesterday.
Re: dhcpleased: interface "stalls" during Renewing
Peter Gorsuch(gorsu...@cfw.com) on 2021.11.13 08:25:00 -0500: > Hi All, > > As [Renewing] begins and during the renewing cycle (as I view > configuration with dhcpleasectl -l fxp0) about halfway through the > ISP'one hour dhcp lease, the external interface seems to become "stalled". > > "Stalled" is a term that describes the experience of using a host on the > lan, as one's video is fine, then stops, then starts up again after some > period of time. > > This on a dual homed i386 GENERIC installation planned to be a router > and run unbound and dhcp for the lan. > Subject to my understanding, I'm informed by > https://www.mail-archive.com/misc@openbsd.org/msg180064.html and I > imagine there is some interplay with the dhcp rebinding/renewing > timer(s) and name resolution. Have you tried the fix suggested by florian@ in that thread? If not you can upgrade to the latest snapshot, that change was commited yesterday.
dhcpleased: interface "stalls" during Renewing
Hi All, As [Renewing] begins and during the renewing cycle (as I view configuration with dhcpleasectl -l fxp0) about halfway through the ISP'one hour dhcp lease, the external interface seems to become "stalled". "Stalled" is a term that describes the experience of using a host on the lan, as one's video is fine, then stops, then starts up again after some period of time. This on a dual homed i386 GENERIC installation planned to be a router and run unbound and dhcp for the lan. Subject to my understanding, I'm informed by https://www.mail-archive.com/misc@openbsd.org/msg180064.html and I imagine there is some interplay with the dhcp rebinding/renewing timer(s) and name resolution. hostname.fxp0 has: lladdr [fxp0 mac address] inet autoconf up during the "stall": from a local host I can ping the "stalled" interface from the stalled interface I can ping the adjacent fxp1 interface (and vice versa) from the stalled interface I can ping a local lan host from the stalled interface I cannot ping the dhcp server ping -I 64.203.147.252 64.4.147.142 (dhcp server) and ping says "No route to host" Another dhcp server: 64.4.117.66 has provided an address and all is good until the next Renewing cycle. For completeness I'll mention that during the "stall" or Renewing time, when the client does the unicast request, ISP dhcp server is the fourth hop out from fxp0. Please find below logs of tcpdump on port 67 and 68 along with a record of dhcpleased's actions. Again, all is subject to my understanding of things, and if further direction is needed, I'm willing. Thank you very much, Pete tcpdump on ports 67 and 67 (overnight): 21:37:37.794212 00:01:29:17:24:01 ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 > 255.255.255.255.67: xid:0xbf9abf5 [|bootp] [tos 0x10] 21:37:37.820800 a4:7b:2c:3d:03:74 00:01:29:17:24:01 0800 590: 64.203.147.2.67 > 64.203.147.251.68: xid:0xbf9abf5 Y:64.203.147.251 G:10.245.0.3 [|bootp] [tos 0xc0] 22:07:37.921663 00:01:29:17:24:01 00:00:5e:00:01:09 0800 342: 64.203.147.251.68 > 64.4.117.142.67: xid:0xe8045d16 [|bootp] 22:18:53.031792 00:01:29:17:24:01 00:00:5e:00:01:09 0800 342: 64.203.147.251.68 > 64.4.117.142.67: xid:0x7565c229 [|bootp] 22:30:42.560940 00:01:29:17:24:01 ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 > 255.255.255.255.67: xid:0xb5045322 [|bootp] [tos 0x10] 22:30:42.585848 a4:7b:2c:3d:03:74 00:01:29:17:24:01 0800 590: 64.203.147.2.67 > 64.203.147.251.68: xid:0xb5045322 Y:64.203.147.251 G:10.245.0.3 [|bootp] [tos 0xc0] 22:30:42.588890 00:01:29:17:24:01 00:00:5e:00:01:09 0800 342: 64.203.147.251.68 > 64.4.117.142.67: xid:0x94f64521 [|bootp] 23:20:23.003559 00:01:29:17:24:01 ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 > 255.255.255.255.67: xid:0xd82511a3 [|bootp] [tos 0x10] 23:20:23.028535 a4:7b:2c:3d:03:74 00:01:29:17:24:01 0800 590: 64.203.147.2.67 > 64.203.147.251.68: xid:0xd82511a3 Y:64.203.147.251 G:10.245.0.3 [|bootp] [tos 0xc0] 23:50:23.130648 00:01:29:17:24:01 00:00:5e:00:01:09 0800 342: 64.203.147.251.68 > 64.4.117.142.67: xid:0xb72f620e [|bootp] 00:13:27.769937 00:01:29:17:24:01 ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 > 255.255.255.255.67: xid:0xaf233fee [|bootp] [tos 0x10] 00:13:27.794085 a4:7b:2c:3d:03:74 00:01:29:17:24:01 0800 590: 64.203.147.2.67 > 64.203.147.251.68: xid:0xaf233fee Y:64.203.147.251 G:10.245.0.3 [|bootp] [tos 0xc0] 00:43:27.898039 00:01:29:17:24:01 00:00:5e:00:01:09 0800 342: 64.203.147.251.68 > 64.4.117.66.67: xid:0x5218fa3b [|bootp] 01:06:32.537328 00:01:29:17:24:01 ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 > 255.255.255.255.67: xid:0x4eb78fc9 [|bootp] [tos 0x10] 01:06:32.562361 a4:7b:2c:3d:03:74 00:01:29:17:24:01 0800 590: 64.203.147.2.67 > 64.203.147.251.68: xid:0x4eb78fc9 Y:64.203.147.251 G:10.245.0.3 [|bootp] [tos 0xc0] 01:36:32.664554 00:01:29:17:24:01 00:00:5e:00:01:09 0800 342: 64.203.147.251.68 > 64.4.117.66.67: xid:0xbd0c7e36 [|bootp] 01:59:37.303896 00:01:29:17:24:01 ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 > 255.255.255.255.67: xid:0x5ad6e610 [|bootp] [tos 0x10] 01:59:37.328723 a4:7b:2c:3d:03:74 00:01:29:17:24:01 0800 590: 64.203.147.2.67 > 64.203.147.251.68: xid:0x5ad6e610 Y:64.203.147.251 G:10.245.0.3 [|bootp] [tos 0xc0] 02:29:37.431019 00:01:29:17:24:01 00:00:5e:00:01:09 0800 342: 64.203.147.251.68 > 64.4.117.142.67: xid:0x880c6233 [|bootp] 02:51:41.962153 00:01:29:17:24:01 ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 > 255.255.255.255.67: xid:0xe92a28b6 [|bootp] [tos 0x10] 02:51:41.986640 a4:7b:2c:3d:03:74 00:01:29:17:24:01 0800 590: 64.203.147.2.67 > 64.203.147.251.68: xid:0xe92a28b6 Y:64.203.147.251 G:10.245.0.3 [|bootp] [tos 0xc0] 03:21:42.089271 00:01:29:17:24:01 00:00:5e:00:01:09 0800 342: 64.203.147.251.68 > 64.4.117.66.67: xid:0xa0ed2e00 [|bootp] 03:44:46.728577 00:01:29:17:24:01 ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 > 255.255.255.255.67: xid:0xba32aa0b [|bootp] [tos 0x10] 03:44:46.753055 a4:7b:2c:3d:03:74 00:01:29:17:24:01 0800 590: 64.203.147.2.67 > 64.203.147.251.68:
