On Thu 02 Mar 2023 at 10:32:41 (+0100), daven...@tuxfamily.org wrote:
> On 2023-03-02 00:24, David Wright wrote:
> > On Tue 28 Feb 2023 at 16:05:14 (+0100), daven...@tuxfamily.org wrote:
> > > On 2023-02-28 05:27, David Wright wrote:
> > > > On Thu 23 Feb 2023 at 11:23:30 (+0100),
On Thu, Mar 02, 2023 at 12:14:14PM -0600, David Wright wrote:
> On Thu 02 Mar 2023 at 17:23:23 (-), Curt wrote:
> > On 2023-03-02, David wrote:
[...]
> > Those seem like antithetical concepts.
>
> The state is identical in both cases, hence using the same letter.
> OTOH the paths to that
On Thu 02 Mar 2023 at 17:23:23 (-), Curt wrote:
> On 2023-03-02, David wrote:
> > On Fri, 3 Mar 2023 at 00:19, Greg Wooledge wrote:
> >
> >> Man, I really wish the aptitude(8) man page would explain how to read
> >> the output of "why". What does the "p" mean? Purged? There's nothing
> >>
On 2023-03-02, David wrote:
> On Fri, 3 Mar 2023 at 00:19, Greg Wooledge wrote:
>
>> Man, I really wish the aptitude(8) man page would explain how to read
>> the output of "why". What does the "p" mean? Purged? There's nothing
>> in the man page that explains the symbols in the first 3
On Fri, 3 Mar 2023 at 02:18, wrote:
> On 2023-03-02 14:19, Greg Wooledge wrote:
> > On Thu, Mar 02, 2023 at 02:01:57PM +0100, daven...@tuxfamily.org wrote:
> >> > > > akb@akira:~$ LC_ALL=C aptitude why ifupdown
> >> > > > p netscript-2.4 Provides ifupdown
> >> > > > p netscript-2.4 Depends
On 2023-03-02 14:19, Greg Wooledge wrote:
On Thu, Mar 02, 2023 at 02:01:57PM +0100, daven...@tuxfamily.org wrote:
> > > akb@akira:~$ LC_ALL=C aptitude why ifupdown
> > > p netscript-2.4 Provides ifupdown
> > > p netscript-2.4 Depends bridge-utils (>= 0.9.3)
> > > p bridge-utils
On Fri, 3 Mar 2023 at 00:19, Greg Wooledge wrote:
> Man, I really wish the aptitude(8) man page would explain how to read
> the output of "why". What does the "p" mean? Purged? There's nothing
> in the man page that explains the symbols in the first 3 columns, as
> far as I can find.
Yeah.
On Thu, Mar 02, 2023 at 02:01:57PM +0100, daven...@tuxfamily.org wrote:
> > > > akb@akira:~$ LC_ALL=C aptitude why ifupdown
> > > > p netscript-2.4 Provides ifupdown
> > > > p netscript-2.4 Depends bridge-utils (>= 0.9.3)
> > > > p bridge-utils Suggests ifupdown
> > > > akb@akira:~$
On 2023-03-02 13:47, daven...@tuxfamily.org wrote:
On 2023-03-02 13:32, Greg Wooledge wrote:
On Thu, Mar 02, 2023 at 10:32:41AM +0100, daven...@tuxfamily.org
wrote:
This system never had any debian 10 or lower. It has been issued to
my by
$worksplace
in december 2021, initially running
On 2023-03-02 13:32, Greg Wooledge wrote:
On Thu, Mar 02, 2023 at 10:32:41AM +0100, daven...@tuxfamily.org wrote:
This system never had any debian 10 or lower. It has been issued to my
by
$worksplace
in december 2021, initially running windows.
akb@akira:~$ LC_ALL=C aptitude why ifupdown
p
On Thu, Mar 02, 2023 at 10:32:41AM +0100, daven...@tuxfamily.org wrote:
> This system never had any debian 10 or lower. It has been issued to my by
> $worksplace
> in december 2021, initially running windows.
> akb@akira:~$ LC_ALL=C aptitude why ifupdown
> p netscript-2.4 Provides ifupdown
> p
On 2023-03-02 00:24, David Wright wrote:
On Tue 28 Feb 2023 at 16:05:14 (+0100), daven...@tuxfamily.org wrote:
On 2023-02-28 05:27, David Wright wrote:
> On Thu 23 Feb 2023 at 11:23:30 (+0100), daven...@tuxfamily.org wrote:
> > On 2023-02-23 02:59, cono...@panix.com wrote:
[ … ]
Well, it
On Tue 28 Feb 2023 at 16:05:14 (+0100), daven...@tuxfamily.org wrote:
> On 2023-02-28 05:27, David Wright wrote:
> > On Thu 23 Feb 2023 at 11:23:30 (+0100), daven...@tuxfamily.org wrote:
> > > On 2023-02-23 02:59, cono...@panix.com wrote:
> > >
> > > […]
> > >
> > > On the newer work laptop on
On Tue, 2023-02-28 at 16:05 +0100, daven...@tuxfamily.org wrote:
>
> It's the systemd-style so-called "predictable" interfaces names.
> Replacing the older the eth0, wlan0, and so on…
>
> ens-something (annoying name made of multiple letters and digits) is the
> new name for eth0
Or eno for
On 2023-02-28 05:27, David Wright wrote:
On Thu 23 Feb 2023 at 11:23:30 (+0100), daven...@tuxfamily.org wrote:
On 2023-02-23 02:59, cono...@panix.com wrote:
[…]
On the newer work laptop on the other hand, there is that eth0 block,
there's is no eth0 interface on my system (there's enp.* and
On Thu 23 Feb 2023 at 11:23:30 (+0100), daven...@tuxfamily.org wrote:
> On 2023-02-23 02:59, cono...@panix.com wrote:
> > On 2/22/23, daven...@tuxfamily.org wrote:
> > >
> > > There is an unidentified process that decides it's ok to delete and
> > > recreate /etc/resolv.conf without asking
On Mon, Feb 27, 2023 at 03:14:40PM +0100, daven...@tuxfamily.org wrote:
> I did
>
> - chattr +i /etc/revolv.conf
>
> And when auditd showed a (failed) delete event on /etc/resolv.conf
>
> I grepped "resolv.conf" recursively on /var/log/, and All I've found are
> entries in
>
> -
Hello
On 2023-02-24 11:27, daven...@tuxfamily.org wrote:
On 2023-02-24 10:27, to...@tuxteam.de wrote:
On Fri, Feb 24, 2023 at 10:19:38AM +0100, daven...@tuxfamily.org
wrote:
[...]
BUT I will make sure to take some time to dig into the logs monday.
Now that I have an idea what I'm looking
On Fri 24 Feb 2023 at 10:19:38 (+0100), daven...@tuxfamily.org wrote:
> > […]
> > vpnc_script has about eight methods available for setting up and
> > reverting resolv.conf. Which is used depends on the presence of
> > a binary, checked in turn from this list:
> >
> > /etc/openwrt_release
On Fri, Feb 24, 2023 at 10:19:38AM +0100, daven...@tuxfamily.org wrote:
> However, I didn't notice any vnpc_script malfunction. It does what it is
> expected to do. I'm like 99% sure the problem is dhclient deleting and
> recreating /etc/resolv.conf as it sees fit, multiple times a day, and
>
On Fri, Feb 24, 2023 at 11:27:40AM +0100, daven...@tuxfamily.org wrote:
> [...] totally agree logs are better than suspicion
But please, don't take my snark all too seriously. On reread I
realize it might have sounded harsher than it was meant.
Cheers
--
t
signature.asc
Description: PGP
On 2023-02-24 10:27, to...@tuxteam.de wrote:
On Fri, Feb 24, 2023 at 10:19:38AM +0100, daven...@tuxfamily.org wrote:
[...]
However, I didn't notice any vnpc_script malfunction. It does what it
is
expected to do. I'm like 99% sure the problem is dhclient deleting and
recreating
On Fri, Feb 24, 2023 at 10:19:38AM +0100, daven...@tuxfamily.org wrote:
[...]
> However, I didn't notice any vnpc_script malfunction. It does what it is
> expected to do. I'm like 99% sure the problem is dhclient deleting and
> recreating /etc/resolv.conf as it sees fit, multiple times a day,
Hello,
[…]
vpnc_script has about eight methods available for setting up and
reverting resolv.conf. Which is used depends on the presence of
a binary, checked in turn from this list:
/etc/openwrt_release modify_resolvconf_openwrt
/usr/bin/resolvectl
On Thu, Feb 23, 2023 at 11:39:03PM -0600, David Wright wrote:
[...]
> vpnc_script has about eight methods available for setting up and
> reverting resolv.conf. Which is used depends on the presence of
> a binary, checked in turn from this list:
>
> /etc/openwrt_release
On Thu 23 Feb 2023 at 10:44:35 (+0100), daven...@tuxfamily.org wrote:
> On 2023-02-22 22:08, David Wright wrote:
> > On Wed 22 Feb 2023 at 18:12:29 (+0100), daven...@tuxfamily.org wrote:
> >
> > > What I want is: setting up /etc/resolv.conf ONLY
> > > - at system startup/initial network
Hi.
On Thu, Feb 23, 2023 at 11:31:44AM +0100, daven...@tuxfamily.org wrote:
> > If it is DHCP: You might do a countermeasure in
> > /etc/dhcp/dhclient.conf. On my system I have an entry as below.
> >
> > interface "wlp4s0" {
> > supersede domain-name-servers 127.0.0.1;
>
>
On 2023-02-23 10:54, to...@tuxteam.de wrote:
On Thu, Feb 23, 2023 at 10:44:35AM +0100, daven...@tuxfamily.org wrote:
[...]
Thank you. I'll give it a try, But I won't be on remote work before
next
week
Which log file is used for that?
That depends: it's the perpetrator's choice where to log
On 23/2/23 18:23, daven...@tuxfamily.org wrote:
Hello,
On 2023-02-23 02:59, cono...@panix.com wrote:
On 2/22/23, daven...@tuxfamily.org wrote:
There is an unidentified process that decides it's ok to delete and
recreate /etc/resolv.conf without asking user/admin,
The problem is, the
Hi
On 2023-02-22 18:30, Christoph Brinkhaus wrote:
Am Wed, Feb 22, 2023 at 06:12:29PM +0100 schrieb
daven...@tuxfamily.org:
= context =
For the context, I use a Debian 11 laptop for work. When I work
remotely
from home, I have to use a cisco VPN. Good thing is there is
Hello,
On 2023-02-23 02:59, cono...@panix.com wrote:
On 2/22/23, daven...@tuxfamily.org wrote:
There is an unidentified process that decides it's ok to delete and
recreate /etc/resolv.conf without asking user/admin,
The problem is, the problematic process is not work's VPN related and
On Thu, Feb 23, 2023 at 10:44:35AM +0100, daven...@tuxfamily.org wrote:
[...]
> Thank you. I'll give it a try, But I won't be on remote work before next
> week
> Which log file is used for that?
That depends: it's the perpetrator's choice where to log (or whether
to log at all, sadly).
> So
Hello
On 2023-02-22 22:08, David Wright wrote:
On Wed 22 Feb 2023 at 18:12:29 (+0100), daven...@tuxfamily.org wrote:
What I want is: setting up /etc/resolv.conf ONLY
- at system startup/initial network connexion.
- when openconnect is executed and connects to work's VPN
- when openconnect is
On 2/22/23, daven...@tuxfamily.org wrote:
>
> There is an unidentified process that decides it's ok to delete and
> recreate /etc/resolv.conf without asking user/admin,
> The problem is, the problematic process is not work's VPN related and
> creates the file with wrong resolver's IP. The IP
On 2/22/23, daven...@tuxfamily.org wrote:
>
> There is an unidentified process that decides it's ok to delete and
> recreate /etc/resolv.conf without asking user/admin,
> The problem is, the problematic process is not work's VPN related and
> creates the file with wrong resolver's IP. The IP
On Wed 22 Feb 2023 at 18:12:29 (+0100), daven...@tuxfamily.org wrote:
> What I want is: setting up /etc/resolv.conf ONLY
> - at system startup/initial network connexion.
> - when openconnect is executed and connects to work's VPN
> - when openconnect is ^C-ed and disconnects from the works VPN
>
On Wed, Feb 22, 2023 at 06:12:29PM +0100, daven...@tuxfamily.org wrote:
> There is an unidentified process that decides it's ok to delete and recreate
> /etc/resolv.conf without asking user/admin,
> The problem is, the problematic process is not work's VPN related and
> creates the file with wrong
Am Wed, Feb 22, 2023 at 06:12:29PM +0100 schrieb daven...@tuxfamily.org:
>
> = context =
> For the context, I use a Debian 11 laptop for work. When I work remotely
> from home, I have to use a cisco VPN. Good thing is there is openconnect,
> which does work, and in teh case of ym
On Wed, Feb 22, 2023 at 06:12:29PM +0100, daven...@tuxfamily.org wrote:
>
> There is an unidentified process that decides it's ok to delete and recreate
> /etc/resolv.conf without asking user/admin,
I will admit up front that I did not read your message in great detail.
However, overall it seems
Hello,
= context =
For the context, I use a Debian 11 laptop for work. When I work remotely
from home, I have to use a cisco VPN. Good thing is there is
openconnect, which does work, and in teh case of ym work's VPN, it does
wor. cisco's spyware/downloaded binry, namely using
40 matches
Mail list logo
