Project

General

Profile

Actions

Bug #13729

open

Gateways stuck in Unknown status

Added by Nazar Mokrynskyi about 2 months ago. Updated about 1 month ago.

Status:
Feedback
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 about 2 months 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 about 2 months 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 about 2 months ago

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

Actions #4

Updated by Nazar Mokrynskyi about 2 months 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 Greene about 2 months ago

what virtual environment, host version, etc?

Actions #6

Updated by Nazar Mokrynskyi about 2 months 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 Greene about 1 month 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 about 1 month 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

Also available in: Atom PDF