= Сообщение: 6870 из 7402 ============================================= IPV6 = От : Scott Street 1:266/420 20 Oct 21 10:41:08 Кому : Michiel van der Vlist 20 Oct 21 10:41:08 Тема : A small questionary on ISPs FGHI : area://IPV6?msgid=1:266/420+61702e37 На : area://IPV6?msgid=2:280/5555+616fbd24 = Кодировка сообщения определена как: UTF8 =================================== Ответ: area://IPV6?msgid=2:280/5555+617317b2 ============================================================================== Hello Michiel!
20 Oct 21 08:51, you wrote to me:
SS>> Additionally, I can ping my router's public IPv6 address from SS>> the LAN side, don't know about the WAN side. I also can make SS>> IPv6 connections to sites on the Internet, infact, macOS 11+ SS>> default to IPv6 first; and my Linux system has been updated to do SS>> the same.
MV> OK, so you have outgoing IPv6 capbility. But incoming is still a MV> problem. Can you expand a bit on what attempts you have made to MV> achieve incoming and why you think it didn't work?
Ah, two reasons. a) I'm not in direct control of the router, my roommate is the "customer" on the account and he is non-techincal. Thus I have to walk him through the changes on the Xfinity app to allow pin-holes in the default firewall/router. b) After much of the "walking through", Xfinity/Comcast would 'clean' the firewall rules of the required settings; both for IPv4 and IPv6.
Neither of these are probably Comcast's issues; more likely my /non-techincal/ roommate. For a real solution, I am awaiting for permanent employment before I just into getting my very own connection.
I was able to get the IPv4 connection with upnpc, which I run in a cron job several times a day. command:: upnpc -e "BINKP Incoming Mail" -a `upnpc -l | grep "Local LAN ip" | cut -d: -f2` 24554 24554 tcp
The bits after -a; `...` get the Linux machines IPv4 address (dynamically), since the router, too, likes to change all of the addresses on, what appears to be, random basis. The IPv6 address change at the same time. Which is a real bear, as I often leave terminal (ssh) sessions open from my Mac to the Linux machine, and of course, when the addresses change my sessions are killed. Again, all of which I hope to solve with my own connection, the sooner the better.
Scott
--- * Origin: -={ The Digital Post }=- (1:266/420)
