oh well i don't understand chinese haha. I need to login to access the link you provided

can look at Yanling brand as well from AliExpress.
https://m.aliexpress.com/store/v3/home.html...ePath=index.htm

OEM brand for Protectli

Special thanks to papyrous as sharing the ipv6 configuration for opnsense, tested working with maxis fibre with new box

I use IPv6 to put some hexspeak:







My /64:


My Server Address: [2001:d08:e6:7a1b:dead:daff:feed:f00d]:8080

This post has been edited by Anime4000: Nov 12 2021, 09:55 PM

noice. man of culture

This post has been edited by papyrous: Nov 13 2021, 06:50 PM

rajin bos setup haha. Me myself just use EUI64 to configure for the interface

yeah, just to mess with sysadmin, tracker to show not regular user xD

yes, I use EUI64 to make static IPv6
just get creative around ff:fe

sorry, a bit confused. i'm using pfsense fyi.

has the settings to enable ipv6 for tmnut unifi been updated from this article?
https://advanxer.com/blog/2015/03/configuri...on-pfsense/amp/


in the article they mention using dhcpv6, but comments here seem to allude that this is no longer the recommended setting?

IPv6 PPPoE has 2 type of Address

1. PPPoE Interface Address (/128)
This address is use for Router only

2. Prefix Address
This address for LAN use, it hand out address prefix (2001:a:b:c: and prefix length (/64)

for PPPoE, must use DHCPv6 to obtain:
1. Interface Address
2. Address Prefix
3. Prefix Length

For LAN IPv6 distribution, use NDP

if you have /60 - /48 Prefix Length, then you can use DHCPv6 Server to hand out LAN IPv6, this way you can have extended or more subnet's

hm.....

i sorta get what ur saying, but trying to translate that to how to configure pfsense to work with tmnut unifi ipv6 is a separate matter xd whether i managed to configure as u mentioned.

i mostly use this as a clue by the ts
https://forum.lowyat.net/topic/5204701







as for the lan, all i could find was the dhcpv6 server RA, which i enabled.

Then i tested on mobile android, now ipv6 works whereas before it didn't.

I'm assuming this is the NDP you were talking about? cause thats the only option i could find in pfsense :{


from desktop, i get a 8/10 score here (the 2 parts it said had issue with was dns, and ICMP. for the dns portion, there is no dns hostname shown, not sure why )

https://ipv6-test.com/



and a perfect score here

https://ipv6test.google.com/
https://test-ipv6.com/

This post has been edited by Moogle Stiltzkin: May 22 2022, 12:21 PM

Yes you are right, it should be under Router Advertisements.
using Stateless DHCP correct?

looking at netgate docs under DHCPv6/RA there’s a part about being unable to receive DNS info, can see if that helps solve it

yes, u mentioned stateless so i set it to that in pfsense.

since ur using opnsense, so i then had to translate ur suggestion and make guesses what options these were in pfsense and adjust accordingly.

not sure about dns info but the internet works.

in ipv6 test i got a 8/10 rating in one of them. but in another site it was 10/10 no issues. google ipv6 also no issues. i also tested on mobile android and ipv6 seems to work from there (i noticed that mobiel android ipv6 only worked after i enabled the DHCPv6 RA. but if u don't, then seems only the desktop pc worked for ipv6 only )

So funny thing happened, updated to 22.1.9 , rebooted and internet stopped working.
tried switching to another router and error shows.. PAP authentication error.
called TM to come and fixed it, password was changed and no problem running on that router.

switched back to Opnsense today because i’m running on Proxmox, updated and rebooted to run a new kernel, and Opnsense stopped working again.
showing PAP authentication error once again

happened twice again, i suspect may be an issue with IPV6.

TM technician say on their side my username seems to freeze up. so unable to drop or connect.

Support OPNSense.

my internet also suddenly didn't work.

equipment and wiring all ok. rebooted everything still didn't work. modem showed no issues connecting ppoe, but log shows there is authentication issue.

so the technician just connected the default router and logged in fine.

after re-adding the cable back to pfsense, wan could connect fine.


so firstly excuse the layman talk, but i suspect the issue has something to do with how pfsense is communicating to unifi to login for internet access which somehow got stuck which resulted in no internet. so when using the default unifi router equipment to login, this somehow unstucked the login, which would explain why reconnecting the ethernet back to the pfsense router why wan could work fine now (because the account connection to unifi was unstuck).

i don't know the technical explanation for this, but this is what i discovered.

Theory #1, could be that my ip4/ip6 pppoe settings is done incorrectly which is why it resulted in this odd behaviour resulting in internet authentication failure. or the #2nd theory, could be some sort of bad stuff with tmnut end which results in this odd issue. thats all i could deduce from this but it's definitely not a hardware or wiring issue (in my case) cause i checked.


so no, i did not have to resort to resetting unifi password (fyi calling tmnut to reset the port didn't work, neither did restarting modem). just simply connecting to wan using the default unifi router, then replacing back the ethernet to the pfsense router (to connect to wan) seemed to fix the problem.


anyway i think u were spot on in regards to your comment


i'm not using opnsense, but my pfsense setting is roughly similar to yours if u figure out if the setting was done incorrectly somehow (which is causing this weird account froze/stuck behaviour, assuming the issue is on the pfsense/opnsense router settings side), i would love to know

but for now, my temporary solution is to have the default router on standby to temporary login to wan to unstuck, then switch back to pfsense, if i encounter this issue again (thkfully this doesn't seem to occur very often afaik), before i bother calling up tmnut to look into it

This post has been edited by Moogle Stiltzkin: Jul 10 2022, 12:48 PM

lucky you. I tried using TMNut stock router no joy. still getting authentication error and had to call them. technician said if i face this error again to call TM and ask them to “release HSI”.
suspect IPv6 because i was messing around with turning IPv6 on/off.

did you update pfsense recently for this to happen?

i''m not sure but i think ur right. i've used pfsense for years using ipv4 only, no issue. only recently i added the ipv6 based on your guide, but then i run into this issue where the unifi pppoe login gets stuck.

so the technician explained was, the pfsense router gets stuck for some reason (he doesn't elaborate why). So his solution was, use the stock unifi router and don't use back pfsense, if get stuck will void warranty (though that makes no sense if u don't tamper with their own equipment when switching back).

But his point was, the pfsense gets stuck, i suspect like u its something to do with ipv6.

i noticed when setting up the original stock unifi router, he asked to reset password. i think he did that to unstuck it (also based on what i read online. though he did not want to admit he had to do that to unstuck it).

i tried asking them what “release HSI” is, he claimed he don't know but i'll try that next time. did doing so fix your issue though?

is it possible to reset ur unifi password yourself? so don't have to call the technician over to do that? becauz seems like that would solve the issue if i encounter this next time


so anyway, i switch pfsense back to an older config where i used ipv4 only (no ipv6). This old setup worked fine for many years, so hopefully i won't encounter this stuck pppoe issue (which resulted in unable to relogin to pppoe again)




hm i'm using the latest pfsense, no idea if that is the reason for the recent issues the only setting changed recently was just adding ipv6 to get that working, which is why i suspect that was the culprit.





eh rely? i managed to get the stock tmnut router upon request the same day, didn't know this was hard to get had to pay for it though cauz warranty for old one expired i had an asus router i don't use but it's not using the stock firmware, so i could not use the unifi Isp requirements from the preselect list. So i'll have to reflash back to stock firmware, so i can use that as a backup for emergency to test the internet

This post has been edited by Moogle Stiltzkin: Jul 21 2022, 01:18 PM

I have been using Opnsense IPv4/IPv6 for almost a year without issues actually. just the recent 22.1.9 update and reboot then start to have this issue.

I don’t think it is possible to reset Unifi password yourself.
the last time i tried talking to customer service to reset password, they say will send sms of new password. didn’t get it at all then technician came the next day to solve it, so I’m not sure if it can solve the issue, logically yes.

So mine got stuck 3 times, first time they change password.
then 2nd and 3rd time technician just make a phone call to solve it and he didn’t even have to come, no password change too

you mean you request new router from TM?
l thought you meant use the one given by TM in the beginning, mine still in good condition since the beginning of contract so just took it out to try.

i use the regular pfsense 1 year + but only using ipv4 without issue. only recently when added ipv6 then i started having this freeze issue at least once a month or 2-3 month roughly, when before i never had this issue




o like this? well hopefully customer support will be enuff. i rather not call the technician over. is it true there is such warranty if u use ur own networking gear like router? technician claim should i decide to use my own router like the pfsense, if it resulted in tmnut account getting stuck/frozen again, then he claims warranty expire. But how does that work? it's not like i am flashing third party firmware onto the default tmnut router which i am not using. i keep the default router so i can use that to relogin because it should work, because by their logic, at that point i am using their own gear/setup so it should connect to the internet, so then they can't blame pfsense for why i cannot connect .

But he claims that for whatever reason, pfsense is causing the account login to get stuck (this part we can at least agree), there is no opinion why or any effort to troubleshoot this apparently (although i saw to fix this issue, he had to reset the tmnut password for isp ) This part we disagree, because since the issue seems to be on their end why my isp relogin seems to get stuck for whatever reason, they can't just simply deny to solve this issue (i assume password reset or whatever it is like they did for u but didn't what exactly?) under the basis u decide to connect using pfsense that gets it stuck yet again, can they?

i alrdy switch config to an old working one which only connects to ipv4 (but no ipv6), so hope i won't get this issue again, but i can't be completely certain until i've tested this for a while


mine got lost ages ago. had to pay to get issued a new one

This post has been edited by Moogle Stiltzkin: Jul 22 2022, 04:09 AM