Project

General

Profile

Actions

Bug #13729

closed

Gateways stuck in Unknown status

Added by Nazar Mokrynskyi over 1 year ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Multi-WAN
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.6.0
Affected Architecture:
All

Description

My pfSense is virtualized, so its interfaces are always up.
I have a multi-WAN setup with WAN and WAN2 interfaces.

I booted VM today with physical connections on the host for both interfaces unplugged, so pfSense wasn't able to get IP addresses over DHCP from ISPs.

When I later connected physical interfaces, pfSense was able to get IP address and things seemed to work, however gateway status remained "Unknown" forever.


Files

Actions #1

Updated by Marcos M over 1 year ago

  • Status changed from New to Feedback

There's a decent chance this is fixed in 2.7/23.01. Please test there.

Actions #2

Updated by Nazar Mokrynskyi over 1 year ago

Marcos M wrote in #note-1:

There's a decent chance this is fixed in 2.7/23.01. Please test there.

I'm willing to try, how safe is 2.7 to daily drive without any third-party apps at this point?

Actions #3

Updated by Marcos M over 1 year ago

I would not recommend it for production, but it should be fine for personal use.

Actions #4

Updated by Nazar Mokrynskyi over 1 year ago

Marcos M wrote in #note-3:

I would not recommend it for production, but it should be fine for personal use.

It is for personal home use, so I went ahead and updated to 2.7.0.a.20221209.0600, but unfortunately the issue is still present.
Also I noticed that when pfSense gets IP addresses on both WAN interfaces, routing works, but DNS resolver is not until I manually restart it.
Probably related, if not I'm not sure how to reproduce it outside of this issue.

Actions #5

Updated by Jordan G over 1 year ago

what virtual environment, host version, etc?

Actions #6

Updated by Nazar Mokrynskyi over 1 year ago

Jordan Greene wrote in #note-5:

what virtual environment, host version, etc?

Qemu 7 with 3 virtio network interfaces (WAN, LAN, WAN2), host is x86-64 Alpine Linux that bridges virtual interfaces to physical ones and runs some other VMs as well. Nothing special really.

Actions #7

Updated by Jordan G over 1 year ago

Nazar Mokrynskyi wrote in #note-6:

Qemu 7 with 3 virtio network interfaces (WAN, LAN, WAN2), host is x86-64 Alpine Linux that bridges virtual interfaces to physical ones and runs some other VMs as well. Nothing special really.

Were you able to see if dpinger service was started or not?

Actions #8

Updated by Nazar Mokrynskyi over 1 year ago

Jordan Greene wrote in #note-7:

Nazar Mokrynskyi wrote in #note-6:

Qemu 7 with 3 virtio network interfaces (WAN, LAN, WAN2), host is x86-64 Alpine Linux that bridges virtual interfaces to physical ones and runs some other VMs as well. Nothing special really.

Were you able to see if dpinger service was started or not?

It didn't, only when I re-applied settings on WAN it caused dpinger to start on all interfaces and they went "Online"

Actions #9

Updated by Jordan G over 1 year ago

Nazar Mokrynskyi wrote:

My pfSense is virtualized, so its interfaces are always up.
pfSense was able to get IP address and things seemed to work, however gateway status remained "Unknown" forever.

Let us know if this persists once you've had the opportunity to update. Thanks!

Marcos M wrote in #note-1:

There's a decent chance this is fixed in 2.7/23.01. Please test there.

Actions #10

Updated by Nazar Mokrynskyi over 1 year ago

Jordan Greene wrote in #note-9:

Nazar Mokrynskyi wrote:

My pfSense is virtualized, so its interfaces are always up.
pfSense was able to get IP address and things seemed to work, however gateway status remained "Unknown" forever.

Let us know if this persists once you've had the opportunity to update. Thanks!

Marcos M wrote in #note-1:

There's a decent chance this is fixed in 2.7/23.01. Please test there.

As I mentioned in further comments I already tested 2.7 with the same result back in December, just re-tested latest 2.7 from February 15th and it is still an issue.

P.S. I really wish interfaces were configured in parallel, those timeouts take a while.

Actions #11

Updated by Marko Koivusalo over 1 year ago

Same issue, restarting dpinger service resolved the issue. I have dpinger in service watchdog service do it should not have been dead at least.

Actions #12

Updated by Jordan G about 1 year ago

Actions #13

Updated by Azamat Khakimyanov 10 months ago

  • Status changed from Feedback to Resolved

Tested on several pfSense versions: 21.02_2, 22.05, 23.05_1 and 2.7

I was able to reproduce this issue on 21.02_2.
What I saw on 21.02_2 was that when I unplugged cables from both WAN ports and rebooted pfSense, dpinger service stayed down after reboot. So dpinger didn't start if there were only 2 WAN gateways which were down. And plugging cables back to WAN ports didn't start dpinger service.

I added one more LAN gateway which was always UP, unplugged cables from both WAN ports and rebooted pfSense. After reboot dpinger service was running and LAN gateway was 'Online'. When I plugged WAN cables back, both WAN ports became UP, internal hosts got internet access BUT WAN gateways' status still were Pending.

I wasn't able to reproduce this issue on on 23.05_1 and on 2.7-CE. Everything works correctly.

I marked this Bug as resolved.

Actions

Also available in: Atom PDF