First: as others mentioned, tcpdump isn't suited for output rotation
via tools like newsyslog. Even if you manage to restart it with new
log, you'll probably skip some packets. You might implement some sort
of overlap (you start tcpdump to a new file, *then* you kill the old
one and write a tool to
On Sun, 10 Apr 2022 17:00:25 -0400
Nick Holland wrote:
> On 4/10/22 9:39 AM, Yogendra Kumar Chaudhary wrote:
> > I am running the following command in the OpenBSD 6.2.
You should really upgrade. That version no longer gets security patches
for several years.
> So, I'm thinking you probably want
On 4/10/22 9:39 AM, Yogendra Kumar Chaudhary wrote:
Good Evening Community,
I am running the following command in the OpenBSD 6.2.
*"tcpdump -Nneqt -w tcpdump.pcap -i vic0 &"*
and using the following newsyslog.conf entry for rotating the tcpdump.pcap
# logfile_name owner:group mo
Good Evening Community,
I am running the following command in the OpenBSD 6.2.
*"tcpdump -Nneqt -w tcpdump.pcap -i vic0 &"*
and using the following newsyslog.conf entry for rotating the tcpdump.pcap
# logfile_name owner:group mode count size when flags
/home/logs/tcpdump.pcap
Hello,
I configured an Openbsd system as a VPN server with IKEV2.
It works great but I'd like to use a configuration with different policies
on per-user basis.
The clients connect from dynamic ip.
Does anybody have any hint or alternative?
thanks 😊
5 matches
Mail list logo
