On 24 May 2024 23:23:44 BST, Andy Smith wrote:
>You will likely get better performance if you switch to nftables and
>use an ipset to hold all the bans, though I've no idea how easy
>that is to configure with fail2ban.
It's easy, supported out of the box. I have been using nftables for years w
Hi,
On Sat, May 25, 2024 at 06:04:34AM +0800, Northwind wrote:
> I have been using a KVM vps with 2G ram, 2 cores.
> due to fail2ban jobs, iptables in this vps has dropped 3000+ black IPs.
> may I ask how max iptables rules the VPS can have?
It depends upon the kind of rule but for a typical fail
Hello
I have been using a KVM vps with 2G ram, 2 cores.
due to fail2ban jobs, iptables in this vps has dropped 3000+ black IPs.
may I ask how max iptables rules the VPS can have?
does many iptables rules influence the networking performance?
Thanks
Hi,
On Fri, May 24, 2024 at 11:55:54AM -0700, Chip Smith wrote:
> convention as it pertains to the 127.0.0.1 iIP address is that it
> is meant to be used for testing purposes on a whole.
I am quite sure that plenty of production traffic goes over
localhost network connections on millions of serv
Greg Wooledge wrote:
> On Fri, May 24, 2024 at 01:49:58PM -0400, Jeffrey Walton wrote:
> > On Fri, May 24, 2024 at 1:46 PM Greg Wooledge
> > wrote:
> > >
> > > On Fri, May 24, 2024 at 01:40:38PM -0400, Jeffrey Walton wrote:
> > > > On Fri, May 24, 2024 at 11:13 AM Paul M Foster
> > > > wrote
Hello,
sometimes some cooperative sites had similar problems e.g MS's O365 or
Oracle's support site. In these cases removing stored cookies and
website data helped.
In addition cache can be deactivated in FF Developer Console
(Ctrl-Shift-k) in the tab "Network(ing)". Here you have a checkbox
Thr n convention as it pertains to the 127.0.0.1 iIP address is that it
is meant to be used for testing purposes on a whole.
Moore information may be found in the links below.
https://www.rfc-editor.org/info/rfc1085
https://www.rfc-editor.org/info/rfc1918
On 5/24/24 10:07, Paul M Foster w
On Fri, May 24, 2024 at 01:49:58PM -0400, Jeffrey Walton wrote:
> On Fri, May 24, 2024 at 1:46 PM Greg Wooledge wrote:
> >
> > On Fri, May 24, 2024 at 01:40:38PM -0400, Jeffrey Walton wrote:
> > > On Fri, May 24, 2024 at 11:13 AM Paul M Foster
> > > wrote:
> > > > 192.168.254.30 yosemite.mars.l
On Fri, 24 May 2024 13:08:56 -0400
Paul M Foster wrote:
> There is a colon in my aliases file. I just omitted it in the email.
Don't do that. Always use copy and paste to convey the contents of a
configuration file. Murphy only know what else you inadvertently left
out or added.
--
Does anybod
On Fri, May 24, 2024 at 1:46 PM Greg Wooledge wrote:
>
> On Fri, May 24, 2024 at 01:40:38PM -0400, Jeffrey Walton wrote:
> > On Fri, May 24, 2024 at 11:13 AM Paul M Foster
> > wrote:
> > > 192.168.254.30 yosemite.mars.lan yosemite
>
> > 127.0.1.1 is traditionally used for the fully qualified
On Fri 24 May 2024 at 13:40:38 (-0400), Jeffrey Walton wrote:
> On Fri, May 24, 2024 at 11:13 AM Paul M Foster
> wrote:
> >
> > Folks:
> >
> > In my /etc/hosts file, there's a line:
> >
> > 127.0.1.1 yosemite.mars.lan yosemite
> >
> > I think Debian put it there.
> >
> > Later in the file, I've g
On Fri, May 24, 2024 at 01:40:38PM -0400, Jeffrey Walton wrote:
> On Fri, May 24, 2024 at 11:13 AM Paul M Foster
> wrote:
> > 192.168.254.30 yosemite.mars.lan yosemite
> 127.0.1.1 is traditionally used for the fully qualified domain name
> (fqdn). So I would expect to see 'yosemite.mars.lan',
On Fri, May 24, 2024 at 11:13 AM Paul M Foster wrote:
>
> Folks:
>
> In my /etc/hosts file, there's a line:
>
> 127.0.1.1 yosemite.mars.lan yosemite
>
> I think Debian put it there.
>
> Later in the file, I've got:
>
> 192.168.254.30 yosemite.mars.lan yosemite
>
> So there are two entries for t
On Fri, May 24, 2024 at 05:22:13PM +0100, Joe wrote:
> Long ago, lo used to be just 127.0.0.1, which is what most people would
> try to ping to check localhost, and what appeared in /etc/hosts. There
> is some subtle reason, which I used to know but have now long forgotten,
> why Debian started usi
Paul M Foster writes:
[...]
> If I send an email directly to pa...@yosemite.mars.lan from buckaroo,
> it
What does this mean?
>
> But it appears that OpenSMTPD doesn't consult this table unless explicitly
> instructed to. According to man smtpd.conf(5), you can tell it to scan
> through aliases
On Fri 24 May 2024 at 13:08:56 (-0400), Paul M Foster wrote:
> On Fri, May 24, 2024 at 06:40:09PM +0200, to...@tuxteam.de wrote:
> > On Fri, May 24, 2024 at 11:45:56AM -0400, Paul M Foster wrote:
> >
> > > If I send an email directly to pa...@yosemite.mars.lan from buckaroo, it
> > > arrives. That
Hi,
Hans wrote:
> I am playing around with live-build.
This package has its own specialized mailing list:
debian-l...@lists.debian.org
Have a nice day :)
Thomas
On Fri, May 24, 2024 at 01:08:56PM -0400, Paul M Foster wrote:
> On Fri, May 24, 2024 at 06:40:09PM +0200, to...@tuxteam.de wrote:
>
> > On Fri, May 24, 2024 at 11:45:56AM -0400, Paul M Foster wrote:
> > > Folks:
> >
> > [...]
> >
> > > If I send an email directly to pa...@yosemite.mars.lan from
On Fri, May 24, 2024 at 05:23:55PM +0100, Joe wrote:
> On Fri, 24 May 2024 17:17:45 +0200
> wrote:
>
> > On Fri, May 24, 2024 at 04:49:18PM +0200, Marco Moock wrote:
> >
> > [...]
> >
> > > If you operate mail servers, you must have a FQDN. .lan can't be
> > > used for the global DNS stuff, so
On Fri, May 24, 2024 at 05:22:13PM +0100, Joe wrote:
> On Fri, 24 May 2024 11:40:30 -0400
> Greg Wooledge wrote:
>
> > On Fri, May 24, 2024 at 05:22:14PM +0200, Marco Moock wrote:
> > > Am 24.05.2024 um 17:17:45 Uhr schrieb to...@tuxteam.de:
> > >
> > > > On Fri, May 24, 2024 at 04:49:18PM +0
On Fri, May 24, 2024 at 06:40:09PM +0200, to...@tuxteam.de wrote:
> On Fri, May 24, 2024 at 11:45:56AM -0400, Paul M Foster wrote:
> > Folks:
>
> [...]
>
> > If I send an email directly to pa...@yosemite.mars.lan from buckaroo, it
> > arrives. That means this config can do what it's designed to
On Fri, 24 May 2024 11:40:30 -0400
Greg Wooledge wrote:
> On Fri, May 24, 2024 at 05:22:14PM +0200, Marco Moock wrote:
> > Am 24.05.2024 um 17:17:45 Uhr schrieb to...@tuxteam.de:
> >
> > > On Fri, May 24, 2024 at 04:49:18PM +0200, Marco Moock wrote:
> > >
> > > [...]
> > >
> > > > If you o
On Fri, May 24, 2024 at 11:45:56AM -0400, Paul M Foster wrote:
> Folks:
[...]
> If I send an email directly to pa...@yosemite.mars.lan from buckaroo, it
> arrives. That means this config can do what it's designed to do, basically.
> However, mails to "root" on buckaroo don't get to yosemite. They
On Fri, May 24, 2024 at 11:40:30AM -0400, Greg Wooledge wrote:
> On Fri, May 24, 2024 at 05:22:14PM +0200, Marco Moock wrote:
> > Am 24.05.2024 um 17:17:45 Uhr schrieb to...@tuxteam.de:
> >
> > > On Fri, May 24, 2024 at 04:49:18PM +0200, Marco Moock wrote:
> > >
> > > [...]
> > >
> > > > If you
Hello everyone,
I am playing around with live-build. So I see several packages
called "live-task-*" (for example live-task-xfce), but I can not see any
changes in the live-build tree, when I install them or not.
Checked through the manuals, but I found no information, what I have to do
with it
Folks:
This may require someone who's familiar with OpenSMTPD. I have a machine
which does backups (buckaroo) and a desktop (yosemite) which is my main
machine. When anacron kicks off the backup, it should create an email for
root to detail what happened. Buckaroo is headless, so I want that email
On Fri, May 24, 2024 at 05:22:14PM +0200, Marco Moock wrote:
> Am 24.05.2024 um 17:17:45 Uhr schrieb to...@tuxteam.de:
>
> > On Fri, May 24, 2024 at 04:49:18PM +0200, Marco Moock wrote:
> >
> > [...]
> >
> > > If you operate mail servers, you must have a FQDN. .lan can't be
> > > used for the gl
On Fri, May 24, 2024 at 05:22:14PM +0200, Marco Moock wrote:
> Am 24.05.2024 um 17:17:45 Uhr schrieb to...@tuxteam.de:
>
> > On Fri, May 24, 2024 at 04:49:18PM +0200, Marco Moock wrote:
> >
> > [...]
> >
> > > If you operate mail servers, you must have a FQDN. .lan can't be
> > > used for the gl
Am 24.05.2024 um 17:17:45 Uhr schrieb to...@tuxteam.de:
> On Fri, May 24, 2024 at 04:49:18PM +0200, Marco Moock wrote:
>
> [...]
>
> > If you operate mail servers, you must have a FQDN. .lan can't be
> > used for the global DNS stuff, so set a proper FQDN that belongs to
> > you.
>
> I think
On Fri, May 24, 2024 at 04:49:18PM +0200, Marco Moock wrote:
[...]
> If you operate mail servers, you must have a FQDN. .lan can't be used
> for the global DNS stuff, so set a proper FQDN that belongs to you.
I think this is wrong in that sweeping generality.
Cheers
--
t
signature.asc
Descri
Am 24.05.2024 um 08:05:43 Uhr schrieb Paul M Foster:
> In my /etc/hosts file, there's a line:
>
> 127.0.1.1 yosemite.mars.lan yosemite
>
> I think Debian put it there.
Should be there so the hostname is resolvable - even when not in DNS.
> Later in the file, I've got:
>
> 192.168.254.30 yose
Paul M Foster wrote:
> Folks:
>
> In my /etc/hosts file, there's a line:
>
> 127.0.1.1 yosemite.mars.lan yosemite
>
> I think Debian put it there.
>
> Later in the file, I've got:
>
> 192.168.254.30 yosemite.mars.lan yosemite
>
> So there are two entries for the same (my) machine. Is this
My notebook has Trixie for most packages, then some from Bookworm and a
few form Sid.
Pipewire used to output sound just fine until yesterday, when I upgraded
the whole system via aptitude and rebooted.
Until yesterday I also had rc-buggy in my sources-list, but then I
removed it (before the
On Fri, May 24, 2024 at 08:14:16AM -0400, Stephen P. Molnar wrote:
> E: Release file for
> http://debian.uchicago.edu/debian/dists/bookworm-updates/InRelease is
> expired (invalid since 1d 15h 6min 44s). Updates for this repository will
> not be applied.
Slightly worrisome.
> deb http://debian.uc
On Fri, May 24, 2024 at 08:05:43AM -0400, Paul M Foster wrote:
> Folks:
>
> In my /etc/hosts file, there's a line:
>
> 127.0.1.1 yosemite.mars.lan yosemite
>
> I think Debian put it there.
Correct. This is the address that will be used if you don't have a
static LAN address.
> Later in the fi
During a routine update I got the error:
E: Release file for
http://debian.uchicago.edu/debian/dists/bookworm-updates/InRelease is
expired (invalid since 1d 15h 6min 44s). Updates for this repository
will not be applied.
/etc/apt/sources.lis entries are:
# deb cdrom:[Debian GNU/Linux 12.5.0
Folks:
In my /etc/hosts file, there's a line:
127.0.1.1 yosemite.mars.lan yosemite
I think Debian put it there.
Later in the file, I've got:
192.168.254.30 yosemite.mars.lan yosemite
So there are two entries for the same (my) machine. Is this a problem?
Specifically, could it cause problem
Hi folks,
if I migrate from grub-pc to grub-uefi, then grub-pc.postrm
removes /etc/default/grub on the final purge.
grub2 doesn't provide much information in its man pages, but
AFAICT /etc/default/grub is still processed for UEFI, so why
is it deleted?
Regards
Harri
38 matches
Mail list logo
