![]() ![]() ![]() ![]() |
|
Brumfondl:
MrTomato:
Congratulations - you're officially the first person in the history of the universe to have a problem solved by ripping out Intel NICs and putting in Realtek!
I realise there is rampant sarcasm involved in your post but I am not sure which way it is going. Can I assume that it is normally a Realtek card that is at fault and an Intel one solves the issue or is it the other way round?
Sorry, didn't mean to offend. It's just funny - it's literally the first time I've ever heard of a Realtek NIC working well when an Intel one didn't! [Edit: In my experience the usual problem with Realtek NICs are the drivers. It could be that they've finally got them sorted out after all these years.]
Seriously, though - if it's worked out for you, that's excellent. Full marks to Realtek.
MrTomato:
Sorry, didn't mean to offend. It's just funny - it's literally the first time I've ever heard of a Realtek NIC working well when an Intel one didn't! [Edit: In my experience the usual problem with Realtek NICs are the drivers. It could be that they've finally got them sorted out after all these years.]
Seriously, though - if it's worked out for you, that's excellent. Full marks to Realtek.
I assumed you meant no offense so no worries there :) I am actually just using the default Microsoft drivers. They seem to work fine enough for the moment.
So I had hoped to test the "disable gateway monitoring" on pfsense last night but didn't get far enough...
I wasn't able to get an ipv6 address assigned by Bigpipe. Was only seeing a fe80 link local address on the WAN interface, even after reboots and the pfsense 2.4 patch update.
Resnick:
So I had hoped to test the "disable gateway monitoring" on pfsense last night but didn't get far enough...
I wasn't able to get an ipv6 address assigned by Bigpipe. Was only seeing a fe80 link local address on the WAN interface, even after reboots and the pfsense 2.4 patch update.
A link-local address on the WAN interface is normal if you have 'Request only an IPv6 prefix' selected. Check your LAN interface
My fibre should be operational on Wed so I'll try my current install which is reasonably stable with v6 on ADSL. It doesn't always come up after the box or WAN interface restarts though. Logging didn't give me any clues as to why
Resnick:
So I had hoped to test the "disable gateway monitoring" on pfsense last night but didn't get far enough...
I wasn't able to get an ipv6 address assigned by Bigpipe. Was only seeing a fe80 link local address on the WAN interface, even after reboots and the pfsense 2.4 patch update.
Sadly, this seems to be what the rest of us are seeing when using pfSense, on UFB at least.
If you check the PPP logs, you will likely see a message along the lines of ... unexpected protocol IPv6... I have tried many tweaks listed here and elsewhere on the internet with no lasting results. Every now and then (well, only once in my case) a v6 address is assigned correctly - no address to pfsense itself, but correct addresses to LAN clients - but that doesn't persist after a reboot.
I assume it's some strange incompatibility with the way that pfSense requests information from BigPipe or vice versa.
I did a quick test with a Sophos VM that I also had setup. It was correctly allocated a v6 address (to the firewall itself), but it doesn't support DHCP-PD so no addresses could be allocated to LAN clients.
So, not an issue with the connection, but something strange happening specifically with pfSense.
OmniouS:
A link-local address on the WAN interface is normal if you have 'Request only an IPv6 prefix' selected. Check your LAN interface
My fibre should be operational on Wed so I'll try my current install which is reasonably stable with v6 on ADSL. It doesn't always come up after the box or WAN interface restarts though. Logging didn't give me any clues as to why
Thanks for the input. I had left 'Request only an IPv6 prefix' unticked as per SirHumphreyAppleby and my own previous brief moment of success. Still feling my way through pfsense and I have no previous experience with ipv6 so there will be a lot of trial and even more error.
EDIT: missing "unticked"
random173:
If you check the PPP logs, you will likely see a message along the lines of ... unexpected protocol IPv6... I have tried many tweaks listed here and elsewhere on the internet with no lasting results. Every now and then (well, only once in my case) a v6 address is assigned correctly - no address to pfsense itself, but correct addresses to LAN clients - but that doesn't persist after a reboot.
Yep, same experience and logs here.
Can we still get in on this?
Looks like the IPV6pipe account hasn't been used in a while
Wervie67:
Can we still get in on this?
Looks like the IPV6pipe account hasn't been used in a while
Sure can. The account is still active and we'll respond to queries on it, but as per the blog post we can now handle queries via our standard troubleshooting.
https://www.facebook.com/BigPipeNZ
https://twitter.com/BigPipeNZ
How long is the wait to be put on the beta?
My PM doesn't appear to have been read yet, I've also requested it via email to support on the back of an open ticket which still hasn't been replied to a week after.
I do appreciate this is a courtesy and not a right.
Thanks.
bayofislands:How long is the wait to be put on the beta?
My PM doesn't appear to have been read yet, I've also requested it via email to support on the back of an open ticket which still hasn't been replied to a week after.
I do appreciate this is a courtesy and not a right.
Thanks.
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:bayofislands:
How long is the wait to be put on the beta?
My PM doesn't appear to have been read yet, I've also requested it via email to support on the back of an open ticket which still hasn't been replied to a week after.
I do appreciate this is a courtesy and not a right.
Thanks.
It is a beta and from what I recall there are very few guys who can physically provision IPv6 right now. Be patient, it'll come when they get around to it but you've also got to remember activating somebody for IPv6 is far less important than fixing s fault.
Murph's right, but I'm keen to get this sorted for you. No reason I know of that we can't add you to the beta. As it's Friday and the relevant staff are not on site right now I'll get on to this ASAP from Monday.
https://www.facebook.com/BigPipeNZ
https://twitter.com/BigPipeNZ
I understand that; it was really in frustration to the lack of response to a support request a week ago to explain the periodic 3 second entries filling up my router logs:
. . . WAN1 PPPoE <== Protocol:IPv6CP(8057) ConfReq Identifier:0xE1 Interface Identifier: . . .
As IPv6 was disabled on the router I use, Draytek Vigor 2710Dvn, I wanted to find out why I was getting the continuous requests.
I did get an initial response from BigPipe last Friday that someone would look into it the following week, but I received no further response. So I have enable IPv6 on my Router and requested to go on the BigPipe Beta to see if I can resolve the issue.
Thanks for your quick response.
Thanks Josh - my reply above to Michael was before I saw your response.
|
![]() ![]() ![]() ![]() |