We are checking on the BR1 beta download firmware link issue and will update you shortly. For the network capture tools issue, Engineering team is checking on it as well .
Hello Peplink Team,
There are several requests and discussion in the forum for Geo-Blocking going back several years.
Is there any possibility that this may become available with FW 8.1.0 upon its upcoming release? It may be useful to let the community know if it can get done or why it can not get done.
Happy to Help,
Marcus
Hello @Venn,
I have an open ticket that @TK_Liew is looking after on a UBR, send TK a private message, it does not seam related, though worth asking.
Happy to help,
Marcus
The Geo-blocking or the correct name Region firewall/outbound policy is available since firmware device firmware version 8.0.1 & IC2 firmware version 2.8.2.
Hello @sitloongs,
I got all excited and then realised you have miss-read the requests that we consolidated here, your answer is on an Outbound policy. If you look at all of the requests, it is about the inbound firewall blocking based on the sources IP Geographically assigned locations (what country was that IP block assigned to).
Please dig a little bit deeper for us all on this request.
Appreciate your assistance,
Marcus
You can already do this.
In ic2, group level, network settings, select firewall rules.
Check-mark “Manage Firewall Rules on Balance and MAX devices”
Click create new rules set.
Under source/destination not only can you select Region but also SaaS.
No CSV import yet, but at least you can import from an already working config file.
That is a very challenge feature whereby the captive portal method used are different for different vendors. Auto signing in to the captive portal is very difficult. Some-more WIFI vendor can also easily change captive portal sign-in method for different version and this cause difficult to support on it.
My intent was not to auto login. I just need a browser window within the Balance, and it must allow a cookie to be set by the portal provider. I understand the cookie will ultimately time at which time someone has to log in and do it again. This would be the same as for example an iPhone connecting to a portal. During the connect process a browser-like window pops up.