Actions
Bug #14083
openAdding MSS and MTU values on XG-7100 WAN interface breaks the network connectivity on the firewall
Status:
New
Priority:
High
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Release Notes:
Default
Affected Plus Version:
Affected Architecture:
7100
Description
Steps to reproduce:
- Under Interfaces/WAN, define MTU 1480 and MSS 1440. Save and Apply the changes.
- Reboot the firewall.
- Following the boot logs, I found nothing pointing to the issue. However, after the boot process finishes, the WAN interface didn't receive the IP from the DHCP server, and the DHCP server doesn't provide addresses to the clients connected to the LAN interface. I tried manually defining IP on the client machine, but I couldn't ping the 192.168.1.1 (XG-7100) Lan address or access the GUI.
Updated by Jordan Greene 2 months ago
confirmed on 7100 running 23.01 - after setting mtu/mss and rebooting system receives and displays IP on WAN in console but gui cannot be reached and ping test from console reports sendto: network is down, trying to ping from a different host returns destination host unreachable.
Updated by Jim Pingle 2 months ago
- Project changed from pfSense to pfSense Plus
- Category changed from Interfaces to Interfaces
- Status changed from New to Duplicate
Updated by Danilo Zrenjanin about 2 months ago
We had a customer complaining about similar behavior at Netgate 2100. However, I couldn't reproduce this behavior on Netgate 2100. I defined MTU/MSS on mvneta0 and mvneta1, and everything worked fine. It seems that only XG-7100 is affected.
Updated by Lukas Macura 25 days ago
Is there any progress here?
This is serious bug which affects all XG-7100s path MTU discovery.
Is there any workaround for this please?
Updated by Danilo Zrenjanin 20 days ago
- Priority changed from Normal to High
I tested against:
23.05-RC (amd64) built on Mon May 15 22:17:39 UTC 2023 FreeBSD 14.0-CURRENT
The problem persists.
Actions