OPNsense Forum

Archive => 18.7 Legacy Series => Topic started by: mahescho on September 07, 2018, 05:00:44 pm

Title: Strange IPv6 behavior after update
Post by: mahescho on September 07, 2018, 05:00:44 pm
Hi,

to day I revived my new OPNsense appliance. I set it up with IPv4 and IPv6 and everything worked as expected. The I've updated it to the current version 18.1.13_1-amd64 and IPv6 stopped working. I found that just no IPv6 packets left the appliance. I've seen arrive my ICMP echo requests but no answers. IMHO The packets got dropped. I had to remove the IPv6 address from the WAN interface and the re add it to make it work again.

Just want to let the devs know about this strange behavior.

Matthias
Title: Re: Strange IPv6 behavior after update
Post by: franco on September 08, 2018, 10:36:55 am
Hi Matthias,

It could be related due to ISP oddities: the DHCPv6 advanced options given by OPNsense are plenty for that reason and should be double-checked with the recommendations for your ISP. We're also working on different DUID support schemes and it'll take some time to get everything into the release and documented accordingly.

18.1.13_1 is not the latest version anymore. The point release is 18.7.2 now.


Cheers,
Franco
Title: Re: Strange IPv6 behavior after update
Post by: mahescho on September 08, 2018, 04:21:00 pm
Hi Franco,

In my setup I use a Microtik router to connect to my ISP. There I get a /29 IPv4 net and a /48 IPv6 net. I do not delegate subnets right now I just use static configurations of subnets and routes. So I use a static IPv6 setup on the firewall.

Now I've upgraded from 18.1-amd64 to 18.7-amd64 and it's all the same as soon as I reboot. I've to disable IPv6 on the WAN interface and re enable it to get back IPv6 connectivity. Wen I check the configuration on the shell with "netstat -rn" and "netstat -in" every thing looks fine but it just does not work. When I monitor the WAN interface with "tcpdump" while I'm pinging I don't see a single packet. I think it's some kind of problem in conjunction with "pf". It looks linke all outgoing packets get droppe silently. When I ping the firewall from the router and monitor the WAN interface with "tcpdump" I can see the ICMP echo request bur no replies.

In addition there is a problem with the dashboard. I'm currently pinging a v4 and v6 destination from the firewall without any packet loss and the status of the two gateways on the dashboard flaps every now and then from green to red and vice versa.

One last thing: "ntpd" does not survive the IPv6 reconfiguration. I've to start it afterwards.

Currently the firewall is not in production use. I'm just testing and tying to get familiar with the system. I've no IPv6 on the LAN interface so I can't say if it's affected too.

cheers
Matthias
Title: Re: Strange IPv6 behavior after update
Post by: bimmerdriver on September 08, 2018, 09:12:20 pm
After I updated my system, the Windows 10 computer I'm using on it had no IPv6 address. I had to disable and enable the adapter, then everything was normal.
Title: Re: Strange IPv6 behavior after update
Post by: mahescho on September 10, 2018, 08:24:39 am
Well, now I'm on 18.7.2 and it's all the same as described above ..

Any suggestions?

Suggestion to make life easier: The default net mask for IPv6 should (IMO) be 64 and not 128 for Interfaces.
Title: Re: Strange IPv6 behavior after update
Post by: Droppie391 on September 10, 2018, 09:33:57 am
Just noticed the same problem here, found that the deafult route was pointing to the wan interface in stead of the pppoe interface. fe80::.....%igb0 in stead of fe80::.....%pppoe0
changeing the default route on the console fixed it temporarily:

route -6 delete default
route -6 add default fe80::.....%pppoe0

this may not survive a re-init of the pppoe session !!!
Title: Re: Strange IPv6 behavior after update
Post by: Droppie391 on September 10, 2018, 09:43:13 am
some more info from the system log when the pppoe restarted this morning (by the way im on 18.7.2 since yday)

Sep 10 05:00:05 xxxxxx opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'pppoe0'
Sep 10 05:00:05 xxxxxx opnsense: /usr/local/etc/rc.newwanip: On (IP address: AA.BB.CC.DD) (interface: MTKOM[wan]) (real interface: pppoe0).
Sep 10 05:00:06 xxxxxx opnsense: /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'wan'
Sep 10 05:00:06 xxxxxx opnsense: /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to wan
Sep 10 05:00:06 xxxxxx opnsense: /usr/local/etc/rc.newwanip: ROUTING: IPv6 default gateway set to wan
Sep 10 05:00:06 xxxxxx opnsense: /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to ISP_GW
Sep 10 05:00:06 xxxxxx opnsense: /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway 'ISP-GW'
Sep 10 05:00:06 xxxxxx opnsense: /usr/local/etc/rc.newwanip: ROUTING: skipping IPv6 default route
S

Title: Re: Strange IPv6 behavior after update
Post by: Droppie391 on September 10, 2018, 11:18:25 am
looking at function system_routing_configure in system.inc, it looks like there is no check if the wan is connected to a pppoe interface. the deafult route is here set to the wan interface, which is what i observe, and the Log-message matches this as well (ROUTING: skipping IPv6 default route).
Title: Re: Strange IPv6 behavior after update
Post by: mahescho on September 10, 2018, 01:03:56 pm
I'm not using PPPoE. My IPv6 setup is static on a ethernet interface. Lately I found, that my fist guess, that it has to be a PF issue seems to be right. The only thing I need to do to get it working again is a "pfctl -d" and then "pfctl -e" ...
Title: Re: Strange IPv6 behavior after update
Post by: franco on September 10, 2018, 01:44:10 pm
Hi guys,

I'm doing thorough audit of the interface code since about 2 weeks and what is described here from different angles seems to be what's going on: when IPv4 and IPv6 devices are not the same network device that's where certain reloads go south. But to be fair, this behaviour isn't new at all. And there is no quick fix so the target for correcting these issues will be 19.1 with smaller confirmed fixes being moved to 18.7.x subsequently.

Important things to note when reporting such issues for completeness: setup type of IPv4 and IPv6 and possible advanced IPv6 settings set and the ISP involved. Plus the last version where this worked fine 100% (if applicable).


Thanks,
Franco
Title: Re: Strange IPv6 behavior after update
Post by: Droppie391 on September 10, 2018, 02:47:50 pm
Hi Franco, fair enough.

These are our settings:

ISP: Titan Networks
ipv4 config type: PPPOE (static ip address)
ipv6 config type: DHCPv6  ( /48 range w/o dns nor ip addresses)
Request only an IPv6 prefix = activated
Send SOLICIT direct = activated
NO ipv6 static address on wan side

we are happily working with LL addresses over the pppoe connection
ipv6 routing to our dedicated range is handled by the ISP

Things were alright until the upgrade from 18.1.13 to 18.7.1, then the pppoe-loop effect came to us 2 times in 3 days (before 18.7 we never noticed this).

for completeness, we have 2 OPNsenses in HA where we manually have to switch the pppoe link on failure of
the master box. we would love to have a solution here.. :)

Title: Re: Strange IPv6 behavior after update
Post by: mahescho on September 10, 2018, 03:48:49 pm
Hi Franco,

what do you mean with "not the same network device"?

My WAN interface is igb2. On this interface IPv4 and IPv6 is configured ... a dual stack setup. Both, IPv4 and IPv6 are static configurations.

cheers
Matthias
Title: Re: Strange IPv6 behavior after update
Post by: franco on September 10, 2018, 05:26:00 pm
@Droppie391: try this patch...

https://github.com/opnsense/core/commit/5811fe53

# opnsense-patch 5811fe53

@mahescho: does the following command fix your issue temporarily?

# /usr/local/etc/rc.filter_configure


Cheers,
Franco
Title: Re: Strange IPv6 behavior after update
Post by: mahescho on September 10, 2018, 08:13:09 pm
Hi Fanco,

/usr/local/etc/rc.filter_configure does NOT fix my problem.

Code: [Select]
root@OPNsense:~ # ping6 google.de
PING6(56=40+8+8 bytes) 2001:1a50:5105:1::193 --> 2a00:1450:4001:818::2003
^C
--- google.de ping6 statistics ---
2 packets transmitted, 0 packets received, 100.0% packet loss
root@OPNsense:~ # /usr/local/etc/rc.filter_configure
Configuring firewall.......done.
root@OPNsense:~ # ping6 google.de
PING6(56=40+8+8 bytes) 2001:1a50:5105:1::193 --> 2a00:1450:4001:818::2003
^C
--- google.de ping6 statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss
root@OPNsense:~ # pfctl -d
pf disabled
root@OPNsense:~ # pfctl -e
pf enabled
root@OPNsense:~ # ping6 google.de
PING6(56=40+8+8 bytes) 2001:1a50:5105:1::193 --> 2a00:1450:4001:818::2003
16 bytes from 2a00:1450:4001:818::2003, icmp_seq=0 hlim=56 time=14.594 ms
16 bytes from 2a00:1450:4001:818::2003, icmp_seq=1 hlim=56 time=14.431 ms
^C
--- google.de ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 14.431/14.512/14.594/0.081 ms

cheers
Matthias
Title: Re: Strange IPv6 behavior after update
Post by: franco on September 11, 2018, 10:30:46 am
Hi Matthias,

This is strange. Filter configuration includes reloading the filter and would be expected to unblock operation. Disabling and enabling the filter on the other hand should have no visible effect but it looks like it has.

Toggling the filter will remove it from the kernel hooks and push it back it so that would somehow indicate something is blocking flow inside a kernel facility?

Only guessing at this moment in the hopes to get one step closer through discussion or more diagnostics...


Cheers,
Franco
Title: Re: Strange IPv6 behavior after update
Post by: mahescho on September 11, 2018, 03:53:48 pm
Hi Franco,

just let me know what you need  :)

Matthias
Title: Re: Strange IPv6 behavior after update
Post by: Droppie391 on September 12, 2018, 08:12:01 am
Hi Franco,

i installed the patch y´day but when the interface did its reset this morning, the ipv6 default route returned to wan again. i had to set it to pppoe on the console to get ipv6 internet working again.
Title: Re: Strange IPv6 behavior after update
Post by: franco on September 12, 2018, 09:36:56 am
@Matthias

Do you have a "Reload" button under Interfaces: Overview: WAN ? If so, can you try this one instead...

@ Droppie391

Do you have the system logs for this incident? Search for "ROUTING".


Thanks,
Franco
Title: Re: Strange IPv6 behavior after update
Post by: Droppie391 on September 12, 2018, 01:37:40 pm
i will post the log eintries later but found something more disturbing, it looks like the pppoe interface has linked to the wrong hw interface.:

igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
   options=4400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,TXCSUM_IPV6>
   ether 78:24:af:82:a2:28
   hwaddr 78:24:af:82:a2:28
   inet6 fe80::7a24:afff:fe82:a228%igb0 prefixlen 64 scopeid 0x1
igb1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
   options=4400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,TXCSUM_IPV6>
   ether 78:24:af:82:a2:29
   hwaddr 78:24:af:82:a2:29
   inet6 fe80::7a24:afff:fe82:a229%igb1 prefixlen 64 scopeid 0x2
pppoe0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 1492
   inet6 fe80::7a24:afff:fe82:a229%pppoe0 prefixlen 64 scopeid 0x11

igb0 is our wan link, igb1 is our lan interface
in the point2point settings it is set to link to igb0 (see attached image)

so it looks like the routing isn´t the problem at all....


Title: Re: Strange IPv6 behavior after update
Post by: Droppie391 on September 12, 2018, 01:48:35 pm
and here the log-extract (all IP addresses etc masked)
the log looks exactly the same, before and after applying the patch

Sep 12 05:00:00 my_hostname opnsense: /usr/local/etc/rc.configure_interface: Accept router advertisements on interface igb0
Sep 12 05:00:00 my_hostname opnsense: /usr/local/etc/rc.configure_interface: The command '/var/etc/rtsold_igb0_script.sh' returned exit code '1', the output was ''
Sep 12 05:00:00 my_hostname opnsense: /usr/local/etc/rc.configure_interface: ROUTING: entering configure using 'wan'
Sep 12 05:00:00 my_hostname opnsense: /usr/local/etc/rc.configure_interface: ROUTING: IPv4 default gateway set to wan
Sep 12 05:00:00 my_hostname opnsense: /usr/local/etc/rc.configure_interface: ROUTING: IPv6 default gateway set to wan
Sep 12 05:00:00 my_hostname opnsense: /usr/local/etc/rc.configure_interface: ROUTING: setting IPv4 default route to ISP_IPV4_GW
Sep 12 05:00:00 my_hostname opnsense: /usr/local/etc/rc.configure_interface: ROUTING: removing /tmp/pppoe0_defaultgw
Sep 12 05:00:00 my_hostname opnsense: /usr/local/etc/rc.configure_interface: ROUTING: creating /tmp/pppoe0_defaultgw using 'ISP_IPV4_GW'
Sep 12 05:00:00 my_hostname opnsense: /usr/local/etc/rc.configure_interface: The command '/sbin/route add -'inet' default 'ISP_IPV4_GW'' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable add net default: gateway ISP_IPV4_GW fib 0: Network is unreachable'
Sep 12 05:00:00 my_hostname opnsense: /usr/local/etc/rc.configure_interface: ROUTING: skipping IPv6 default route
Sep 12 05:00:03 my_hostname opnsense: /usr/local/etc/rc.configure_interface: The command `/sbin/ifconfig -m 'pppoe0'' failed to execute ifconfig: interface pppoe0 does not exist
Sep 12 05:00:04 my_hostname kernel: ng0: changing name to 'pppoe0'
Sep 12 05:00:04 my_hostname opnsense: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'pppoe0'
Sep 12 05:00:04 my_hostname opnsense: /usr/local/etc/rc.newwanipv6: On (IP address: fe80::aaaa:bbff:fe82:a228) (interface: MY_WAN_ALIAS[wan]) (real interface: pppoe0).
Sep 12 05:00:05 my_hostname opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'pppoe0'
Sep 12 05:00:05 my_hostname opnsense: /usr/local/etc/rc.newwanip: On (IP address: MY_IPV4_GLOBAL_IP) (interface: MY_WAN_ALIAS[wan]) (real interface: pppoe0).
Sep 12 05:00:06 my_hostname opnsense: /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'wan'
Sep 12 05:00:06 my_hostname opnsense: /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to wan
Sep 12 05:00:06 my_hostname opnsense: /usr/local/etc/rc.newwanip: ROUTING: IPv6 default gateway set to wan
Sep 12 05:00:06 my_hostname opnsense: /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to ISP_IPV4_GW
Sep 12 05:00:06 my_hostname opnsense: /usr/local/etc/rc.newwanip: ROUTING: keeping current default gateway 'ISP_IPV4_GW'
Sep 12 05:00:06 my_hostname opnsense: /usr/local/etc/rc.newwanip: ROUTING: skipping IPv6 default route
Title: Re: Strange IPv6 behavior after update
Post by: Droppie391 on September 12, 2018, 01:57:42 pm
here the ppps log for what its worth:

Sep 12 05:00:04 my_hostname ppp: [wan] Bundle: Interface ng0 created
Sep 12 05:00:04 my_hostname ppp: [wan_link0] Link: OPEN event
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: Open event
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: state change Initial --> Starting
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: LayerStart
Sep 12 05:00:04 my_hostname ppp: [wan_link0] PPPoE: Connecting to ''
Sep 12 05:00:04 my_hostname ppp: PPPoE: rec'd ACNAME "isp_pppoe_gw"
Sep 12 05:00:04 my_hostname ppp: [wan_link0] PPPoE: connection successful
Sep 12 05:00:04 my_hostname ppp: [wan_link0] Link: UP event
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: Up event
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: state change Starting --> Req-Sent
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: SendConfigReq #1
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   PROTOCOMP
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MRU 1492
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MAGICNUM 0xdc2033c6
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: rec'd Configure Request #1 (Req-Sent)
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MRU 1492
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   AUTHPROTO CHAP MD5
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MAGICNUM 0xd420a811
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MP MRRU 1524
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   ENDPOINTDISC [LOCAL] 62 72 61 73 66 72 61 34 30 35
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MULTILINKHEADERFMT
Sep 12 05:00:04 my_hostname ppp: [wan_link0]     Not supported
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: SendConfigRej #1
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MP MRRU 1524
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MULTILINKHEADERFMT
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: rec'd Configure Ack #1 (Req-Sent)
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   PROTOCOMP
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MRU 1492
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MAGICNUM 0xdc2033c6
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: state change Req-Sent --> Ack-Rcvd
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: rec'd Configure Request #2 (Ack-Rcvd)
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MRU 1492
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   AUTHPROTO CHAP MD5
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MAGICNUM 0xd420a811
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   ENDPOINTDISC [LOCAL] 62 72 61 73 66 72 61 34 30 35
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: SendConfigAck #2
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MRU 1492
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   AUTHPROTO CHAP MD5
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   MAGICNUM 0xd420a811
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   ENDPOINTDISC [LOCAL] 62 72 61 73 66 72 61 34 30 35
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: state change Ack-Rcvd --> Opened
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: auth: peer wants CHAP, I want nothing
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: LayerUp
Sep 12 05:00:04 my_hostname ppp: [wan_link0] CHAP: rec'd CHALLENGE #1 len: 31
Sep 12 05:00:04 my_hostname ppp: [wan_link0]   Name: "isp_pppoe_gw"
Sep 12 05:00:04 my_hostname ppp: [wan_link0] CHAP: Using authname "my_login_name"
Sep 12 05:00:04 my_hostname ppp: [wan_link0] CHAP: sending RESPONSE #1 len: 40
Sep 12 05:00:04 my_hostname ppp: [wan_link0] CHAP: rec'd SUCCESS #1 len: 4
Sep 12 05:00:04 my_hostname ppp: [wan_link0] LCP: authorization successful
Sep 12 05:00:04 my_hostname ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
Sep 12 05:00:04 my_hostname ppp: [wan_link0] Link: Join bundle "wan"
Sep 12 05:00:04 my_hostname ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Sep 12 05:00:04 my_hostname ppp: [wan] IPCP: Open event
Sep 12 05:00:04 my_hostname ppp: [wan] IPCP: state change Initial --> Starting
Sep 12 05:00:04 my_hostname ppp: [wan] IPCP: LayerStart
Sep 12 05:00:04 my_hostname ppp: [wan] IPV6CP: Open event
Sep 12 05:00:04 my_hostname ppp: [wan] IPV6CP: state change Initial --> Starting
Sep 12 05:00:04 my_hostname ppp: [wan] IPV6CP: LayerStart
Sep 12 05:00:04 my_hostname ppp: [wan] IPCP: Up event
Sep 12 05:00:04 my_hostname ppp: [wan] IPCP: state change Starting --> Req-Sent
Sep 12 05:00:04 my_hostname ppp: [wan] IPCP: SendConfigReq #1
Sep 12 05:00:04 my_hostname ppp: [wan]   IPADDR 0.0.0.0
Sep 12 05:00:04 my_hostname ppp: [wan]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Sep 12 05:00:04 my_hostname ppp: [wan] IPV6CP: Up event
Sep 12 05:00:04 my_hostname ppp: [wan] IPV6CP: state change Starting --> Req-Sent
Sep 12 05:00:04 my_hostname ppp: [wan] IPV6CP: SendConfigReq #1
Sep 12 05:00:04 my_hostname ppp: [wan] IPCP: rec'd Configure Request #1 (Req-Sent)
Sep 12 05:00:04 my_hostname ppp: [wan]   COMPPROTO VJCOMP, 16 comp. channels, allow comp-cid
Sep 12 05:00:04 my_hostname ppp: [wan]   IPADDR ISP_IPV4_GW
Sep 12 05:00:04 my_hostname ppp: [wan]     ISP_IPV4_GW is OK
Sep 12 05:00:04 my_hostname ppp: [wan] IPCP: SendConfigAck #1
Sep 12 05:00:04 my_hostname ppp: [wan]   COMPPROTO VJCOMP, 16 comp. channels, allow comp-cid
Sep 12 05:00:04 my_hostname ppp: [wan]   IPADDR ISP_IPV4_GW
Sep 12 05:00:04 my_hostname ppp: [wan] IPCP: state change Req-Sent --> Ack-Sent
Sep 12 05:00:04 my_hostname ppp: [wan] IPV6CP: rec'd Configure Request #1 (Req-Sent)
Sep 12 05:00:04 my_hostname ppp: [wan] IPV6CP: SendConfigAck #1
Sep 12 05:00:04 my_hostname ppp: [wan] IPV6CP: state change Req-Sent --> Ack-Sent
Sep 12 05:00:04 my_hostname ppp: [wan] IPCP: rec'd Configure Nak #1 (Ack-Sent)
Sep 12 05:00:04 my_hostname ppp: [wan]   IPADDR MY_IPV4_GLOBAL_IP
Sep 12 05:00:04 my_hostname ppp: [wan]     MY_IPV4_GLOBAL_IP is OK
Sep 12 05:00:04 my_hostname ppp: [wan] IPCP: SendConfigReq #2
Sep 12 05:00:04 my_hostname ppp: [wan]   IPADDR MY_IPV4_GLOBAL_IP
Sep 12 05:00:04 my_hostname ppp: [wan]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Sep 12 05:00:04 my_hostname ppp: [wan] IPV6CP: rec'd Configure Ack #1 (Ack-Sent)
Sep 12 05:00:04 my_hostname ppp: [wan] IPV6CP: state change Ack-Sent --> Opened
Sep 12 05:00:04 my_hostname ppp: [wan] IPV6CP: LayerUp
Sep 12 05:00:04 my_hostname ppp: [wan]   aaaa:bbff:fe82:a229 -> 0123:56ff:fe89:abcd
Sep 12 05:00:05 my_hostname ppp: [wan] IFACE: Up event
Sep 12 05:00:05 my_hostname ppp: [wan] IFACE: Rename interface ng0 to pppoe0
Sep 12 05:00:05 my_hostname ppp: [wan] IPCP: rec'd Configure Ack #2 (Ack-Sent)
Sep 12 05:00:05 my_hostname ppp: [wan]   IPADDR MY_IPV4_GLOBAL_IP
Sep 12 05:00:05 my_hostname ppp: [wan]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Sep 12 05:00:05 my_hostname ppp: [wan] IPCP: state change Ack-Sent --> Opened
Sep 12 05:00:05 my_hostname ppp: [wan] IPCP: LayerUp
Sep 12 05:00:05 my_hostname ppp: [wan]   MY_IPV4_GLOBAL_IP -> ISP_IPV4_GW
Title: Re: Strange IPv6 behavior after update
Post by: mahescho on September 12, 2018, 05:34:43 pm
@Matthias

Do you have a "Reload" button under Interfaces: Overview: WAN ? If so, can you try this one instead...


There is no "Reload" button ...
Title: Re: Strange IPv6 behavior after update
Post by: mahescho on September 18, 2018, 08:33:06 pm
I've disconnected the WAN port an reconnected it with the same result. IPv6 stopped working.
Title: Re: Strange IPv6 behavior after update
Post by: Droppie391 on September 19, 2018, 08:55:26 am
concerning my problem, i enabled the "Use IPv4 Connection" option and now it works.
The help text was a bit confusing here, following the code in "function get_real_interface"

                    default:
                        switch ($cfg['ipaddr']) {
                            case 'pppoe':
                            case 'ppp':
                            case 'l2tp':
                            case 'pptp':
                                if (isset($cfg['dhcp6usev4iface'])) {
                                    $wanif = $cfg['if'];
                                } else {
                                    $parents = get_parent_interface($interface);
                                    if (!empty($parents[0])) {
                                        $wanif = $parents[0];
                                    } else {
                                        $wanif = $cfg['if'];
                                    }
                                }
                                break;

where the parent interface is selected in stead of the pppoe interface without the option set, it appears to affect the routing table too.

Problem solved, my case is closed.
Title: Re: Strange IPv6 behavior after update
Post by: mahescho on September 19, 2018, 07:53:45 pm
Tested to enable "Use IPv4 Connection". Didn't fix my problem.
Title: Re: Strange IPv6 behavior after update
Post by: franco on October 01, 2018, 03:46:11 pm
"Use IPv4 Connection" is not useful if your connection is already working sometimes.

It's really strange to have the firewall toggle to reenable packet flow. This is only for IPv6, right? Do you see blocks in the firewall log when the traffic is "stuck"?
Title: Re: Strange IPv6 behavior after update
Post by: mahescho on December 01, 2018, 09:37:28 am
Just for the record: This still does not work as expected ...
Title: Re: Strange IPv6 behavior after update
Post by: mahescho on December 05, 2018, 07:22:32 pm
Solution:

https://github.com/opnsense/core/issues/3015
Title: Re: Strange IPv6 behavior after update
Post by: mahescho on December 06, 2018, 07:32:19 pm
Final fix:

https://github.com/opnsense/core/commit/c3213d4d918e0675478feda494dc385ae6ccecd1