![]() ![]() ![]() ![]() |
|
So seems the beta test is more about getting the various types of devices working!
Not sure what else to test as everything seems to work as expected?
Anyone else had any issues outside actually getting started with their modem/router?
CPU: AMD 5900x | RAM: GSKILL Trident Z Neo RGB F4-3600C16D-32GTZNC-32-GB | MB: Asus X570-E | GFX: EVGA FTW3 Ultra RTX 3080Ti| Monitor: LG 27GL850-B 2560x1440
Quic: https://account.quic.nz/refer/473833 R473833EQKIBX
I've not had many issues at all once I was able to get it up and working. The only current issue I'm having is a peering issue to gfycat.com
It takes quite a while for any gifs to load over ipv6 (on ipv4 through a vpn they load normally).
I did a traceroute but I believe this may be on their side, not bigpipes.
ZL2TOY/ZL1DMP
mentalinc:
So seems the beta test is more about getting the various types of devices working!
Not sure what else to test as everything seems to work as expected?
Anyone else had any issues outside actually getting started with their modem/router?
it's all about sniff testing. Internal tests may expose 95% of bugs, but its not until all the techys start picking up that say a bug in the setup arises.
Being that your targeting the techy bunch, they can be an asset in platform testing before rolling out to everyone.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
mentalinc:
So seems the beta test is more about getting the various types of devices working!
Not sure what else to test as everything seems to work as expected?
Anyone else had any issues outside actually getting started with their modem/router?
Yep. We're looking for any troubles that come up from a user point of view. Any problem devices we can find about before full launch = an advantage to our support team.
Apart from those using pfSense, thus far most testers seem to be up and running as expected after the switch has been flicked.
As for Gfycat, it does look like this is/was something on their end. I can't seem to resolve their domains over v6 at the moment, and their service seems to be working on a test line right now. Perhaps they were testing something?
If anyone encounters odd troubles with any specific website or service do let us know in this thread so that we can investigate.
IPv6pipe:
As for Gfycat, it does look like this is/was something on their end. I can't seem to resolve their domains over v6 at the moment, and their service seems to be working on a test line right now. Perhaps they were testing something?
If anyone encounters odd troubles with any specific website or service do let us know in this thread so that we can investigate.
Gfycat eventually loads, but it definitely looks like something on their end. I brought it up on Reddit on the ipv6 sub, and others reported the same issue trying to reach it over ipv6 in the US. Seems to be a cloudfront issue. People are unable to go to the site directly using their ipv6 address as well. http://[2600:9000:2033:7e00:d:a332:70c5:88c1]
Thankfully everything else has been playing quite nicely so far.
ZL2TOY/ZL1DMP
IPv6pipe:
If anyone encounters odd troubles with any specific website or service do let us know in this thread so that we can investigate.
Just for the record so it's included - I know a) I've mentioned this before, b) this is a beta and c) you've specifically said you're not supporting reverse DNS and delegation for IPv6 at the moment, so this isn't a moan at this point - Google are very sniffy about receiving mail from IPv6 hosts with missing or improper PTR records, which to my mind makes this must-have functionality when you deploy IPv6 to everyone.
Since I run a (very) low traffic mail server on my network, I think it qualifies as trouble with a specific service.
Detruire:
One router firmware upgrade later and I'm connected again. The old version had a bug that stopped IPv6 settings from being saved.
Very easy with Advanced Tomato
Working fine here too on Advanced Tomato 132. Very easy. Changed settings and rebooted. Didn't have to do a thing with the bridged Vigor 130.
MrTomato:IPv6pipe:If anyone encounters odd troubles with any specific website or service do let us know in this thread so that we can investigate.
Just for the record so it's included - I know a) I've mentioned this before, b) this is a beta and c) you've specifically said you're not supporting reverse DNS and delegation for IPv6 at the moment, so this isn't a moan at this point - Google are very sniffy about receiving mail from IPv6 hosts with missing or improper PTR records, which to my mind makes this must-have functionality when you deploy IPv6 to everyone.
Since I run a (very) low traffic mail server on my network, I think it qualifies as trouble with a specific service.
OmniouS:
It's never a good idea to send email from residential IP ranges
It's never a good idea to say never when it comes to either technical or usage based workflows ;)
OmniouS:
I don't think reverse DNS delegation or management is a necessary offering from a consumer ISP.
It's never a good idea to send email from residential IP ranges
You should relay through a third party smart host instead
Or if you really want to send direct, perhaps ISPs could configure the authoritative DNS servers for their residential IP ranges to return a pattern when queried e.g. a.b.c.d-cust.bigpipe.co.nz or similar. Then just change your smtp host ID to match. Once set up this would require no extra work from the ISP
I disagree. It's not the place of the ISP to dictate how a customer uses their connections. We pay for Internet Service, not glorified Web services. A reverse delegation is essential to fully make use of Internet services. The fact that a user requires this functionality should not automatically push them in to the realm of business (and over-priced) connections.
There is no reason to pay for, or trust mail services to a third party when you can do it yourself. I have run my own mail servers for around 15 years, always on residential connections, and always on ISPs that implemented reasonable policies, such as not rate limiting non-Web traffic. I'm not about to change that and give up control of my mail to Google. Google are evil.
Many SMTP servers drop connections based on HELO/EHLO not matching the PTR, or the use of address literals - a practice which is explicitly prohibited by RFC 821. Matching the PTR and HELO is therefore essential. Simply changing it to match what the ISP has set is a hack (note, Bigpipe does not set the PTR by default, which is worse than an arbitrary PTR), and is also likely to lead to over-zealous rules blocking legitimate mail either based on the PTR including an IP address, or on the domains not matching, both of which I have seen in mail filtering rule sets.
Simply setting the delegation once, and only for those who request it, would require no further work for the ISP. That's equivalent to setting the PTR for IPv4, which Bigpipe will do if requested. A consistent approach is best.
Those who need the ability to set PTR records should make it known (as have I, and a few others over the couple of years), but I would prefer we didn't turn this thread in to a debate on the matter.
OmniouS:
It's never a good idea to send email from residential IP ranges
The whole concept of accepting or denying access or making assumptions based on an IP address is an unreliable bodge with IPv4 and a fool's errand under IPv6 simply because there are too many addresses to account for. Furthermore, in my experience I've not found static IPv4 addresses supplied by NZ consumer ISPs (in NZ at least) to be classified by anyone as residential.
OmniouS:
Or if you really want to send direct, perhaps ISPs could configure the authoritative DNS servers for their residential IP ranges to return a pattern when queried e.g. a.b.c.d-cust.bigpipe.co.nz or similar. Then just change your smtp host ID to match. Once set up this would require no extra work from the ISP
Certainly. Or Bigpipe could take the early initiative to allow customers to set up delegation through their control panel, and hopefully the allocation of 'proper' static IPv6 prefixes too, and reap the dividends of cementing their lead as the go-to ISP for experts and enthusiasts in this country.
Edit: I'll leave it at that - as Sir Humph said, it's better that this thread not be turned into a debate about the issue.
All very valid points thanks. If Bigpipe offered reverse delegation or DNS mangement, I'd definitely set mine, if only to make traceroutes look a bit nicer :)
The main reason I said that it wasn't a good idea to send from residential ranges was that there are a few overzealous providers who will block entire ranges at the drop of a hat. Consumers are more likely to have their connections abused, leading to this - it actually happened to me a few years ago
1xnRWP:
Device - Ubiquiti Edgerouter Lite
Getting there, but some weird issues.
dhcp6-pd is set up and interfaces now has the correct ipv6 address, clients are getting addresses via SLAAC but I don't seem to have any routability...
Config:
Should have read Page 2 or looked at the Edgerouter Tutorial I've got :)
You're missing the default route - look here: http://www.geekzone.co.nz/forums.asp?forumid=158&topicid=210440&page_no=3#1749119
Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)
Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.
michaelmurfy:
1xnRWP:
Device - Ubiquiti Edgerouter Lite
Getting there, but some weird issues.
dhcp6-pd is set up and interfaces now has the correct ipv6 address, clients are getting addresses via SLAAC but I don't seem to have any routability...
Config:
Should have read Page 2 or looked at the Edgerouter Tutorial I've got :)
You're missing the default route - look here: http://www.geekzone.co.nz/forums.asp?forumid=158&topicid=210440&page_no=3#1749119
Ahhh, so I am! Thank you. I also missed the pppoe ipv6 config as well, but after your post above I'm up and running.
I did try searching, but without a per-thread search it's a bit confusing.
|
![]() ![]() ![]() ![]() |