PiVPN has come back to life btw in the latest release 
I think they allowed pull requests now
1 Like
Yep, as I said he’s committed to maintaining it again going forward, but a reasonable chunk of people have already moved and honestly wg is stupidly simple to deploy bare metal or docker at this point, I can see PiVPN usage declining for the original reasons it was archived sooner rather than later.
1 Like
Yeah true, WireGuard is definitely the way going forward. Even tailscale and the likes are good options for connecting to remote infrastructure
Even my Unifi cloud gateway ultra has a WireGuard server built in
1 Like
And client I think? My UDM SE does so can’t see why the ultra wouldn’t
1 Like
Yes, it can do a Wireguard Client too
1 Like
Any word on when the National Lottery website and app will be fixed
Not to in any way diminish the fact it should work, but jumping over to 4G on a mobile etc. will let you play/access it as a workaround. Most of the databases seem to have updated now, obviously the lottery may use an aggregate service or pull from one that hasn’t.
Although some are still showing outdated info on some fields, i’ve only got IPBase showing me as US based atm. Have a look with your IP here: IP Address Lookup | Geolocation
1 Like
That is what I have been doing just very frustrating at this stage
2 Likes
IP’s still not static and our latest one now located again in the US.
Hi,
Please see below re. the latest blocking.
Steve
---------- Forwarded message ---------
From: Michael Tan <[email protected]>
Date: Thu, 30 May 2024, 18:22
Subject: Re: [FortiGuard] IP Geolocation Request
To: contact_geoip <[email protected]>
Hello,
We originally got a geofeed from Yayzi at https://yayzi.co.uk/geofeed.csv provided us by Liam Mulryan. However, it appears that this link is broken, and the page cannot be found on Yayzi’s site. We recommend that you contact the party responsible for maintaining this system to provide us with a new geofeed link or to fix the geofeed site.
We are getting this current classification from cogent’s geofeed (https://geofeed.cogentco.com/geofeed.csv) “149.18.0.0/16,US,US-NJ,EDISON". We also recommend that you reach out to Cogent asking to fix the data in their geofeed file. Once they do this, it will automatically reflect in our data within a few business days.
In the meantime, we do have several workarounds available for this issue.
Our database includes the registration country data apart from geographic location data. If you want to use the “registration” location (GB in this case) of this IP range 149.18.86.0/23 in their firewall policy and their device is running FortiOS 6.4+, please refer to our documentation to modify the configuration of your policy
• Please make sure you are checking the guide in accordance with your FOS version.
Otherwise you could setup an exception policy (manual override) for this specific IP range 149.18.86.0/23 and other IP ranges experiencing similar issues.
• Geography based addresses | FortiGate / FortiOS 7.4.2 | Fortinet Document Library
• Please make sure you are checking the guide in accordance with your FOS version.
If you need help with either of these solutions you could contact our local support engineers or TAC team.
Let me know if you need more information.
Regards,
Michael Tan
Thanks for that Steve, that’s very odd. The geofeed should still be available. I’ll get right on that
Our IP’s are UK based. They go through a cleaning period, if there is a specific service you’re having issues with then we can get the Geo-location databases updated - But I don’t know who you are, so could you either DM me here or email [email protected]
1 Like