Upgrade 17.7.12_1 to 18.1: Lost IPv4 connectivity from configured networks

[tgurr]

I've upgraded to 18.1 and now my internal networks can't reach the internet via a configured PPPoE dial-in connection via IPv4. IPv6 connectivity still works fine. The connection itself is up and running, my WAN interface got an IPv4 address and via the Interface - Diagnostics - Ping I can also ping IPv4 hosts without any problems as long as I choose Default as the source, when I choose one of my configured networks I'm unable to ping any IPv4 host.

The System - Gateway tab looks fine as well. Before the upgrade it worked fine, I didn't do any configuration changes since then, just the upgrade to 18.1.

Any help would be highly appreciated.

[elektroinside]

Try restarting the pf service (from the dashboard). Does this help?

[theq86]

https://forum.opnsense.org/index.php?topic=7060.msg31267#msg31267

If using rules for ICMP:

- do NOT mix v6 and v4 rules (don't use "IPv4+IPv6" version constraint)
- use protocol "IPV6-ICMP" for any rule regarding ICMP and v6
- use protocol "ICMP" for any rule regarding ICMP and v4

[franco]

So I have at least an idea why this wasn't found easily:

If you add a rule for ICMP, it preselects IPv4 and that obviously works.


Cheers,
Franco

[marvo9001]

Hi,
i lost IPv4 connectivity too. But only on some networks.
I have 2 internet connections. A Fibre Link that has IPv6 & IPv4+CGN and a DSL Link that is IPv4 only.

My interfaces:

Code: [Select]

IOT (re0_vlan34) -> v4: 192.168.129.1/24
                    v6/t6: 2a00:XXXX:1efc:6d81:20d:b9ff:fe33:9214/64
 LAN (re1)       -> v4: 192.168.123.129/25
                    v6/t6: 2a00:XXXX:1efc:6d7b:20d:b9ff:fe33:9215/64
 MULTIMEDIA (re0_vlan35) -> v4: 192.168.130.1/24
                    v6/t6: 2a00:XXXX:1efc:6d82:20d:b9ff:fe33:9214/64
 NETADMIN (re0_vlan32) -> v4: 192.168.128.1/24
                    v6/t6: 2a00:XXXX:1efc:6d80:20d:b9ff:fe33:9214/64
 WAN (re0_vlan30) -> v4: 192.168.178.18/24
                    v6/t6: 2a00:XXXX:1efc:6db2:20d:b9ff:fe33:9214/64
 WAN_DG (re2)    -> v4/DHCP4: 100.71.250.118/18
                    v6/DHCP6: 2a00:XXXX:1000:e:b4a1:db10:b480:977e/128
 WLAN (re0_vlan31) -> v4: 192.168.180.1/24
                    v6/t6: 2a00:XXXX:1efc:6db4:20d:b9ff:fe33:9214/64
 WLANGAST (re0_vlan33) -> v4: 10.255.227.1/24

I have already updated my rules regarding the ICMP changes.
LAN had IPv6 only until i changed the default Gateway to the Router of the DSL link.
The network WLAN has v4(DSL)+v6(Fibre) Internet. WLANGAST and MULTIMEDIA only via IPv6.
The ruleset of WLAN and MULTIMEDIA are nearly the same. I don't understand why WLAN works and MULTIMEDIA not.
IOT doesn't need Internet Access and i have not yet checked it.
I use hybrid outgoing NAT.
I don't use the multiWAN feature for automatic gateway switching, because the DSL link is too slow. My preffered link is the fibre link.

I think problem relies to the apinger, but i'm not sure.

I had the same problem as i tried the 18.1r1 two weeks ago, but i thought it was a beta problem and didn't had the time to debug. As i switched back to 17.7 my configuration worked fine again.

@tgurr: I don't think it is a PPPoE Problem. As you can see i have a DSL Router that gives me a private Ethernet istead of PPPoE to the opnsense and ithink we are experiencing the same problems.

Thanks for your support.

[azrael]

Hi,
after 5 hours we figured out how to solve the same problem on our firewall installation:
We have an alias for "Internet" which was configured with many IP blocks in a short notation like
1/8
2/7
...
which worked fine. Now, we had to change them all to
1.0.0.0/8
2.0.0.0/7
...
which solved the problem for us.

Maybe this helps someone else too.