It brings the requirement for a firewall on every endpoint with a unique address. My Phone often has an ipv6 address (found out this holiday wen I couldn't resolve one of sites because of an orphan ipv6 entry nobody noticed), and has little problems. Perhaps there is also "firewalling" on the router and the phone can't even have incoming connections. Not sure. In any case, the phone seems to do fine.

▲

gatio an hour ago | parent | next [-]

> Perhaps there is also "firewalling" on the router and the phone can't even have incoming connections. Not sure.

Correct. Every home wifi router worth its salt will firewall incoming connections by default, whether v4 or v6. It's then possible (unless it's some shitty ISP-provided locked down device) to add specific allow rules, or allow all for a particular client.

egress is typically wide open, although sometimes they lock down particular protocols by default (eg. smtp, bittorrent)

▲

mittensc 4 hours ago | parent | prev | next [-]

> Not sure. In any case, the phone seems to do fine.

That's mostly because a phone is very locked down, can you run an accessible ftp server on your phone?

It's also not windows

▲

c0balt 2 hours ago | parent [-]

For android, the answer is yes (without rooting being required).

	▲	iggldiggl an hour ago \| parent [-]
		> without rooting being required If you want to use the standard port, that's only true as of very recently, though, see https://issuetracker.google.com/issues/218578943#comment17

▲

kijin 4 hours ago | parent | prev [-]

Phone OSs tend to pay a lot more attention to security than the crap they put on consumer-grade routers, "smart" TVs and cheap webcams.

I would invest in a proper firewall for the entire home before opening up anything to the world, IPv6 or not.