Re: Strange VPN behaviour

2021-05-20 Thread Ed Greshko
On 20/05/2021 22:19, Anca, Tibor wrote: Hello, Am Donnerstag, dem 20.05.2021 um 21:46 +0800 schrieb Ed Greshko: But, is the above with or without the /etc/hosts entry? I just checked, it is with added entry, with established VPN-Connection. How about with the entry removed? -- Remind me to

Re: Strange VPN behaviour

2021-05-20 Thread Kevin Becker
On Thu, 2021-05-20 at 12:59 +, Anca, Tibor wrote: > Am Donnerstag, dem 20.05.2021 um 19:33 +0800 schrieb Ed Greshko: > > Does > > > > host host.name.de 192.168.3.33 > > > > Return the IP address you expect? > Yes. But it also returns: > > Host xyz not found: 3(NXDOMAIN) Are you trying to u

Re: Strange VPN behaviour

2021-05-20 Thread Anca, Tibor
Hello, Am Donnerstag, dem 20.05.2021 um 21:46 +0800 schrieb Ed Greshko: > > But, is the above with or without the /etc/hosts entry? I just checked, it is with added entry, with established VPN-Connection. -- Dr. Tibor Attila Anca Pastor Ev.-luth. Kirchengemeinde Dollbergen-Schwüblingsen Fuhsest

Re: Strange VPN behaviour

2021-05-20 Thread Ed Greshko
On 20/05/2021 20:59, Anca, Tibor wrote: Am Donnerstag, dem 20.05.2021 um 19:33 +0800 schrieb Ed Greshko: Does host host.name.de 192.168.3.33 Return the IP address you expect? Yes. But it also returns: Host xyz not found: 3(NXDOMAIN) One of my problems is I can't find a way to give sound ad

Re: Strange VPN behaviour

2021-05-20 Thread Anca, Tibor
Am Donnerstag, dem 20.05.2021 um 19:33 +0800 schrieb Ed Greshko: > Does > > host host.name.de 192.168.3.33 > > Return the IP address you expect? Yes. But it also returns: Host xyz not found: 3(NXDOMAIN) ___ users mailing list -- users@lists.fedoraproje

Re: Strange VPN behaviour

2021-05-20 Thread Ed Greshko
On 20/05/2021 19:27, Anca, Tibor wrote: Hi, Am Donnerstag, dem 20.05.2021 um 19:14 +0800 schrieb Ed Greshko: How are you specifying the hostname you want to reach on the remote side? If you are just using "Aname" then when the request is sent to 192.168.3.33 it will become a request for an A (o

Re: Strange VPN behaviour

2021-05-20 Thread Anca, Tibor
Am Mittwoch, dem 19.05.2021 um 21:24 -0400 schrieb Kevin Becker: > > > > Is the search domain that is added to resolv.conf the correct domain > for your work that you are trying to access? Yes, it is the same which is added by AnyConnect. > I have two domains at my workplace and only one of th

Re: Strange VPN behaviour

2021-05-20 Thread Anca, Tibor
Hi, Am Donnerstag, dem 20.05.2021 um 19:14 +0800 schrieb Ed Greshko: > How are you specifying the hostname you want to reach on the remote > side? > > If you are just using "Aname" then when the request is sent to > 192.168.3.33 it will become > a request for an A (or ) record for "Aname.vpn.d

Re: Strange VPN behaviour

2021-05-20 Thread Anca, Tibor
Hi, Am Mittwoch, dem 19.05.2021 um 20:10 -0400 schrieb John Mellor: > A good VPN does this on purpose - adding ip addresses to what is on > the > corporate network is a very bad thing from a security standpoint.  If > you can do that, your admin guys should probably block you.  Yes, you > like y

Re: Strange VPN behaviour

2021-05-20 Thread Ed Greshko
On 20/05/2021 18:49, Anca, Tibor wrote: Link 5 (vpn0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 192.168.3.33 DNS Servers: 192.168.3.33 192.168.3.133 DNS Domain: vpn.domain.d

Re: Strange VPN behaviour

2021-05-20 Thread Anca, Tibor
Hello, Am Donnerstag, dem 20.05.2021 um 08:46 +0800 schrieb Ed Greshko: > > disconnected My output on disconnected is: Global Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 2 (enp2s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 Pr

Re: Strange VPN behaviour

2021-05-19 Thread Kevin Becker
> On May 19, 2021, at 5:52 PM, Anca, Tibor wrote: > > > I i use openconnect (which I prefer, because it keeps my network printer > available), it doenst do almost anything with resolve.conf. It only adds > a search entry, no dns, nothing. In this case I have to enter the ip > address of the ser

Re: Strange VPN behaviour

2021-05-19 Thread Ed Greshko
On 20/05/2021 07:22, Anca, Tibor wrote: Am Mittwoch, dem 19.05.2021 um 15:20 -0700 schrieb Samuel Sieb: Is there any indication in logs that openconnect is getting DNS info? you can add the DNS info.  I think systemd-resolved is supposed to be should get all requests. Where do I see those logs?

Re: Strange VPN behaviour

2021-05-19 Thread John Mellor
On 2021-05-19 5:52 p.m., Anca, Tibor wrote: I'm using Fedora 34. For some services I need to connect to my corporate VPN (Cysco). I use openconnect with NetworkManager, which connects fine to the vpn server. But there is a weird problem and I can not figure out, where to change something. If I

Re: Strange VPN behaviour

2021-05-19 Thread Anca, Tibor
Am Mittwoch, dem 19.05.2021 um 15:20 -0700 schrieb Samuel Sieb: > Is there any indication in logs that openconnect is getting DNS info? > you can add the DNS info.  I think systemd-resolved is supposed to be > should get all requests. Where do I see those logs? If I run systemctl status systemd-

Re: Strange VPN behaviour

2021-05-19 Thread Samuel Sieb
On 2021-05-19 2:52 p.m., Anca, Tibor wrote: I'm using Fedora 34. For some services I need to connect to my corporate VPN (Cysco). I use openconnect with NetworkManager, which connects fine to the vpn server. But there is a weird problem and I can not figure out, where to change something. If I u