the way.
All the best,
Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
hink you would need to explain what you think is misssing here.
Taking a peek at
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/ugen.c
right now I can see clearly CVS Tags: for each commit.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsd
s been *quite a while* since I attempted running with that kind
of setup myself but I distinctly remember Microsoft systems tended to
have their very own way to deal with time zone changes, and multibooting
systems would run into situations like the one you describe.
- Peter
--
Peter N. M. Hanst
On Tue, Apr 01, 2025 at 09:17:03AM -0400, Sven F. wrote:
> April fools ?
entirely possible
As could be of course the thing that triggered
https://mastodon.social/@pitrh/114262855940544666
(but less likely I think)
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation t
; > connected to the LAN switch with this setup?
>
> The gateway is on 192.168.1.1, the lan is on 192.168.0/24. It is just the way
> it is.
The easy solution then would be to stick
192.168.1.1
in /etc/mygate, then run doas sh /etc/netstart or equivalent
--
Peter N. M. Hansteen, member
instead to blame the tools at hand
is likely a career limiting move.
At that point we could be hearing strongly worded demands that all
traces of the current message thread be removed. If anyone wants
to bet on the probabilities of these things occurring, be my guest.
--
Peter N. M. Hansteen
se try again, and if it still does not work, please report the actual
error.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic&quo
-shooting, of course.
I would recommend taking a long hard look at whether the network design you
describe
is actually suited for your purpose.
That said, there may well be factors in play that have not come to light here.
Have fun!
--
Peter N. M. Hansteen, member of the first RFC 1149 imple
ld check
to make sure that it does.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
nlightening, you could do worse than turn to my stuff, such as
this piece -
https://nxdomain.no/~peter/what_every_it_person_needs_to_know_about_openbsd.html
(also published elsewhere, links therein)
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com
ave an IPv6 addess assigned.
Well spotted, Jon!
All the best,
Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah
a problem with slow response from that network's
DHCP service, for example?
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network t
The Call for Talk and Presentation proposals for EuroBSDCon 2025 is now open.
Enter your submission at https://events.eurobsdcon.org/2025/
Please also visit the main website https://2025.eurobsdcon.org/ for information
about the conference.
See you in Zagreb!
--
Peter N. M. Hansteen, member
trying again later worked, the machine
is up with
OpenBSD 7.6-current (GENERIC.MP) #569: Fri Feb 28 00:55:14 MST 2025
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
so I guess all that ends well is well :)
All the best,
Peter
--
Peter N. M. Hansteen, member of the f
best,
Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
right direction.
All the best,
Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
version
a little while back (the exact time escapes me but can probably be dug
out of the www repo).
All the best,
Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set t
://www.bsdcan.org/2025/papers.html to get oriented.
Looking forward to seeing you in Ottawa!
All the best,
Peter (on the BSDCan program committee,
https://www.bsdcan.org/2025/committee.html)
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https
o post at least the generally applicable parts (and if there are
any odditiest it is useful to be aware of) in some form here.
All the best,
Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
&qu
r to the various local filtering features
we have at the client end. I must admit I have a (fortunately short)
list of senders whose messages I will not see unless I take specific
steps to do so.
All the best,
Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementati
o it, my just-abandoned response might have been too forceful for
the purpose.
It is worth keeping in mind, though, for the archives if nothing else, that
some frequent posters here also have a habit of activating auto-ignore
mechanisms
in order to avoid seeing posts by users with high of
ate that-period firefox:
https://marc.info/?l=openbsd-ports&m=139448326727922&w=2
Others here will have better ideas, I'm sure
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Reme
.
Something needs a gentle push, perhaps?
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.1
fficient privileges to bind
to the specified port.
If you have a reasonable doas(1) configuration, prepending doas to the
rcctl command should rid you of the error and have httpd running.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://w
should I set it manually and boot into it pointing loader manually?
It is possible the issue has been fixed already. I ran a sysupgrade -s
on an amd64 machine just 20 min ago with no issues.
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.bl
supgrade -s before running another doas pkg_add -u.
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
it turns up in your dmesg, here em1:
em1 at pci3 dev 0 function 0 "Intel I210" rev 0x03: msi, address
00:25:90:47:88:8c
and the configuration is stored in
$ ls -l /etc/hostname.em1
-rw-r- 1 root wheel 207 Jul 17 2023 /etc/hostname.em1
Hope this helps.
All the best,
Peter
t goes into OpenBSD.
Stories like this one, with only a loose narrative and no data that could have
served to verify a sequence of events, are worse than useless.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://
ith G's
trackers
as the cost for slightly nicer formatting
https://bsdly.blogspot.com/2022/09/a-few-of-my-favorite-things-about.html)
which has a few useful links at the end including to a certain book that *might*
be worth looking into.
All the best,
Peter
--
Peter N. M. Hansteen, membe
ailable for reading and writing from elsewhere?
Anyway, fuser(1) might be a useful tool to check the real status of the
files in question.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"R
On Mon, 21 Oct 2024, notpeter87 notpeter87 wrote:
if anything would happen to Theo de Raadt, he is 56 years old according to
wikipedia, what would happen to OpenBSD?
There's a backup of Theo on an RK05 disk. We're good to go!
--
Monty Brandenberg, Software Engineer
t;if you need to ask the price, you can definitely not afford it" range.
All the best,
Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all m
vely simple approach where the initial active line in each /etc/pf.conf
reads
block # will expand to block all on load
# from here, specifically allow desirable traffic, nothing more, nothing less.
and you insert whatever you feel is strictly needed in pass rules thereafter.
All the best,
Peter
On Wed, Sep 25, 2024 at 02:26:18PM +0200, Peter N. M. Hansteen wrote:
> Another related set of examples and explanations can be found in the blog post
I sense a complete URL would have been beneficial here, as in
https://nxdomain.no/~pe
).
If you go the overload table + block (or tiny queue) route, it will be useful to
set up periodic expiry of the table, as I believe is mentioned in the articles.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https:/
nitely skippable. I forget just when it was
made into a no-op on OpenBSD, but I think it's been like that for
at least a couple of releases.
Other followups from people with slightly less rapid-refresh memory
than myself may even provide the exact commit.
- Peter
--
Peter N. M. Hansteen, me
an also be found *without G's trackers* at
https://nxdomain.no/~peter/yes_you_too_can_be_an_evil_network_verlord.html
(the liberated versions of other blogposts can be found, pre-prettification
at https://nxdomain.no/~peter/blogposts/)
- Peter
--
Peter N. M. Hansteen, member of the
iences!
All the best,
Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconne
quot;
Are we safe to assume that your sshd listens on port 1522?
Once again, it is impossible to offer really useful input unless we have
the entire configuration, at least the complete pf.conf along with any
hostname.vio0 or at least the ifconfig output for the interface.
All the best,
Pete
point in the future, but don't hold your breath :)
All the best,
Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
our browser) is very useful.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnecte
On Thu, Sep 05, 2024 at 01:59:49PM -0400, openbsd_fr...@mail2tor.com wrote:
> Gentlemen! How do I doas my regular user.
Please do not assume all contributors here are male.
doas needs a valid doas.conf. See man doas and man doas.conf.
--
Peter N. M. Hansteen, member of the first RFC 1
eter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
On Tue, Sep 03, 2024 at 10:38:38AM +0300, Ville Valkonen wrote:
> Hello Peter,
>
> how about replacing sudo usage with doas?
If I haven't already, that is an oversight I'll fix shortly. Thanks!
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implem
On Mon, Sep 02, 2024 at 11:47:57PM +0200, Kirill Miazine wrote:
> > Comments and corrections welcome, as always.
>
> add a link afterboot(8), perhaps? https://man.openbsd.org/afterboot
Yes! Added, thanks!
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementatio
;10 years old
pieces I dug out recently.
Comments and corrections welcome, as always.
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious
On Sat, Aug 31, 2024 at 03:01:22PM +0300, Mihai Popescu wrote:
> If your intention is/was to help a new OpenBSD user to install
> packages, then my feedback is a simple no. This article is far from
> helping a beginner to easily install packages.
After offering https://marc.info/?l=openb
/youve_installed_it_now_what_packages.html
or prettified and G-tracked as
https://bsdly.blogspot.com/2013/04/youve-installed-it-now-what-packages.html
Comments and corrections welcome, of course there may be parts where things
could
have happened in the space of 11 years and some months.
All the best,
Peter
--
Peter N. M
t
up such a thing worth it is entirely up to them.
That said, if you have reason to believe that making your email address
available in searchable archives on the Internet, using an alternate
address for posting to the list might be a workable option.
--
Peter N. M. Hansteen, member of the first
the FAQ about packages is worth reading
(https://www.openbsd.org/faq/faq15.html).
Actually *all* parts of the faq are worth reading if you are responsible
for OpenBSD systems.
- P
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ ht
SD relevant issue you might raise will choose to filter away
messages from "Anon Loli" so they will not waste any time reading those pieces
of text.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://w
ts
If I remember correctly, choosing disk and if needed then choosing the
device name for the USB device you booted from is the way forward.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remem
://nxdomain.no/~peter/forcing_the_password_gropers_through_a_smaller_hole.html
(also prettified but tracked at
https://bsdly.blogspot.com/2017/04/forcing-password-gropers-through.html)
could be what you need (some assembly required, obviously).
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdl
er of useful writeups
such as Paul de Weerd's writeup on installing OpenBSD via a serial console
http://www.weirdnet.nl/openbsd/serial/.
For the details such as which flag or option corresponds to which in
each of the systems, it is likely useful to follow the man page links in
the FAQ an
e helpful
If you're new to OpenBSD, you will likely be returning to the FAQ and
the man pages a lot to find info.
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
e thing harder, but definitely legal.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
being extra
careful
about netmasks and routes, but we need more info on the actual configuration to
be sure.
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the e
ctl(s) to enable forwarding?
$ sysctl net.inet.ip.forwarding
and
$ sysctl net.inet6.ip6.forwarding
will provide the answer (as in, if those values are not 1, forwarding
between interfaces is not enabled)
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blog
SD would,
more often.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
happened immediately before the incidents in the log files
such as /var/log/messages (and any other possibly relevant log files).
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember
ve encountered Just Work),
configure that, then run fw_update. Once the firmware is in place, the rest
should be straightforward.
Good luck!
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
&q
most
recent OpenBSD release", with some desktop/laptop oriented tweaks I had found
useful myself. Some of those tweaks may still apply, but some are likely to
be outdated or just plain wrong to start with. But perhaps an updated version
would be useful to somebody?
--
Peter N. M. Hansteen, memb
n is there
significant risk that new users would encounter this in the wild, with a
probability large enough that it would be useful to add a note about this to
say https://www.openbsd.org/faq/faq4.html#bsd.rd somewhere?
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http
t even from some other unixlike like
Linux will do).
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]:
onf
this can not ever be over emphasised or over amplified.
On OpenBSD, you can expect man pages to be complete and informative and
to contain references to other useful resources.
Anyone learning OpenBSD or with OpenBSD should be using 'apropos' and 'man'
quite intensiv
lly related gibberish,
but the thing partially redeems itself by offering up that poem at the end -
https://nxdomain.no/~peter/chatgpt_on_ipv6_and_openbsd_poetry.html (or again
with nicer formatting but G's trackers
https://bsdly.blogspot.com/2023/03/chatgpt-opines-on-ipv6-procastination.html)
is supposed to do, competent people here might offer some advice
on how to make things work properly.
Until that happens, I for one will simply ignore anything from that
source.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ ht
not parse host specification
This sounds to me like those interfaces either do not exist or
have not been correctly configured.
Are those interfaces configured, as in do they have IP addresses?
the output of ifconfig igc1 and ifconfig igc2 will show you.
--
Peter N. M. Hansteen, member of the
treat the two interfaces separately.
The other option - if your network layout is such that it makes
sense to treat them to the same rule criteria - would be to make an
interface group with both interfaces as members, then use the
interface group name in your rules.
--
Peter N. M. Ha
BSD.
(the fuller story is at
https://nxdomain.no/~peter/blog_wild_wild_world_of_windows.html
or with nicer formatting and trackers
https://bsdly.blogspot.com/2021/07/the-impending-doom-of-your-operating.html)
In your case, the relevant option (if it exists) may be labeled
something completely different. But
etwork to port $client_out
- that way you will actually use the macro. But the macro sitll references
the invalid service nportntp (you probably want ntp instead), and I would
think that the services "446, cvspserver, 2628, 5999, 8000, 8080" are unlikely
to be useful unless you *know* you
home.nuug.no/~peter/pf/en/basicgw.html#GWPITFALLS
(That is in the piece that evolved into The Book of PF, and likely
something similar appears somewhere in the book too)
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https:
.$icmp_types" and
> "...$client_out"). I am assuming "log log" on the last rule is a typo,
> and it is actually "log out".
Those are as far as I can tell correct observations. There appears to be
no rule allowing traffic other than the selected icm
e, but with a
bare environment with only essentials like $HOME defined and no
~/.terminfo directory (as opposed to an empty one), do the odd messages
still appear?
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https:/
se to take a few steps back, start from the basics and add only the
things you know you need.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network
On Wed, Apr 10, 2024 at 11:01:18PM +0200, Peter N. M. Hansteen wrote:
> Another gentle introduction can be found in the latest PF tutorial,
> the slides for the AsiaBSDCon 2024 version can be found as
> https://nxdomain.no/~peter/pf_asiabsdcon2024.pdf which in turn has
> reference
tions.
All the best,
Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Please actually read the advice offered by contributors to this thread.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
deli
x error
for conversion to tables, keep in mind that references need the
surrounding '<' and '>'.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set
he ranges in $martians (which I anyway would recommend converting
into a table), and your block referencing $martians comes after the pass rules
that would have let icmp through. With no previous matching quick, last match
applies.
- Peter
--
Peter N. M. Hansteen, member of the first RFC
by default. Fortunately
it was possible to choose the other options and have the device turn up
as a regular NMVe device:
https://nxdomain.no/~peter/blog_wild_wild_world_of_windows.html (or with
incrementally nicer formatting at the cost of G's trackers,
https://bsdly.blogspot.com/2021/07/the
at least some
information.
- P
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
h like a situation where the base system and packages
are out seriously of sync AND your user is et up with a default shell from
packages (I am guessing bash).
The solution would likely be to log in as root, run pkg_add -D snap -u
to get the latest snapshot packages, then try to log in as yo
@mastodon.social
>From a tweet of mine from 2011, but evergreen:
I DEMAND TO KNOW WHY YOUR GROUP OF OVERWORKED VOLUNTEERS, WHICH
I AM NOT A MEMBER OF, IS NOT PURSUING MY PERSONAL GRIEVANCE.
Mar 28, 2024, 12:22 PM
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
ht
I am on the list, the Cc:s are not necessary and in fact
a bit annoying)
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
On Sat, Mar 30, 2024 at 05:44:32PM +0500, ofthecentury wrote:
> On Sat, Mar 30, 2024 at 5:29 PM Peter N. M. Hansteen wrote:
> >
> > why?
>
> I got "disassoc"s events in the log.
disassociations can happen for a number of different reasons. The event
should log a
ect to all sorts of radio interference that's
essentially background noise
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
rvice, systemd."
Enjoy!
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
your From: without putting in some extra effort.
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[2994
, will do the integrity checking.
If you *want* to have a script that wraps both actions into one, that's fine.
But I would have wanted to make life easier by sticking to the tools that
are available in a default install.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation t
I was just notified that two different obvious pr0n
spam sources followed my account.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network tr
On Fri, Mar 15, 2024 at 06:38:14PM +0100, Peter N. M. Hansteen wrote:
> least the content of your configuration files -- /etc/hostmhame.* and the
> output
that should of course have been /etc/hostname.* but would be obvious?
--
Peter N. M. Hansteen, member of the first RFC 1149 implemen
we need to see at
least the content of your configuration files -- /etc/hostmhame.* and the output
of ifconfig for the relevant interfaces (if need be with stuff like IP
addresses
and passwords masked).
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blo
net6' settings in there.
- Peter
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
r_plugin_set_property]: could not
> set sound-card to '%s', trying the default card instead"
> wrapper-2.0: vfprintf %s NULL in "%s: muted"
>
> Nothing else to show up in /var/log/messages. Is there
> a more detailed log?
>
> How do I gather
anyone trying to help diagnose
the issue
a lot more.
As somebody (sorry, I forget who) posted earlier, https://idownvotedbecau.se/
is actually
worth reading.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://ww
be my next step.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
iling, more likely than not you would be seeing messages
in system log files or possibly even in dmesg output. Totally silent failures
are not very common.
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no
easy to spot for a separate set
of eyes.
- P
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
1 - 100 of 1036 matches
Mail list logo
