samba - Apr 2020 - Removing IP address from DC

On 30/04/2020 09:50, William Edwards wrote:
> I want to do this because IPv4 is a legacy protocol. I do not need IPv4, it
is old, and I do not want IPv4 in my network if I don't need it.
Just because something is legacy, it doesn't mean you cannot still use
it.
>> Do you have more than 2,147,483,647 computers, printers, scanners etc ?
> No.
> Then you have no real need to use IPv6
That's thinking in the wrong direction.
I have no need to use IPv4. My network does IPv6, my VPN does IPv6, so why would
I still use a legacy protocol?



--
To unsubscribe from this list go to the following URL and read the
instructions: ?https://lists.samba.org/mailman/options/samba

On 30/04/2020 10:23, William Edwards via samba wrote:
> That's thinking in the wrong direction.
> I have no need to use IPv4. My network does IPv6, my VPN does IPv6, so why
would I still use a legacy protocol?
No, you are thinking in the wrong direction, there is absolutely no 
reason to use IPv6 internally. IPv6 only came about because of the 
shortage of IPv4 addresses for global internet addresses, you can and 
should use IPv4 addresses internally. However, it is your network and 
you can decide to not use best practise.

Rowland

> No, you are thinking in the wrong direction, there is absolutely no
> reason to use IPv6 internally. IPv6 only came about because of the
> shortage of IPv4 addresses for global internet addresses, you can and
> should use IPv4 addresses internally.
I wholeheartedly disagree. The next generation of network engineers should be
completely IPv6-focused to increase IPv6 adoption rates on the internet. Using
IPv4 internally will only steer them in the direction of using IPv4 on the
internet as well, as the protocols require different levels of knowledge.
> However, it is your network and
> you can decide to not use best practise.
I think a product that requires use of IPv4 as best practice should reconsider
its recommended configuration methods and philosophy. IPv6 is the future. Users
should be steered towards using future-proof internet protocols, even if there
is no absolute necessity to use them internally; increasing its adoption rates
in any network will improve adoption rates.

Anyway, I highly doubt this mailing list is the right place to discuss this. My
question was answered in your first reply, for which I would like to thank you.

William

Hai 
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> William Edwards via samba
> Verzonden: donderdag 30 april 2020 11:42
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] Removing IP address from DC
> 
> > No, you are thinking in the wrong direction, there is absolutely no
> > reason to use IPv6 internally. IPv6 only came about because of the
> > shortage of IPv4 addresses for global internet addresses, 
> you can and
> > should use IPv4 addresses internally.
> 
> I wholeheartedly disagree. The next generation of network 
> engineers should be completely IPv6-focused to increase IPv6 
> adoption rates on the internet. Using IPv4 internally will 
> only steer them in the direction of using IPv4 on the 
> internet as well, as the protocols require different levels 
> of knowledge.
> 
> > However, it is your network and
> > you can decide to not use best practise.
> 
> I think a product that requires use of IPv4 as best practice 
> should reconsider its recommended configuration methods and 
> philosophy. IPv6 is the future. Users should be steered 
> towards using future-proof internet protocols, even if there 
> is no absolute necessity to use them internally; increasing 
> its adoption rates in any network will improve adoption rates.
> 
> Anyway, I highly doubt this mailing list is the right place 
> to discuss this. My question was answered in your first 
> reply, for which I would like to thank you.
Correct, but this IS a good point. 

And, i think i understand where this is coming from. ( helps that im dutch also
).
Dutch Internet provider Ziggo is deploying routers that have only IPv6
configured for the lan segements.
and IPv6 routings are more inteligent then IPv4.. 

I suggest, configure the AD-DC for both IPv4 and IPv6.

@Rowland, its something we really should think about. 
Maybe i'll do a setup also with only IPv6 configured. 

I'll think about it. (since its more work and im behind...) 

Greetz, 

Louis