Messages

Is there a date planned to release the fix?

I had a hunch and it was quicky confirmed:

https://github.com/opnsense/core/commit/528a6349

The workaround is alright but I think going back to the historic check is better for the time being.


Cheers,
Franco

Problem solved - it was a firewall setting stopping echo replies to outside local subnet
Resolved by adding 192.168.0.0/16
See attached

Code Select Expand

@192.168.3.2:~$ traceroute 192.168.2.50
traceroute to 192.168.2.50 (192.168.2.50), 30 hops max, 60 byte packets
1  _gateway (192.168.3.1)  0.222 ms  0.183 ms  0.159 ms
2  * * *
3  * * *
4  * * *
5  * * *
6  * * *
7  *^C

[Problem]

A newbie here, setting up my first router with four NICs.

Problem: pings between two local lans are flowing fine from LAN -> OPT1, but NOT from OPT1->LAN

Setup
OPT1 is named NAS

Interfaces:
igc0 WAN
igc1 LAN       192.168.2.1/24
igc2 OPT1(NAS) 192.168.3.1/24
Both LASs enabled
"Block private networks" unchecked on both

Firewall Rules:
in IPv4   *   LAN net   *   *   *   *   *      Default allow LAN to any rule
in IPv4+6 *   NAS net   *   *   *   *   *      Default allow NAS to any rule

DHCP enabled on both interfaces

Tests:
Ping

• From 192.168.2.50 on LAN: ping   ok to 192.168.3.1 and 192.168.3.2
• From 192.168.3.2  on NAS: ping   ok to 192.168.2.1
• From 192.168.3.2  on NAS: 100% loss to 192.168.2.50
• WebUI Ping:   ok to 192.168.2.50
• WebUI Ping:   ok to 192.168.3.2
• WebUI Ping:   ok        source=192.168.3.1 to 192.168.2.1
• WebUI Ping:   100% loss source=192.168.3.1 to 192.168.2.50

WebUI Ping is done using Interfaces: Diagnostics: Ping

Trace Route ICMP using WebUI
Response
traceroute to 192.168.2.50 (192.168.2.50) from 192.168.3.1, 64 hops max, 40 byte packets
TTL   AS#   Host   Address   Probes
timeout reached
Response
traceroute to 192.168.2.50 (192.168.2.50) from 192.168.2.1, 64 hops max, 48 byte packets
TTL   AS#   Host   Address   Probes
1   AS0   txxxxa   192.168.2.50   0.262 ms