Pace IPv6 Settings

Internet access discussion, including Fusion, IP Broadband, and Gigabit Fiber!
15 posts Page 2 of 2
by adame » Tue Dec 23, 2014 11:27 am
abfeldman wrote:I have also enabled IPv6 ready. First problem is I cannot figure out how to configure firewall via the PACE 4111N-030 modem. Does this mean that the whole IPv6 network is wide-open? Not a big problem because I have an extra IPv6 firewall on each host but...
We apologize for the lack of a configurable IPv6 firewall on the Pace 4111N. The firewall is in place, but is not configurable due to limitations of the device. This means features like port forwarding and DMZ will never work for 6RD until we move on from the 4111N. For customers who wish to run IPv6-addressable servers from behind the Pace, our IPv6 Tunnel feature is still the only option.
abfeldman wrote: The second problem is with the MTU. When I go to http://test-ipv6.com/ it tells me I have problems with large packets.
This was due to a problem with the 6RD gateway. We believe it should be fixed now.
abfeldman wrote: The third problem is that traceroute from my Linux hosts does not work. Seems like a modem ping6 firewall issue.
Can you post an example? I've been able to issue successful v6 traceroutes from behind the modem.
Adam Martinetti
Customer Experience Manager
Sonic.
by abfeldman » Sat Dec 27, 2014 1:13 pm
Thanks a ton. I think I understand what is going on. The problem is in the firewall and the ICMPv6 being blocked. I think I am going to shop around for an ADSL model that has a good support for OpenWRT. I ordered a chepish Netgear DGN2200 modem from Amazon but it sux the same way the Pace modem you guys distribute, so I am returning it. Believe it or not the Germans make a good ADSL modem:

http://en.avm.de/products/fritzbox/

But it is hard to find in the US and it is far too expensive. I will let you know once I know more.

Happy holidays!
by dane » Sat Dec 27, 2014 2:29 pm
The AVM Fritzbox is a neat router, but it's not certified for use in the US.
Dane Jasper
Sonic
by Guest » Sun Dec 28, 2014 3:15 am
adame wrote:
abfeldman wrote:I have also enabled IPv6 ready. First problem is I cannot figure out how to configure firewall via the PACE 4111N-030 modem. Does this mean that the whole IPv6 network is wide-open? Not a big problem because I have an extra IPv6 firewall on each host but...
We apologize for the lack of a configurable IPv6 firewall on the Pace 4111N. The firewall is in place, but is not configurable due to limitations of the device. This means features like port forwarding and DMZ will never work for 6RD until we move on from the 4111N. For customers who wish to run IPv6-addressable servers from behind the Pace, our IPv6 Tunnel feature is still the only option.
abfeldman wrote: The second problem is with the MTU. When I go to http://test-ipv6.com/ it tells me I have problems with large packets.
This was due to a problem with the 6RD gateway. We believe it should be fixed now.
abfeldman wrote: The third problem is that traceroute from my Linux hosts does not work. Seems like a modem ping6 firewall issue.
I also have problems tracerouting google.com over IPv6. Also, the maximum MTU I could get over IPv6 is 1232; encapsulation overhead can't account for that unless multiple encapsulations are being done.
Can you post an example? I've been able to issue successful v6 traceroutes from behind the modem.
by Guest » Sun Jan 18, 2015 9:56 pm
For the past couple of days, I have a lot of difficulty with connectivity to Google sites. I have been unable to get the Play Store to load at all, and even simply connecting to google.com would take a long time. Third party sites that depend on some Google element were also being delayed, including Sonic's forums (I think it was "apis.google.com" that was being shown as the thing that was holding up the page load). I tried to run a tracert to google.com and the only thing that didn't time out was the first line, which included something about 6rd and IP6. I checked my Member Settings as directed in this thread, found that the IP6 option was enabled (I don't remember if I personally enabled this at some point or not), changed it to disabled, and now my Google connectivity seems to be restored.
15 posts Page 2 of 2