Will IPv6 support be a form of spammers?

A large (main) part of developing a web application is to protect it from abuse, more specifically, protection from spammers.

I just noticed that today spam bots manage to request a form, fill it out, submit and resend (for example, in case the CMS requests additional information before accepting the form data) ... all from different IPv4 addresses.

Firstly, two questions:

  • What methods do they use to route different requests belonging to the same session (submitting the form) through different IP addresses, in a few seconds?
  • I could encode an IP-based hash to verify that the IP request of the form and whoever represents it are the same; but: is there a legitimate reason why a user (i.e. not a spammer) might want to send a form from a different IP address than the one that requested it?

Then, to the meat of this question:

With its virtually unlimited number of IPv6 addresses, will the life of webmasters and web application developers be miserable?

It’s possible that end users will have their own static IPv6, which is good for us because we can more easily block users whose computers are at risk.

Or spammers can continue to attack us from different angles, never using the same IPv6 twice ... I'm not too sure how this will work technically, especially since I don’t even understand how it works with IPv4.

, IPv4 .

+5
4

, IPv6, , , .

: IPv6 RFC 4941, -, , 64- ​​ .

, IPv4, . , - IPv4, NAT, , IPv4-. - , , IPv4, NAT, , .

+4

, , , IPv6 HTTP-; .

[] IPv6 , :

C:\>netsh interface ipv6 show address interface=4 level=normal
Querying active state...


Interface 4: Local Area Connection

Addr Type  DAD State  Valid Life   Pref. Life   Address
---------  ---------- ------------ ------------ -----------------------------
[...]
Temporary  Preferred     23h59m47s     3h59m47s 2001:4830:16c0:0:f51c:8f47:26ff:596b
Temporary  Deprecated    23h59m47s           0s 2001:4830:16c0:0:8d09:1a8:6039:548b
Temporary  Deprecated    23h59m47s           0s 2001:4830:16c0:0:954b:fd2d:6528:a6b2
Temporary  Deprecated    23h59m47s           0s 2001:4830:16c0:0:4c27:9415:e1cc:5a5a
Temporary  Deprecated    23h59m47s           0s 2001:4830:16c0:0:951f:b93:b21e:1d97
Temporary  Deprecated    23h59m47s           0s 2001:4830:16c0:0:59c3:d575:189e:4fbb
Temporary  Deprecated     6h32m45s           0s 2001:4830:16c0:0:f838:1133:38d0:894c
Public     Preferred     23h59m47s     3h59m47s 2001:4830:16c0:0:20b:dbff:fe26:9fc5
Link       Preferred      infinite     infinite fe80::20b:dbff:fe26:9fc5
No entries were found.

( , .)

, "" "" "" ( "" ).

"Link" - , . ( , "", , .)

naesten@hydrogen:~% ipv6calc -i fe80::20b:dbff:fe26:9fc5 2>/dev/null
Address type: unicast, link-local
Registry for address: reserved
Interface identifier: 020b:dbff:fe26:9fc5
EUI-48/MAC address: 00:0b:db:26:9f:c5
MAC is a global unique one
MAC is an unicast one
OUI is: Dell ESG PCBA Test

, ( 64- ) MAC- .

, 2001:4830:16c0::/48, , , , .

"" , , ( ), , , .

"" ?

: ?

RFC 4941 - IPv6. , IP- ", , " ( " " ), ).

IPv6- . "" , , "", "", , "" . "" "" , TEMP_VALID_LIFETIME TEMP_PREFERRED_LIFETIME, .

, 5 , , , , :

TEMP_VALID_LIFETIME -- Default value: 1 week.  Users should be able
to override the default value.

TEMP_PREFERRED_LIFETIME -- Default value: 1 day.  Users should be
able to override the default value.
+2

IP- , - , , Wi-Fi- Wi-Fi- . .

+2

/64, - , .

(, a/56 /48), , .

+1

All Articles