As a default route, my wireless router is still on the route table but FortiClient is using it to keep connected to the VPN. Nice! And now, I can’t access to the internet. Link#19 is disappeared from default route. This local ip address is dynamic and it changes on every connection because DHCP is assigning this ip address. Now, the next hop should be my FortiClient local ip address. Yes, I decided to manipulate my routing table manually. Our VPN service is not using split-tunneling and link#19 OR 10.212.134.152 is should be the next hop for the default route with my wireless router at the same time. 10.212.134.152 is my local IP address which one is assigned by FortiClient. It’s okay.Īfter this, I connected to VPN via FortiClient and I re-checked my route table. 192.168.31.1 is my wireless router and default root it to my wireless router. I started to debugging to find a root cause and I checked the routing table before connect to VPN. I asked my colleagues about “are you having any issues with VPN and/or VPN speed?” and that they said “NO!” They are using a little bit older MacBookPro than mine with an Intel-based CPU and I thought it’s a normal situation because Intel-based versions are okay and stable. Normally, I have 100MB/sec internet speed. When I connected to VPN via FortiClient v6., it looks like connected but my internet speed is getting too slow. Sometimes I’m having some issues like “This component is not compatible with your CPU”. Previously, Apple was using an Intel-based CPU but now, they decided to run macOS with an ARM-based CPU and Apple called M1 for now.Ī lot of software not compatible with ARM. M1 MacBookPro is different than the others because it comes with a new CPU architecture. When I started to work for my company in March 2021, they gave me an M1 MacBookPro. I need to connect VPN via FortiClient to do my work and access some resources securely.

Fortinet client mac