FT blocks an entire Internet ASN
Apr 12, 2022 | 2:27 pm
#1
Original Poster
Moderator: Hyatt, American Express; FlyerTalk Evangelist
Join Date: Jun 2015
Location: WAS
Programs: :rolleyes:, DL DM, AA EXP, UA Silver, Hyatt Glob, Mlife Noir (=> Marriott Amb), invol FT beta tester
Posts: 21,654
FT blocks an entire Internet ASN
I am currently on a trip that includes the Netherlands and Belgium. The travel eSIM I bought uses mainly KPN in the Netherlands (though I have occasionally seen some version of Vodaphone pop up), and a couple different providers in Belgium (Belgacom, Proximus, Base) that Google/Wikpedia tell me might be affiliated with KPN.
At any rate, in all cases, attempting to access FlyerTalk while using mobile data on these networks leads to the error message below.
An ASN covers a *huge* chunk of Internet IP space (or really, multiple chunks of IP addresses usually related to the same entity in some way): https://en.wikipedia.org/wiki/Autono...stem_(Internet)
Here are all the IP ranges in this particular one: https://www.whatismyip.com/asn/16276/
So far I have gotten this error messages for IP addresses falling within 51.38.0.0/16, 54.36.0.0/16, and 54.37.0.0/16 (none of which match my physical location but this is not entirely surprising for a multi-national service provider) -- note that a /16 is more than 65k IP addresses.
OK, "Operator: OVN" sort of explains it because, yes, as someone who administers my own email servers, I have gotten a lot of spam from OVH addresses in the past, so I get it, but
https://en.wikipedia.org/wiki/KPN
"Its mobile division, KPN Mobile, had more than 33 million subscribers in the Netherlands, Germany, Belgium, France, and Spain under different brand names. Through its ownership of several European Internet service providers, KPN also provides Internet access to 2.1 million customers"
https://en.wikipedia.org/wiki/Proximus
"Proximus [...] is the largest of Belgium's three mobile telecommunications companies"
I suggest that maybe banning the entire ASN isn't the best business decision...
The obvious temporary user workaround is to use a VPN, which lol: Consolidated "Problems Accessing FlyerTalk When Using A VPN" thread
(luckily I run my own VPN server at home)
At any rate, in all cases, attempting to access FlyerTalk while using mobile data on these networks leads to the error message below.
An ASN covers a *huge* chunk of Internet IP space (or really, multiple chunks of IP addresses usually related to the same entity in some way): https://en.wikipedia.org/wiki/Autono...stem_(Internet)
Here are all the IP ranges in this particular one: https://www.whatismyip.com/asn/16276/
So far I have gotten this error messages for IP addresses falling within 51.38.0.0/16, 54.36.0.0/16, and 54.37.0.0/16 (none of which match my physical location but this is not entirely surprising for a multi-national service provider) -- note that a /16 is more than 65k IP addresses.
OK, "Operator: OVN" sort of explains it because, yes, as someone who administers my own email servers, I have gotten a lot of spam from OVH addresses in the past, so I get it, but
https://en.wikipedia.org/wiki/KPN
"Its mobile division, KPN Mobile, had more than 33 million subscribers in the Netherlands, Germany, Belgium, France, and Spain under different brand names. Through its ownership of several European Internet service providers, KPN also provides Internet access to 2.1 million customers"
https://en.wikipedia.org/wiki/Proximus
"Proximus [...] is the largest of Belgium's three mobile telecommunications companies"
I suggest that maybe banning the entire ASN isn't the best business decision...
The obvious temporary user workaround is to use a VPN, which lol: Consolidated "Problems Accessing FlyerTalk When Using A VPN" thread
(luckily I run my own VPN server at home)
Apr 15, 2022 | 10:51 pm
#4
Original Poster
Moderator: Hyatt, American Express; FlyerTalk Evangelist
Join Date: Jun 2015
Location: WAS
Programs: :rolleyes:, DL DM, AA EXP, UA Silver, Hyatt Glob, Mlife Noir (=> Marriott Amb), invol FT beta tester
Posts: 21,654
looks better now, thanks!