|
git apologist posted:ipv6 addresses can be adorbs, for example local services in an aws vpc are prefixed with fd00:ec2, eg dns is fd00:ec2::253 check out this nerd
|
#
?
Feb 16, 2024 10:36
|
|
|
|
| # ? Jun 7, 2024 15:07 |
|
|
git apologist posted:ipv6 addresses can be adorbs, for example local services in an aws vpc are prefixed with fd00:ec2, eg dns is fd00:ec2::253 no 420 or 69 can some1 probe thjs mf!!!!!???!??
|
|
#
?
Feb 16, 2024 10:57
|
|
|
echinopsis posted:no 420 or 69 seconded
|
|
#
?
Feb 16, 2024 11:03
|
|
|
fart simpson posted:check out this nerd text me
|
|
#
?
Feb 18, 2024 15:42
|
|
|
fart simpson posted:seconded you have my acks
|
|
#
?
Feb 18, 2024 20:56
|
|
|
ip v1: original syn
|
|
#
?
Feb 18, 2024 23:40
|
|
|
Buck Turgidson posted:ip v1: original syn 
|
|
#
?
Feb 19, 2024 00:03
|
|
|
I broke out a separate subnet on my home network for a simple "hello world" nginx server running on a Raspberry Pi, and something about being in an IPv6 only environment causes the network interface to slowly fail while revealing nothing useful in the logs 
|
|
#
?
Feb 20, 2024 03:15
|
|
|
the biggest fail is running nginx at home
|
|
#
?
Feb 20, 2024 03:54
|
|
|
burning 18 quintillion addresses for a cat picture 
|
|
#
?
Feb 20, 2024 05:33
|
|
|
Posting by policy: GNOME Network Monitor really doesn't like if it never gets a DHCP response, and will cycle the network connection indefinitely. This loving sucks when you have it plugged into a IPv6-only network with no stateful DHCP, only router advertisements. The workaround is to increase the IPv6 DHCP client timeout to infinity.
|
|
#
?
Feb 20, 2024 17:03
|
|
|
Skinnymansbeerbelly posted:Posting by policy: GNOME Network Monitor really doesn't like if it never gets a DHCP response, and will cycle the network connection indefinitely. This loving sucks when you have it plugged into a IPv6-only network with no stateful DHCP, only router advertisements. The workaround is to increase the IPv6 DHCP client timeout to infinity. linux on the desktop, folks
|
|
#
?
Feb 25, 2024 12:05
|
|
|
Skinnymansbeerbelly posted:Posting by policy: GNOME Network Monitor really doesn't like if it never gets a DHCP response, and will cycle the network connection indefinitely. This loving sucks when you have it plugged into a IPv6-only network with no stateful DHCP, only router advertisements. The workaround is to increase the IPv6 DHCP client timeout to infinity. works fine if you set ipv4 to ignore. otherwise it will indeed keep trying to bring up ipv4, as configured.
|
|
#
?
Feb 25, 2024 16:09
|
|
|
outhole surfer posted:works fine if you set ipv4 to ignore. otherwise it will indeed keep trying to bring up ipv4, as configured. I disabled ipv4 before plugging it into the 6 only network, and it still cycled.
|
|
#
?
Feb 27, 2024 16:49
|
|
|
I still can't make it work because the router keeps eating the variable upon which my prefix change detection script relies 
|
|
#
?
Feb 27, 2024 17:05
|
|
|
weird. maybe clatd somehow keeps mine from flapping, but i'm ipv6 only at home and it all just works.
|
|
#
?
Feb 27, 2024 17:23
|
|
|
i have to give a talk to a bunch of nerds on ipv6 in like a month the thesis of my talk is like ‘there’s no real compelling reason to move to ipv6, don’t bother if you can avoid it’. thanks
|
|
#
?
Feb 28, 2024 08:16
|
|
|
depends on the setting. internal network, then of course it doesn't matter, but anything actually touching the internet should have it enabled.
|
|
#
?
Feb 28, 2024 09:04
|
|
|
git apologist posted:i have to give a talk to a bunch of nerds on ipv6 in like a month lol no
|
|
#
?
Feb 28, 2024 11:00
|
|
|
know what i love? cgnat let’s keep loving this chicken forever folks
|
|
#
?
Feb 28, 2024 11:01
|
|
|
|
| # ? Jun 7, 2024 15:07 |
|
|
i simply pay $10 a month to my isp to have a static ip and hence avoid cgnat (cos that’s just how it works with them)
|
|
#
?
Feb 28, 2024 11:05
|
|