Re: Is IPV6 option still necessary?

2019-10-08 Thread Wolfgang Zenker
* Dave Horsfall  [191009 02:58]:
> On Wed, 9 Oct 2019, Wolfgang Zenker wrote:
>> So, you don't *need* IPv6. But you might *want* to have it anyway.

> In my 40+ years career I've only encountered one (1) client that ran IPv6 
> internally (oddly enough, a law firm) and that was by management decree, 
> not the tehchies' (come to think of it, I don't think they *had* a techie 
> department).  Roll the lawyer jokes...

It's a big and diverse planet out there. In my 40+ years career I've
used, implemented and deployed many different networking systems.
Most of them are gone now, just IP (v4 and v6) remains. And use is
slowly shifting from IPv4 to IPv6 now.

> [..]
> If you've ever tried to grok the IPv6 spec, your brain will explode...

Must have happened to me some 20 years ago then. Probably the reason why
I rarely get a head ache :-)

Wolfgang
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Is IPV6 option still necessary?

2019-10-08 Thread Dave Horsfall

On Wed, 9 Oct 2019, Wolfgang Zenker wrote:


So, you don't *need* IPv6. But you might *want* to have it anyway.


In my 40+ years career I've only encountered one (1) client that ran IPv6 
internally (oddly enough, a law firm) and that was by management decree, 
not the tehchies' (come to think of it, I don't think they *had* a techie 
department).  Roll the lawyer jokes...


My router tries IPv6 first, but inevitably falls back to IPv4; IPv6 is a 
camel i.e. a horse designed by a committee.


If you've ever tried to grok the IPv6 spec, your brain will explode...

-- Dave
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Is IPV6 option still necessary?

2019-10-08 Thread Wolfgang Zenker
Hi,

* abi via freebsd-ports  [191008 21:16]:
> 07.10.2019 09:18, Yasuhiro KIMURA пишет:
>> On October 10, 2012 IPV6 option of all ports was enabled by
>> default. Commit message said "We are in 2012, it is time to activate
>> IPV6 options by default everywhere".

>> And now we are in 2019. IPv6 is more widely used than 2012. So I
>> wonder if IPV6 option is still necessary.

>> If you use official packages then you always use IPv6-enabled
>> binaries. And even if you build packages by yourself you still use
>> IPv6-enabled ones unless you disable IPV6 option. So I think at most
>> only a few people uses IPv6-disabled packages.

>> Are there anybody who still disables IPV6 option for some serious
>> reason such as working around IPv6-related problem? If there aren't
>> then I think it's time to remove IPV6 option from ports framework.

> I'm writing from 2019 and I build kernel and ports without IPv6. For all 
> this years I fail to understand why I need it.

> My home devices fit 10.0.0.0/16 nicely, I have faith in NAT and I 
> encountered no IPv6-only sites.

> But I saw CVEs in IPv6 stack.

If you connect from a typical end user site to a website on my company,
if you go via IPv4 your packets will go through NAT at your CPE, quite
possibly NATted to IPv6, going through another NAT at the exit routers
of your provider and arrive at an reverse proxy at my site being proxied
to IPv6 finally reaching the website which is running on a IPv6 only
jail. Thats because neither your typical DSL or mobile provider nor my
webhosting company has enough IPv4 addresses to hand out a globally
routable address to all nodes. An IPv6 connection would be end-to-end.

So, you don't *need* IPv6. But you might *want* to have it anyway.

Wolfgang
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Is IPV6 option still necessary?

2019-10-08 Thread abi via freebsd-ports

07.10.2019 09:18, Yasuhiro KIMURA пишет:

On October 10, 2012 IPV6 option of all ports was enabled by
default. Commit message said "We are in 2012, it is time to activate
IPV6 options by default everywhere".

And now we are in 2019. IPv6 is more widely used than 2012. So I
wonder if IPV6 option is still necessary.

If you use official packages then you always use IPv6-enabled
binaries. And even if you build packages by yourself you still use
IPv6-enabled ones unless you disable IPV6 option. So I think at most
only a few people uses IPv6-disabled packages.

Are there anybody who still disables IPV6 option for some serious
reason such as working around IPv6-related problem? If there aren't
then I think it's time to remove IPV6 option from ports framework.

I'm writing from 2019 and I build kernel and ports without IPv6. For all 
this years I fail to understand why I need it.


My home devices fit 10.0.0.0/16 nicely, I have faith in NAT and I 
encountered no IPv6-only sites.


But I saw CVEs in IPv6 stack.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"