DNS resolve issues on Ubuntu 24 LTS with f5fpc
Hi, Problems connecting to vpn after upgrading to ubuntu 24.04 | DevCentral After switching to Ubuntu 24 LTS, I encountered the connection issues as described here https://community.f5.com/discussions/TechnicalForum/problems-connecting-to-vpn-after-upgrading-to-ubuntu-24-04/329549 . Applying the fix symlinking /etc/resolv.conf made things work partly. What I am seeing is that, after connecting with f5fpc, /etc/resolv.conf contains the two nameservers of my vpn domain (great), but also still my local lan nameserver (192.168.1.1 , not so great). This makes that about 1 in 3 DNS requests for hosts on the vpn side fail. $ cat /etc/resolv.conf 17 │ nameserver 192.168.20.2 18 │ nameserver 192.168.20.25 19 │ nameserver 192.168.1.1 20 │ search . Any ideas what could be causing this ?Need to log the VPN Pool IP Address on the Edge Firewall Logs
Dears Greeting I am Using the F5 APM as a VPN Solution On the Edge Firewall Logs i can see ONLY the SELF IP Addresses and NOT the the Assigned VPN Pool IP Address that is configured under the Network Access Profile on the APM Config, I am Using a One Arm Deployment When i am try to remove the SNAT from the Virtual Server , and Network Access Profile on the APM interchangeably and with each other , I cannot reach the services
[Workaound] User required to manually start EPI and VPN in browsers
After upgrading to version 16.1.4 the users need to manually start the End Point Inspector and the Web Initiated VPN by clicking on a "Start" button. This is describe in this KB. I created a user-common.js that will automatically click on the start button for the user. However, please note that this workround works as of 3rd of November 2023, but might stop working in the future in different browsers. In order to activate the workaround you need to have an Access Policy of the Moden type. Then go to Customizations -> Advanced -> Acces Profiles -> <Your Access Profile> -> Common Add the followinf to the file user-common.js define(["require", "exports", "apmui"], function (require, exports, apmui_1) { "use strict"; Object.defineProperty(exports, "__esModule", { value: true }); var app = apmui_1.App.get(); app.subscribe(apmui_1.EventType.EPS_CHECK_PROGRESS, function (_, store) { var btns = document.getElementsByClassName("apmui-button"); if (btns.length == 0) { console.log("Failed to find button..."); return; } btns[0].click(); }); app.subscribe(apmui_1.EventType.DIALOG_OPEN, function (_, store) { setTimeout(function () { var dialog = document.getElementById("sna_auto_start_not_supported"); if (dialog == null) { console.log("Didn't find the right dialog"); return; } var btns = dialog.getElementsByClassName("apmui-button"); if (btns.length == 0) { console.log("Didn't find the start button"); return; } btns[0].click(); }, 100); }); }); If you have a better solution to this, please let me know. This was just what I came up with when asked by customers that the new "Start" button had created confusion among their users.
