Author Topic: Another post from your IP within 60 seconds (Read 13751 times)

madires · « **Reply #25 on:** October 27, 2016, 12:34:45 pm »

172.68.51.163 is one of Cloudflare's proxies in Vienna:

$ traceroute 172.68.51.163
[...]
 7  vix.edge01.vie01.as13335.com (193.203.0.195)  13.065 ms  13.153 ms  13.060 ms
 8  172.68.51.163 (172.68.51.163)  12.826 ms  12.801 ms  12.881 ms

AS13335 is Cloudflare and "vix" indicates the Vienna Internet eXchange.

voltsandjolts · « **Reply #26 on:** October 27, 2016, 02:50:44 pm »

I'm not sure if I understand:

Are you saying that because eevblog.com uses Cloudflare DNS servers, it also uses Cloudflare CDN services - to the extent that Cloudflare servers in your local country can actually act as reverse proxies for eevblog.com server in AUZ to speed things up a bit. When that happens, what eevblog.com thinks is my internet ip address is actually the address of the Cloudflare proxy.

Is that how it works?

Monkeh · « **Reply #27 on:** October 27, 2016, 02:58:01 pm »

CloudFlare will be passing X-Forwarded-For, so it's not likely to be them.

You'll note if you look at your own posts that you see your own IP address in the bottom right corner. So let's not be jumping to 'forum misconfigured' conclusions when only one or two people out of hundreds are having issues.

rstofer · « **Reply #28 on:** October 27, 2016, 03:13:38 pm »

I have the same issue (erroneous timing) and I'm in the US. Specifically, I use Comcast and my problems are with the wired Internet, no wireless magic in use.

Sometimes I will do a Copy just in case things go sideways.

I also get the Bad Gateway error from the site. I can usually clear it by using the 'Reload this page' button. It seems strange that I can still get to the site, to the extent I get the bad gateway message, but I can't go back to a forum I was using an hour or so ago.

madires · « **Reply #29 on:** October 27, 2016, 03:38:35 pm »

Cloudflare includes X-Forwarded-For and X-Forwarded-Proto ( https://support.cloudflare.com/hc/en-us/articles/200170946-Does-CloudFlare-include-an-X-Forwarded-For-or-X-Forwarded-Proto-header- ). And SMF seems to parse X-Forwarded-For (http://www.simplemachines.org/community/index.php?topic=477528.0 ). Sill, PeDre has the proxy's IP address logged. On my posts I see the network symbol, but no IP address. Hmm, there could be another cause, like IPv6.

In case, you also got those "another post from your IP address" errors, could you please check, if your latest posts got an IP address logged. At the bottom right of your post is a network symbol. For other users is states "Logged". Does it state an IP address. If yes, IPv4 or IPv6?

madires · « **Reply #30 on:** October 27, 2016, 03:49:16 pm »

I've checked my old posts and until 2016-09-23 my IPv4 address is logged. After that date no IP address is logged at all. BTW, I got IPv4 and IPv6, and prefer IPv6 if available.

Monkeh · « **Reply #31 on:** October 27, 2016, 03:50:25 pm »

Disable IPv6 if you have it available and see what happens.

madires · « **Reply #32 on:** October 27, 2016, 03:56:24 pm »

Quote from: Monkeh on October 27, 2016, 03:50:25 pm

Disable IPv6 if you have it available and see what happens.

This post is from a PC with public IPv4 only.

Edit: And the forum logs my IPv4 address fine. So Cloudflare started to roll out IPv6 and SMF has problems with IPv6. Maybe it treats all IPv6 addresses as "0.0.0.0" or n/a , which might cause the issue. So all users with IPv6 could face the "Another post from your IP" error.

madires · « **Reply #33 on:** October 27, 2016, 04:34:43 pm »

From what we've seen so far:

The forum uses Cloudflare's reverse proxy service, which uses X-Forwarded-For to pass on the client's original IP address. SMF (the forum's software) takes the originating IP address and also parses X-Forwarded-For to handle proxies. For the IP address logged SMF prefers X-Forwarded-For, if available. That address is also used to detect malicious users (multiple users using the same address) and SMF has a threshold for that. About a month ago Cloudflare seems to have added IPv6 addresses to the DNS records for the forum, which causes clients with IPv4 and IPv6 to prefer the IPv6 addresses (default setting in many OSs). But obviously SMF has problems to deal with IPv6 addresses (not logged) and treats posts from IPv6 clients as being from the same IP address, causing the "Another post from your IP within 60 seconds" error.

bitseeker · « **Reply #34 on:** October 27, 2016, 06:35:17 pm »

I haven't encountered the erroneous version of the 60-second block, but my IP address still appears correctly on my posts.

madires · « **Reply #35 on:** October 27, 2016, 06:50:49 pm »

IPv4 or IPv6?

PS: I just had the error again

Monkeh · « **Reply #36 on:** October 27, 2016, 06:51:43 pm »

Good old IPv6. Should've been using it actively over 10 years ago, still can't get simple things to deal with it.

madires · « **Reply #37 on:** October 27, 2016, 07:18:09 pm »

I don't get it. A lot of companies are ignoring IPv6 despite the lack of public IPv4 address space. It wasn't any surprise, took a little bit longer than expected actually. Ignoring reality costs about US$ 10 per IPv4

PS: And the lovely error again

Looks like, I have to tamper with my DNS to make EEVblog IPv4 only.

bitseeker · « **Reply #38 on:** October 27, 2016, 11:13:48 pm »

Quote from: madires on October 27, 2016, 06:50:49 pm

IPv4 or IPv6?

Oh, IPv4.

Homer J Simpson · « **Reply #39 on:** October 27, 2016, 11:32:01 pm »

T3sl4co1l · « **Reply #40 on:** October 28, 2016, 02:27:19 am »

Quote from: bson on October 27, 2016, 01:32:11 am

Could it be accidentally considering a preview a post?

It seems like it happens most on posts I've previewed...

Tim

T3sl4co1l · « **Reply #41 on:** October 28, 2016, 02:37:14 am »

Quote from: PeDre on October 27, 2016, 11:27:54 am

I noticed yesterday that the logged IP address is wrong.
I have a static IP address 83.64.2xx.xx, but it was these logged here 172.68.51.163.
It was logged normally the correct IP address.

Peter

Edit: Also in this posting the wrong IP address 172.68.51.163 has been logged.

Hmm, looking over my recent posts, most don't show an IP logged. One shows,
172.2.37.169
which is not my IPv4 address (65.xxx).

I do have IPv6 configured, so most services should be using that.

I don't have any way to check what the forum server sees me as (since it doesn't seem to record it, most of the time), but I certainly don't have a proxy configured. It seems unlikely that it would be a proxy (whether accidentally or maliciously..).

So, possibly it's an SMF bug?

Tim

Monkeh · « **Reply #42 on:** October 28, 2016, 02:42:16 am »

Quote from: T3sl4co1l on October 28, 2016, 02:37:14 am

Quote from: PeDre on October 27, 2016, 11:27:54 am
I noticed yesterday that the logged IP address is wrong.
I have a static IP address 83.64.2xx.xx, but it was these logged here 172.68.51.163.
It was logged normally the correct IP address.

Peter

Edit: Also in this posting the wrong IP address 172.68.51.163 has been logged.

Hmm, looking over my recent posts, most don't show an IP logged. One shows,
172.2.37.169
which is not my IPv4 address (65.xxx).

.. have you been working for Creation Technologies lately?

Quote

It seems unlikely that it would be a proxy (whether accidentally or maliciously..).

ISPs love to be 'helpful' with proxies, and I have no idea if SMF can handle chained X-Forwarded-For headers the way CF handle proxy chains.

T3sl4co1l · « **Reply #43 on:** October 28, 2016, 02:53:24 am »

Quote from: Monkeh on October 28, 2016, 02:42:16 am

.. have you been working for Creation Technologies lately?

Oh yeah, I post from there sometimes.

Come to think of it, kind of surprised they don't have IPv6 set up...

they have good IT

Tim

EEVblog · « **Reply #44 on:** October 28, 2016, 02:54:36 am »

Quote from: T3sl4co1l on October 28, 2016, 02:37:14 am

Quote from: PeDre on October 27, 2016, 11:27:54 am
I noticed yesterday that the logged IP address is wrong.
I have a static IP address 83.64.2xx.xx, but it was these logged here 172.68.51.163.
It was logged normally the correct IP address.
Peter
Edit: Also in this posting the wrong IP address 172.68.51.163 has been logged.
Hmm, looking over my recent posts, most don't show an IP logged. One shows,
172.2.37.169
which is not my IPv4 address (65.xxx).
I do have IPv6 configured, so most services should be using that.
I don't have any way to check what the forum server sees me as (since it doesn't seem to record it, most of the time), but I certainly don't have a proxy configured. It seems unlikely that it would be a proxy (whether accidentally or maliciously..).
So, possibly it's an SMF bug?

Actually, I don't see the IP address next to quite a few posts here, including yours.
First time I've noticed this, I thought it always logged and displayed the IP address of every post.

EDIT: Yep, something is very wrong:

I have never seen this before, I've always been able to track IP's on every user and every post.

Monkeh · « **Reply #45 on:** October 28, 2016, 02:56:18 am »

It does not seem to like IPv6. Does the actual server even have IPv6?

Cerebus · « **Reply #46 on:** October 28, 2016, 03:10:56 am »

Quote from: Monkeh on October 28, 2016, 02:56:18 am

It does not seem to like IPv6. Does the actual server even have IPv6?

Well it's got IPv6 AAAA DNS records but that doesn't necessarily mean anything as, obviously, they will be pointing to CloudFlare.

I'm native IPv6 here and have been for donkey's years. I'm also running on a stack that will pick IPv6 over IPv4 if it's available so if IPv6 has been available for the EEVBlog then that's what I'll have been using. I've see the spurious rate limiting messages recently, but not in the past.

Monkeh · « **Reply #47 on:** October 28, 2016, 03:12:01 am »

Quote from: Cerebus on October 28, 2016, 03:10:56 am

Quote from: Monkeh on October 28, 2016, 02:56:18 am
It does not seem to like IPv6. Does the actual server even have IPv6?

Well it's got IPv6 AAAA DNS records but that doesn't necessarily mean anything as, obviously, they will be pointing to CloudFlare.

That's why I asked about the server..

EEVblog · « **Reply #48 on:** October 28, 2016, 05:49:49 am »

gnif confirmed it is ipv6 support (or lack of)
I have just installed a mod to fix this, can people please do a test post so I can see if the IP address is shown, Cerebus and T3sl4co1l in particular who's IP's I can't see.

EEVblog · « **Reply #49 on:** October 28, 2016, 05:53:04 am »

I've also installed another mod that supposedly fixes the cloudflare IP issue.


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: Another post from your IP within 60 seconds (Read 13751 times)

Share me