Well I haven't thought of that, thanks for sharing another advantage/use of IPv6 Boltersdriveer.

IPv6 botnets are rare as for now.

(07-04-2012 03:47 PM)Boltersdriveer Wrote:  Then again, with an IPv6 setup e.g. on a remotely hosted database, it kinda protects the server more since a number of residential users will not be able to directly access it due to lack of IPv6 - only the web server has to access the database via IPv6.

Very interesting idea. Though you can just drop all packets that aren't coming from the server, but I suppose that does incur slightly more load and spoofing isn't exactly hard.

Anyway, ipv6 isn't inherently more secure, but it does support privacy and security options that can allow it to be.

(07-05-2012 05:14 AM)f8ll Wrote:  

(07-04-2012 03:47 PM)Boltersdriveer Wrote:  Then again, with an IPv6 setup e.g. on a remotely hosted database, it kinda protects the server more since a number of residential users will not be able to directly access it due to lack of IPv6 - only the web server has to access the database via IPv6.

Very interesting idea. Though you can just drop all packets that aren't coming from the server, but I suppose that does incur slightly more load and spoofing isn't exactly hard.

Anyway, ipv6 isn't inherently more secure, but it does support privacy and security options that can allow it to be.

Of course, with DNSSEC and other options that I'm still researching on, I feel that this should have been what the Internet should have been created with.

I don't believe it incurs more load, but just that non-IPv6 devices will not be able to directly access the database - so you just need to connect via IPv6 on your web server onto it - similar to IPv4 remote database setup, just that in this case it would be IPv6.

I meant that dropping packets incurs more load. That is, you can do something similar with ipv4 but just drop packets that do not originate from the server.