IPv6 beta for Bigpipe

Forums › Spark New Zealand (including Skinny and BigPipe) › IPv6 beta for Bigpipe

1 | ... | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29

742 posts

Ultimate Geek

ID Verified

Trusted

#1843506 10-Aug-2017 12:54

SirHumphreyAppleby:

lucky015:

Yep, Logs below seem to indicate some form of permission denied so I'm assuming it's falling outside of some of the normal parameters but I'll upgrade anyway, Just been making the backups, etc

How did your upgrade go? I've been updating in the 2.4 branch regularly, but after upgrading again this morning, my connection seems unreliable.

@Bigpipe - are there presently connectivity issues?

Updated successfully to 2.4.0.b.20170808.1459 and IPv4 has been fine however IPv6 is still the same as it was before, I got busy at work yesterday so didn't get a chance to do much more but I'll take a closer look shortly and double check to see if part of the config didn't make it through the upgrade. Will check the logs, etc.

Edit: Also seems to have corrected an inexplicable issue with decreased throughput between the host and VM I was having before with 2.3 so I'm really happy with 2.4 overall.

Tradepub

Free professional, reference and technical white papers (affiliate link).

SirHumphreyAppleby

2830 posts

Uber Geek

#1843570 10-Aug-2017 14:19

lucky015:

Updated successfully to 2.4.0.b.20170808.1459 and IPv4 has been fine however IPv6 is still the same as it was before, I got busy at work yesterday so didn't get a chance to do much more but I'll take a closer look shortly and double check to see if part of the config didn't make it through the upgrade. Will check the logs, etc.

Edit: Also seems to have corrected an inexplicable issue with decreased throughput between the host and VM I was having before with 2.3 so I'm really happy with 2.4 overall.

My upgrade this morning was to 2.4.0.b.20170809.1306. With that build, it was IPv4 I was having the most difficulty with. IPv6 seemed to keep working when IPv4 failed, and port mappings worked intermittently. There was a configuration version bump since the last build I installed, but a revert to pre-upgrade rules and a factory reset didn't get things running. I was careful to not shut down the system, as it's a VM, and I wanted to rule out hardware issues (in particular anything to do with PCI passthrough). Once I had exhaused all software possibilities, I shutdown the host, and problems persisted. Looks like a buggy build, but I can't be certain of that yet. I will report back if I have further issues now that I have a clean install... of OPNsense 17.7 (Release build), which now also seems to work with IPv6.

With OPNsense, you need to use the "Directly send SOLICIT" option, which appears to do the same thing as "Do not wait for a RA" on pfSense.

EDIT: It was actually my intention to move to OPNsense in the long term, so I will be sticking with it, however I will still do my best to assist with pfSense issues.

OmniouS

423 posts

Ultimate Geek

Trusted

Lifetime subscriber

#1843644 10-Aug-2017 16:11

SirHumphreyAppleby:

lucky015:

Updated successfully to 2.4.0.b.20170808.1459 and IPv4 has been fine however IPv6 is still the same as it was before, I got busy at work yesterday so didn't get a chance to do much more but I'll take a closer look shortly and double check to see if part of the config didn't make it through the upgrade. Will check the logs, etc.

Edit: Also seems to have corrected an inexplicable issue with decreased throughput between the host and VM I was having before with 2.3 so I'm really happy with 2.4 overall.

My upgrade this morning was to 2.4.0.b.20170809.1306. With that build, it was IPv4 I was having the most difficulty with. IPv6 seemed to keep working when IPv4 failed, and port mappings worked intermittently. There was a configuration version bump since the last build I installed, but a revert to pre-upgrade rules and a factory reset didn't get things running. I was careful to not shut down the system, as it's a VM, and I wanted to rule out hardware issues (in particular anything to do with PCI passthrough). Once I had exhaused all software possibilities, I shutdown the host, and problems persisted. Looks like a buggy build, but I can't be certain of that yet. I will report back if I have further issues now that I have a clean install... of OPNsense 17.7 (Release build), which now also seems to work with IPv6.

With OPNsense, you need to use the "Directly send SOLICIT" option, which appears to do the same thing as "Do not wait for a RA" on pfSense.

EDIT: It was actually my intention to move to OPNsense in the long term, so I will be sticking with it, however I will still do my best to assist with pfSense issues.

It's worth noting for other readers trying pfSense that the 'Do not wait for RA' setting is only meant to be used with an IPoE connection, not PPPoE

SirHumphreyAppleby

2830 posts

Uber Geek

#1843656 10-Aug-2017 16:33

SirHumphreyAppleby:

My upgrade this morning was to 2.4.0.b.20170809.1306. With that build, it was IPv4 I was having the most difficulty with.

Sorry for yet another post. I just wanted to give a quick update on this issue, as I think the problems I've had today won't be relevant to others.

I ran in to the same problem with OPNsense 17.7, which suggests the issue is probably due to an update in the base system (either that or a hardware fault). I'm temporarily back on pfSense 2.3.4 (no IPv6) just to ensure everything runs smoothly.

In case it's related to changes in the base system, I'm running pfSense/OPNsense under ESXi, with one E1000 virtual interface, and one Intel 82574L configured for PCI passthrough. Significant issues with the em driver (both cards) seem unlikely, so my issues are more likely related to virtualisation. If you're on real hardware, hopefully the 2.4 branch will continue working for you.

lucky015

742 posts

Ultimate Geek

ID Verified

Trusted

#1843661 10-Aug-2017 16:39

SirHumphreyAppleby:

SirHumphreyAppleby:

My upgrade this morning was to 2.4.0.b.20170809.1306. With that build, it was IPv4 I was having the most difficulty with.

Sorry for yet another post. I just wanted to give a quick update on this issue, as I think the problems I've had today won't be relevant to others.

I ran in to the same problem with OPNsense 17.7, which suggests the issue is probably due to an update in the base system (either that or a hardware fault). I'm temporarily back on pfSense 2.3.4 (no IPv6) just to ensure everything runs smoothly.

In case it's related to changes in the base system, I'm running pfSense/OPNsense under ESXi, with one E1000 virtual interface, and one Intel 82574L configured for PCI passthrough. Significant issues with the em driver (both cards) seem unlikely, so my issues are more likely related to virtualisation. If you're on real hardware, hopefully the 2.4 branch will continue working for you.

I'm happy to report that I'm now seeing an active IPv6 Gateway as well as receiving IPv6 addresses to my devices, It appears to have started working on its own without any changes over the last few hours for me but I cant explain what fixed it as I hadn't made any significant changes since yesterday. I'll try check the logs a little later on.

SirHumphreyAppleby

2830 posts

Uber Geek

#1843698 10-Aug-2017 18:04

lucky015:

I'm happy to report that I'm now seeing an active IPv6 Gateway as well as receiving IPv6 addresses to my devices, It appears to have started working on its own without any changes over the last few hours for me but I cant explain what fixed it as I hadn't made any significant changes since yesterday. I'll try check the logs a little later on.

The test will be if it still works after a reboot. I managed to get an IP address a few times, although no traffic flowing. Some of the workarounds for various issues involved simply changing settings, which cause the interface to be configured in a slightly different way/order.

SirHumphreyAppleby

2830 posts

Uber Geek

#1845356 11-Aug-2017 20:00

Sorry @Bigpipe, I think your graphs lied :) Something outside of my control appears to have been causing connectivity issues yesterday. Revisiting the configurations today, I've experienced no issues.

I am now going to declare the following configurations working with Bigpipe and IPoE:

pfSense 2.4 amd64 (recent beta builds)
OPNsense 17.7 amd64 (release build)

Settings as posted at the bottom of page 22.

IPv6pipe

98 posts

Master Geek

Trusted

BigPipe

#1846156 14-Aug-2017 08:59

Sorry to hear. If you experience any trouble getting online at all, your best bet is to submit a support ticket via https://www.bigpipe.co.nz/contact-us - this way it can be tracked and investigated.

As a reminder: IPoE is not our officially supported protocol, and as such we cannot guarantee it will work at all times.

SirHumphreyAppleby

2830 posts

Uber Geek

#1854847 29-Aug-2017 15:26

I lost IPv6 connectivity after my plan was upgraded to gigabit last week. I had been successfully using OPNsense 17.7 prior to the upgrade, with IPv6 persisting after reboots.

IPv6 was removed and reprovisioned by support, but it's still no go here after numerous reboots (delayed as I am presently reseeding my CrashPlan backup). Support suggested any follow-up be through Geekzone, which is why I'm posting about the issue here. Hopefully it's just a trivial little detail causing issues. No configuration changes on my end.

ref:_00D90oVYy._5006F1SG4mw

IPv6pipe

98 posts

Master Geek

Trusted

BigPipe

#1854884 29-Aug-2017 16:29

SirHumphreyAppleby:

I lost IPv6 connectivity after my plan was upgraded to gigabit last week.

There's an email waiting for you. :)

bayofislands

10 posts

Wannabe Geek

#1859194 5-Sep-2017 19:05

Is there any progress on the HG659 as per http://pages.bigpipe.co.nz/ipv6-on-bigpipe/

Modems/routers that work with IPv6 on Bigpipe, but have some bugs: Huawei HG659

As it's the router of choice for vodafone, spark & bigpipe, and I have one as a backup, it would be cool to have definitive firmware and config available for ipv6 from spark/bigpipe, a ground zero if you like that does everything as it should.

What are the "some bugs" exactly?

Thanks,

Paul.

DarkShadow

1647 posts

Uber Geek

#1859204 5-Sep-2017 19:39

bayofislands:

Is there any progress on the HG659 as per http://pages.bigpipe.co.nz/ipv6-on-bigpipe/

Modems/routers that work with IPv6 on Bigpipe, but have some bugs: Huawei HG659

As it's the router of choice for vodafone, spark & bigpipe, and I have one as a backup, it would be cool to have definitive firmware and config available for ipv6 from spark/bigpipe, a ground zero if you like that does everything as it should.

What are the "some bugs" exactly?

Thanks,

Paul.

I've posted on the first page a workaround.

kiwicam

136 posts

Master Geek

#1859206 5-Sep-2017 19:43

DarkShadow:

bayofislands:

Is there any progress on the HG659 as per http://pages.bigpipe.co.nz/ipv6-on-bigpipe/

Modems/routers that work with IPv6 on Bigpipe, but have some bugs: Huawei HG659

As it's the router of choice for vodafone, spark & bigpipe, and I have one as a backup, it would be cool to have definitive firmware and config available for ipv6 from spark/bigpipe, a ground zero if you like that does everything as it should.

What are the "some bugs" exactly?

Thanks,

Paul.

I've posted on the first page a workaround.

I'm running a Vodafone HG659 with BigPipe's firmware and it's working great.

I used @DarkShadow's workaround but found that the Prefix was a required field. Just check your "Internet" tab and copy and paste the prefix obtained there - dropping the /64 from the end.

bayofislands

10 posts

Wannabe Geek

#1859210 5-Sep-2017 19:58

Thanks Caminham - I was just wondering what BigPipe's progress was on the:

"we’ve identified some IPv6 bugs with our modem that we’re working with the vendor to get sorted"

What the bugs were and whether there might be a release to ipv6 beta testers of updated firmware and config.

kiwicam

136 posts

Master Geek

#1859221 5-Sep-2017 20:28

bayofislands:

Thanks Caminham - I was just wondering what BigPipe's progress was on the:

"we’ve identified some IPv6 bugs with our modem that we’re working with the vendor to get sorted"

What the bugs were and whether there might be a release to ipv6 beta testers of updated firmware and config.

Looks like the firmware on the site now is the same one I downloaded in June. @IPv6pipe - any updates on the way??

Just to re-iterate, it's been rock solid on the current firmware once the above workarounds have been used configuring it.

1 | ... | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29