Since updating from ER605 from 2.2.2 to 2.2.4, I have had IPv6 issues.

Locally, it is an only IPv4 network. 
The modem only issues an IPv4 address,
The internet/WAN is set to IPv4 only.

Since the update, every box on the network seems to want an IPv6 address (see below).  Despite incoming IPv6 being set to be blocked by default on firmware 2.2.3.
This seems like an extreme oxymoron for the network to enable it, but block all incoming.

This conflict is creating issues espeacilly with cURL.  Any update service or serve-server communication that relies on cURL fails.

I have tried to allow incoming IPV6 traffic to the WAN in ACL rules.  No affect.
I have tried settings/internet/wan and adding IPv6 options, but all fail.  My ISP does not assign an IPv6.

The only work arounds I have found to specificy each addess in a /etc/hosts or to revert the firmware (and not get all future security updates.)
 

Maybe I'm missing something easy, but I could use some help getting the network back on track.
Thanks!

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 94:de:h0:24:39:75 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.35/24 brd 10.0.0.245 scope global enp3s0
       valid_lft forever preferred_lft forever
    inet6 fe80::96de:80jf:fe14:8975/64 scope link
       valid_lft forever preferred_lft forever