News for hackers. Stuff that matters.
Re:A brief history of IPv4 address space exhaustion by metalliqaz on Thursday May 25, 2017 @02:25PM (#14419090)
I now receive a block of IPv6 from Comcast. I allow the router to assign them to devices on the network, but I admit that I am somewhat worried that my local PC is no longer isolated from the Internet by a private IP.
Re:A brief history of IPv4 address space exhaustion by lwhalen on Thursday May 25, 2017 @02:30PM (#14419120)
You want to set up an 'egress only' v6 gateway for your /64s (or however you carve up your netblock). That is going to be the closest analogue to behind-a-NAT-like behavior.
Re:A brief history of IPv4 address space exhaustion by metalliqaz on Thursday May 25, 2017 @02:33PM (#14419141)
Thanks I'll look into it with pfSense.
Re:A brief history of IPv4 address space exhaustion by JetSpiegel on Thursday May 25, 2017 @02:49PM (#14419254)
Your router has a firewall, external computers can't just send packets to the internal addresses. NAT is not a firewall.
Re:A brief history of IPv4 address space exhaustion by mirimir on Thursday May 25, 2017 @03:41PM (#14419590)
So IPv6 firewall rules are common now for consumer routers?
Re:A brief history of IPv4 address space exhaustion by Symbiote on Friday May 26, 2017 @03:47AM (#14422565)
Yes.

My mum's boring broadband connection, with a free router supplied by the ISP in the UK, has the functionality next to the port forwarding settings for IPv4.

That's typical. Look up IPv6 pinhole to see how ISPs document it.

Re:A brief history of IPv4 address space exhaustion by mirimir on Friday May 26, 2017 @07:46AM (#14423372)
OK, so I suspect that it varies greatly among markets.

But I wonder, is it a fair assumption that the router that you get will either 1) not route IPv6 at all, or 2) route IPv6, and by default deny incoming traffic? Problematic would be ones that routed IPv6, and by default accepted incoming traffic.

Re:A brief history of IPv4 address space exhaustion by Spivak on Thursday May 25, 2017 @04:59PM (#14420115)
First, nothing is common for consumer IPv6 routers, they're practically non-existent.

Second, you get the same security benefits by having a firewall that denies outbound connections not already established.

Re:A brief history of IPv4 address space exhaustion by sparewalking on Thursday May 25, 2017 @05:20PM (#14420223)
I bought an IPv6 router 3-4 years ago.
Re:A brief history of IPv4 address space exhaustion by voltagex_ on Thursday May 25, 2017 @08:26PM (#14421174)
Most people don't buy routers, they are given them by their ISPs. My parents switched ISP at the start of the year and were given a 5 year old modem/router.
Re:A brief history of IPv4 address space exhaustion by Spivak on Thursday May 25, 2017 @09:08PM (#14421404)
You're also on Hacker News. They have been available for a long time, but they're firmly a techie/early adopter product.
Re:A brief history of IPv4 address space exhaustion by Symbiote on Saturday May 27, 2017 @08:34AM (#14429837)
In many countries the ISP supplies the router. I've had IPv6 capable routers for years and years in Britain, but it's only in the last 2 years or so that the IPv6 address has been assigned by the ISP.
Re:A brief history of IPv4 address space exhaustion by bArray on Thursday May 25, 2017 @02:39PM (#14419182)
I think whilst it's nice to have that barrier, it's prevention rather than cure anyway. There's no substitute for secure devices :)
Re:A brief history of IPv4 address space exhaustion by 2bitencryption on Thursday May 25, 2017 @03:51PM (#14419669)
what's more secure than a device you cannot possibly reach?

I'll take an insecure device isolated at the bottom of the ocean in a titanium block over a probably-secure device that is publicly addressable any day.

Re:A brief history of IPv4 address space exhaustion by Spivak on Thursday May 25, 2017 @04:53PM (#14420081)
Your appliance 'router' can (and probably does) run a firewall to give you that kind of control. NAT never really gave you that.
Re:A brief history of IPv4 address space exhaustion by linkregister on Thursday May 25, 2017 @03:55PM (#14419694)
Which devices are secure?
Re:A brief history of IPv4 address space exhaustion by Spivak on Thursday May 25, 2017 @04:54PM (#14420087)
Certainly not the 'router' running your NAT.
Re:A brief history of IPv4 address space exhaustion by bArray on Friday May 26, 2017 @09:49AM (#14423987)
Yep.
Re:A brief history of IPv4 address space exhaustion by belorn on Thursday May 25, 2017 @04:41PM (#14419994)
Be sure that you are really isolated if relying on it for protection. Its only as secure as the least secure node inside the bubble, and there can be quite a dangerous in large networks like in a company or campus. It would not surprise me if a number of WannaCry victims was behind nat and got infected by a machine on the same local network.
Re:A brief history of IPv4 address space exhaustion by djsumdog on Thursday May 25, 2017 @05:47PM (#14420381)
I was at a company that made a mistake like this during their IPv6 rollout. The firewalls are different an individual, and initially they only had iptables rules on their BGR and an empty ip6tables set.
Re:A brief history of IPv4 address space exhaustion by mavendependency on Thursday May 25, 2017 @02:51PM (#14419262)
This is the case for ipv6 on mobile data by default. Would using a usb modem result in getting affected by smb exploits or something of the sort?