Earlier today I enabled OpenVPN by uploading an ovpn file to the router. It did this successfully and I am able to see the connector on my account. However, now I can't access the admin panel, not is the router connected to the internet.
I read that installing VPN will change the IP address of the admin panel. I found the IP address of the connection, but I still can't connect using that address.
Could you please tell me what I'm doing wrong? Do I need to reset the router?
No, you are not right in this part. The admin panel should always be 192.168.8.1.
To check further, you need to give more info, including router model, firmware version and ovpn config etc.
I just got a case that the opvn tunnel tries to use 192.168.8.1/24 subnet and breaks the firmware.
I figured out how to get the IP address of the router, it is now 192.168.2.1
I used that address as the admin panel, and switched off the VPN connector. Internet now working, but VPN is switched off
Hi,
For further check this issue, please provide OpenVPN configuration of the server and client, router model with which firmware version, and shows us the topology figure might be better if your network is complex.
Gl-ax1800 flint router (firmware version 4.5.16), connected by wan to TP-Link modem router, connected to NBN (Australia). I can't get rid of TP-Link router as I have my landline phone connected to it.
I use OpenVPN connexa connect client on my devices, set up server on open VPN, flint router set up with site-to- site connector with ovpn file from the server
Is it your topology? (although without line-phone)
Topology
GL with OpenVPN client - TP-Link - NBN router - public internet - connexa OpenVPN server
Syslog
Thu Jun 27 21:45:11 2024 daemon.info avahi-daemon[4126]: Leaving mDNS multicast group on interface ovpnclient.IPv4 with address 100.96.1.18.
Thu Jun 27 21:45:11 2024 daemon.info avahi-daemon[4126]: Withdrawing address record for 100.96.1.18 on ovpnclient.
Thu Jun 27 21:45:11 2024 daemon.info avahi-daemon[4126]: Joining mDNS multicast group on interface ovpnclient.IPv4 with address 100.96.1.18.
Thu Jun 27 21:45:11 2024 daemon.info avahi-daemon[4126]: New relevant interface ovpnclient.IPv4 for mDNS.
Thu Jun 27 21:45:11 2024 daemon.info avahi-daemon[4126]: Registering new address record for 100.96.1.18 on ovpnclient.IPv4.
Thu Jun 27 21:45:11 2024 daemon.notice netifd: Interface 'ovpnclient' is now up
Thu Jun 27 21:45:11 2024 daemon.notice netifd: Network device 'ovpnclient' link is up
Thu Jun 27 21:45:11 2024 daemon.notice netifd: ovpnclient (1023): route: SIOCDELRT: No such process
Thu Jun 27 21:45:11 2024 daemon.notice netifd: ovpnclient (1023): route: SIOCDELRT: No such process
Thu Jun 27 21:45:11 2024 daemon.notice netifd: ovpnclient (1023): route: SIOCDELRT: No such process
Thu Jun 27 21:45:11 2024 daemon.notice netifd: ovpnclient (1023): route: SIOCDELRT: No such process
Thu Jun 27 21:45:11 2024 user.notice firewall: Reloading firewall due to ifup of ovpnclient (ovpnclient)
Thu Jun 27 21:45:11 2024 daemon.err ovpnclient[1023]: write UDP: Operation not permitted (code=1)
Thu Jun 27 21:45:11 2024 daemon.err ovpnclient[1023]: write UDP: Operation not permitted (code=1)
Thu Jun 27 21:45:11 2024 daemon.err ovpnclient[1023]: write UDP: Operation not permitted (code=1)
Thu Jun 27 21:45:11 2024 daemon.err ovpnclient[1023]: write UDP: Operation not permitted (code=1)
Thu Jun 27 21:45:11 2024 daemon.err ovpnclient[1023]: write UDP: Operation not permitted (code=1)
Thu Jun 27 21:45:11 2024 daemon.err ovpnclient[1023]: write UDP: Operation not permitted (code=1)
Thu Jun 27 21:45:11 2024 daemon.err ovpnclient[1023]: write UDP: Operation not permitted (code=1)
Thu Jun 27 21:45:13 2024 daemon.notice ovpnclient[1023]: Initialization Sequence Completed
The server you are connecting to is probably an Online VPN Service Provider, which uses push "redirect-gateway" to send ALL your client data over the VPN. To stop this you can add route-nopull to your client config file.
