hm why doesn't this work: sudo tcpdump -n -e -ttt -i pflog0 | logger -p local0.notice

tried sudo /bin/sh -c "tcpdump -n -e -ttt -i pflog0 | logger -p local0.notice" yoo

too*

sudo /bin/sh -c "repeat 1000 'tcpdump -n -e -ttt -i pflog0 | logger -p local0.notice'" is right

or not

maybe, at last

or

[ins er t co i ns]

what?

гep пук

ya i just don't know what any of that means

polyex: you have to add log to every line of block or pass in pf.conf and it'll appear in syslog, at least on OpenBSD. Probably the same in FreeBSD

pass in log, block in log, etc

add what vortexx?

the log keyword

i have added "log" to all of my rules i want to know about, and i can see them

the issue is getting them into syslog

is check that daemon.log or messages.log aren't getting filled with pf messages

is check?

/var/log/daemon.log & /var/log/messages

s/is check/check

also you have to set log interface in pf.conf, such as set loginterface dc0

why are you talking about filling up files? that's beside the point. why doesn't sudo tcpdump -n -e -ttt -i pflog0 | logger -p local0.notice or sudo /bin/sh -c "tcpdump -n -e -ttt -i pflog0 | logger -p local0.notice" work?

without that it won't work

think, if you're activating logging to syslog on an interface with high traffic, every single packet passage will be logged to syslog and whereever that ends up it will balloon the logfile

the most knowledgeable people about pf are in #openbsd, I suggest you ask there

which has a different pf

i think you guys are missing the point. i run tcpdump -n -e -ttt -i pflog0 and it works fine, i see a few lines an hour. why can't i just pipe that into logger so that those few lines an hour end up in syslog?

it's like you're not even listening and you just want to type dozens of lines for fun

i wasn't here for the original question, but add -l to tcpdump

or /msg greybot !faq buffering

WORKING

TYVM!!

and to make "sudo tcpdump -n -l -e -ttt -i pflog0 | logger -p local0.notice" always running, i just pass it to daemon and make a rc.d script out of it?

'tput AB F AF 0 cd' no longer worked for me on FreeBSD UNIX 14

whoo all my IPv6-only kernel changes got MFC's into stable/14 and releng/14.1 and will be in 14.1-RELEASE, so you can now build a kernel with no IPv4 support at all by removing 'options INET'

lw omfg tyvm. ipv6-only is the future

lw any way you could add per-vimage mac_portacl support to jails?

probably not rn as i'm very busy, i suggest mailing net@ or filing a PR. or do it yourself!

(also i don't know anything about vnet...)

trying to make my tcpdump to logger command a rc.d script ran by daemon, but it makes error? termbin.com/vh2g

dunno why my sudoers line isn't solving that error

polyex: why don't you just set pflog_enable=YES?

lw what do you mean? pflog is enabled

but that doesn't put my tcpdump lines onto syslog which is what i wanna do

aren't you just duplicating pflog functionality then? the log is already available in /var/log/pflog

ah

it's built on pflog0 actually

then you have to run your script as root, or configure devd to make /dev/bpf accessible to another group

ohh it's not just a sudo thing?

i don't know what you mean by "sudo thing" but your rc.d script is not invoking sudo, if that's what you intended?

it would be more secure to run it as non-root anyway though, since tcpdump does have a history of security issues

oh lol yea duh i'm not calling sudo. hmm

what's the right way to run this thing as its own user but also get permission to run the cmd? add logg user to devd group for /dev/bpf?

yes, you need to get devd to create /dev/bpf with group read permission. i don't know how to do that off hand though

(i'm sure it's not complicated as this is the sort of thing that devd is intended to support)

polyex: cgit.freebsd.org/ports/tree/net/wireshark/pkg-message i'm sure this will work with tcpdump too

Title: pkg-message « wireshark « net - ports - FreeBSD ports tree

then you just need to make sure your rc.d script runs as a user in the 'network' group

ooo interesting tyvm!!

apparently tcpdump on freebsd is capsicumised though so the risk of running it as root is less than you might expect

but still, don't run things as root if not required

yep

Title: wifi - Boot iPXE on macbook pro using BSDP - Ask Different

Would love if someone could prove me wrong!

Phrased as a question: Are there tools in FreeBSD to run binary-only blobs for the wifi-crap in macbooks?

|cos|: Could NDISulator do that?

Hm, maybe that was ripped out in 14.x?

|cos|: maybe look at wifibox

vkarlsen, lw: thanks! it sure seems wifibox would do the trick. i'll commmense my freebsd install and update the SE answer.

yeah, wifibox is basically the new version of the NDISulator

since Linux supports all common wifi cards nowadays

it sucks you need to run Linux to make common wifi devices work but it's better than nothing

even when wifi does work it doesn't work well. I have an old atheros chipset but it's limited to 802.11n 54g despite both ends being capable of ac MIMO and it spams my dmesg with weird errors

ath0: bad series0 hwrate 0x1b, tries 3 ts_status 0x0

ath0: ath_rate_tx_complete: ts_rate=27 ts_finaltsi=0, final_rix=0

wifi randomly stops working every a day or two and needs manual intervention

Hey good afternoon #freebsd ... I'm trying to build some ports for a FreeBSD 11.4 , and am hitting constantly this paste.centos.org/view/21f5be26

Title: Untitled - Pastebin Service

to the untrained eye, it seems the issue is the "make: "/usr/ports/ports-mgmt/pkg/work/pkg-1.21.2/mk/common.mk" line 16: Need an operator"

any ideas please?

FWIW that's showing as 16 -include $(DEPFILES_NONEMPTY:=)

The last time I had a look at the code for 802.11 drivers, it gave me a headache.

The cost of entry for these technologies is enormous, even for embedded systems engineers.

I think that to really make progress on this subject, someone would have to work on it full-time for at least a year.

is there an alternative wireless protocol?

if 802.11 is so hard to implement

no, currently routeros, but the ac devices require "qcom-wifi-ac" package

wc

anyone knows how is 802.11ac/ax development going?

Something like 3 commits in 5 years iirc

=O

asking for a friend, is anybody using digital ocean floating ips, *and* carp?

and for an alternative, looking for a tcp or udp based "clustering" protocol

if node A is down, then node B should run a shell script

and vice versa

Hi, I need to install packages on a FreeBSD 12 jail. I cannot upgrade to 13 nor 14, is there an old repository I can point to?>

I found this: mirror.sg.gs/freebsd-pkg/FreeBSD:12:amd64

Title: FreeBSD:12:amd64

hi, I'm trying to take a failing drive offline with MegaCLI64 on my raid array, using this guide: advancedclustering.com/act_kb/replacing-a-disk-with-megacli

Title: Replacing an LSI raid disk with MegaCli - Advanced Clustering Technologies

oh I forgot I need to use bash instead of csh for this, sorry for the noise

anyone on stable/14 with latest changes? i have no sound after some work on sound drivers

there was certain changes to sound driver

Title: src - FreeBSD source tree

however, i had no last 24 hour changes, only ones that 5 days old

re

andjjj23: I am on a pretty fresh FreeBSD 15-CURRENT and sound works, with both Realtek ALC262 and USB sound cards

er sorry andjjj23 :)

to give specific users access to bpf is the best way how cgit.freebsd.org/ports/tree/net/wireshark/pkg-message does it? can it be in devfs.rules instead of devfs.conf?

Title: pkg-message « wireshark « net - ports - FreeBSD ports tree

is bpf available at boot? that's 1 of the differences manpages say

why can't i chgrp on /dev/bpf0?

i type it and there's no error but ls -la still shows root:wheel