Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 12 replies
  • Subscribers 28 subscribers
  • Views 1130 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

VPN does not resolve local hosts on linux

oldgoodname

Hi guys,

I am using a Sophos XG v19 as gateway and try to connect via SSL VPN from a Linux notebook.

I configured the SSL VPN as in the sophos own video-tutorial and I found some other tutorials showing the same steps.

When I try to connect from terminal, it works fine, except the DNS resolution. The DNS resolves only public domain-entries. So I think it uses a public-dns-server.

I tried different SSL Settings, configuring no dns or the IP of the sophos itself, because the sophos firewall is the internal dns server.  I also activated the "Use as default Gateway" switch, for not having a split-tunnel.

I think everything should be correct, but I am not able to ping internal hosts by there fqdn, but IP address works fine. So I think the DNS could be wrong. I checkt the /etc/resolv.conf, but there is only one entry showing up:

# Generated by Network Manager

nameserver127.0.0.53

So I am not sure, which one really is in use, when connected by VPN. When I am connected directly to the lan, the DNS on the Sophos firewall works without problems.

I also tried to import the config file into the network manager, which works. But when I try to connect, password field always shows up, so I think it does not work generally or with MFA, or I did it wrong.

So my 2 questions are:

  1. Do you have any suggestion, what to configure, that resolving local DNS host is possible via VPN?
  2. How to correctly import the sophos openvpn config file into the network manager, and where to type in the password and where the MFA token, that i correctly works? -> I would prefer this over connecting via terminal.

I currently use KDEneon distribution.

Thanks a lot in advance and best regards



Edited TAGs
[edited by: Erick Jan at 6:25 AM (GMT -8) on 15 Nov 2022]
Parents
  • 0

    DNS server (this is a hierarchical system that allows you to forward requests to other servers and find answers). You cannot resolve localhost DNS unless you have a DNS server with an entry for localhost. Try setting it up on a Linux host. Note that Meraki does not have a DNS server (some firewalls do).


    hostname resolution in the office-This works for some hosts on the same VLAN, but over broadcast, not over DNS. IT does not work between subnets (different VLANs). Again, the answer is: Implement a DNS server.


    MAC Address Resolution-MAC addresses apply only to the local LAN segment (same physical network). In this case, it is the same VLAN. Therefore, Mac addresses such as remote VPN hosts will not be resolved.

    This may help,
    J Wick

Reply
  • 0

    DNS server (this is a hierarchical system that allows you to forward requests to other servers and find answers). You cannot resolve localhost DNS unless you have a DNS server with an entry for localhost. Try setting it up on a Linux host. Note that Meraki does not have a DNS server (some firewalls do).


    hostname resolution in the office-This works for some hosts on the same VLAN, but over broadcast, not over DNS. IT does not work between subnets (different VLANs). Again, the answer is: Implement a DNS server.


    MAC Address Resolution-MAC addresses apply only to the local LAN segment (same physical network). In this case, it is the same VLAN. Therefore, Mac addresses such as remote VPN hosts will not be resolved.

    This may help,
    J Wick

Children
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?

Unfiltered HTML