Re: Re: Amule with Raspberry
  By: NY to Doug McIntyre on Thu Jul 30 2020 09:35 am

 > "Doug McIntyre"  wrote in message
 > news:opmdnaGkjZUda7zCnZ2dnUU7-KOdnZ2d@giganews.com...
 > > "NY"  writes:
 > >>"yamo'"  wrote in message
 > >>> Does the raspberry has an ipV4? (And not only an ipV6)
 > 
 > >>I think all computers that use TCP/IP have at least IPv4 - and optionally
>>IPv6.
 > I've never seen anything which only does IPv6 and does not do IPv4.
 > 
 > > I have many IPv6 only machines.
 > 
 > > There's no reason to setup IPv4 in a properly setup IPv6 environment
depending on
 > > your needs and requirements for them.
 > 
 > If you have a router and ISP that give you an IPv6 address, then I suppose
 > IPv4 is not strictly necessary. However I would have thought that any
 > default installation of Windows, Linux etc would enable IPv4 by default, so
 > it would require explicit action to turn it off.
 > 
 > The whole concept of IPv6 fills me with horror. The idea that all LAN
 > devices have public IP addresses, and that all devices must have a good
firewall,
 > instead of using the NAT and the firewall in the router, seems a *huge*
retrograde
 > step in terms of security. By all means use IPv6 for the router's public WAN
addres
 > to allow many more such WAN addresses in the world, but I'd have preferred
IPv6 to
 > still use IPv4 addressing within the
 > LAN, and NAT to translate between WAN and LAN.
 > 
 > But they didn't do it that way (why?) so we've got to live with the
consequences of
 > the way they designed IPv6.

If you have an Ipv6 assignation for your LAN

and you have a proper way to tell the LAN computers where to find the DNS
servers over
ipv6

and you have a proper way to tell the LAN computers where to find time servers.

Yes, then you can get away with no ipv4 in some circumpstances. Issue being,
many
routers etc don't do proper dhcpv6/slaac, so if you try to go ipv6 only with
those,
you will get the ips of your devices assigned, but they won't be able to
resolve names
or get their clocks synced.

The real problem with ipv6 is not that devices get exposed. Your LAN firewall
should
take care of it anyway. The real problem is that ipv6 requires the good will of
your
ISP for properly segmenting your network. As it is, if you want to use ipv6
properly
for having multiple networks/subnetowrks, you need the isp to have a working
dhcp with
prefix delegation. GUess what, most have not. SO if you want to do fancy tricks
with
your LAN network topology you end up having to resort to NAT66 which is ugly as
heck.

TL;DR; ipv6 SUCKS because it is poorly implemented and puts the control of your
LAN
topology in the hands of your ISP.

--
gopher://gopher.operationalsecurity.es
--- SBBSecho 3.11-Linux