William, The plan is to carve out a /24 for "Estonia" and have special servers on it. This would be the same /24 I'd have to use if I were to put a legitimate POP there. This also means I don't conflict with the real Germany.
I am just worried about violating the 'rules' of these providers and getting myself blacklisted from submitting corrections. Afterall the traceroute will still show us hitting a router in Germany before it hits my network. Traceroutes aren't the end all be all but it's a tell-tale sign. I guess this is all ISP-reported info so it's not "illegal" or a violation in any way. -Nanoguser100 Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, April 21, 2021 4:31 PM, William Herrin <b...@herrin.us> wrote: > On Wed, Apr 21, 2021 at 12:35 PM nanoguser100 > nanoguser...@protonmail.com wrote: > > > providing cloud hosted desktop solutions for end users. > > I missed this on the first read. Virtual Desktop along the lines of > Azure Virtual Desktop, Google VDI or Amazon Workspaces. > > I would emphasize this; it'll help folks on the group offer better > information. > > > We are not a VPN per-se, it's more of a cloud hosted remote desktop > > service. We do have a VPN service as well which provides security services. > > That's a really interesting question. Some uses of geolocation will > give suboptimal results if you pick Estonia since the packets need to > go to Germany. Others, like content restriction, won't work right > unless the IPs reflect the users' location. > > Generally, I think the geolocation is represented as the rough region > where the servers are, with services that care about geolocation for > content restriction intentionally disallowing them. That's the safe > answer. For the alternative, I expect the different consumers of > geolocation services will have different opinions about it. > > > With that being said is it proper for transit providers to advertise the IP > > of their end users? > > Yes. > > > Are we considered a true transit provider since we are not an ISP per-se? > > No. It's not whether you're an ISP, the IP packets are stopping at > your network; you're not transiting them onward. > > Regards, > Bill Herrin > > -------------------------------------------------------------------------------------------------------------------------------------------- > > William Herrin > b...@herrin.us > https://bill.herrin.us/
