On Fri Sep29'23 11:44:08PM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Fri, 29 Sep 2023 23:44:08 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/29/23 20:58, Ranja
On Fri Sep29'23 11:44:08PM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Fri, 29 Sep 2023 23:44:08 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/29/23 20:58, Ranja
On 9/29/23 20:58, Ranjan Maitra wrote:
Thanks!
On 9/28/23 19:03, Ranjan Maitra wrote:
On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
The problem is that the VPN is setting its options on the global state
instead of the tunnel where they should be. Normally, when the tunnel goes
away, so do
Thanks!
> On 9/28/23 19:03, Ranjan Maitra wrote:
> > On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
> > > The problem is that the VPN is setting its options on the global state
> > > instead of the tunnel where they should be. Normally, when the tunnel
> > > goes
> > > away, so do the special s
On 9/28/23 19:03, Ranjan Maitra wrote:
On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
The problem is that the VPN is setting its options on the global state
instead of the tunnel where they should be. Normally, when the tunnel goes
away, so do the special settings for it, but here they're globa
On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Thu, 28 Sep 2023 10:32:55 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/28/23
On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Thu, 28 Sep 2023 10:32:55 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/28/23
On 9/28/23 05:02, Ranjan Maitra wrote:
$ resolvectl dns
Global: [IP addresses associated with my VPN site] {*}
Link 2 (enp57s0u2u1u1): [IP addresses associated with my ISP] 192.168.1.1 {**}
Link 22 (cscotun0):
$ resolvectl domain
Global: [VPN connection domainname] [ISP]
Link 2 (
Thank you!
On Wed Sep27'23 03:04:53PM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Wed, 27 Sep 2023 15:04:53 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/27/23
On 9/27/23 09:14, Ranjan Maitra wrote:
From the past week, I have had an issue in that after several hours, some
particular sites become inaccessible to me, and can only be accessed if I use
restart using sudo systemctl restart systemd-resolved.service
What particular issues cause this? Why
wrote:
> From: Joe Zeff
> Date: Wed, 27 Sep 2023 10:24:00 -0600
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 09/27/2023 10:14 AM, Ranjan Maitra wrote:
> > From the past week, I
On 09/27/2023 10:14 AM, Ranjan Maitra wrote:
From the past week, I have had an issue in that after several hours, some
particular sites become inaccessible to me, and can only be accessed if I use
restart using sudo systemctl restart systemd-resolved.service
Before any of us can help you, we
Dear friends,
From the past week, I have had an issue in that after several hours, some
particular sites become inaccessible to me, and can only be accessed if I use
restart using sudo systemctl restart systemd-resolved.service
What particular issues cause this? Why did it start a week ago, an
13 matches
Mail list logo
