-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 23 Oct 2021, Uwe Sauter wrote:
From my experience, tcpdump connects to the interface and you will see
all traffic regardless of firewall settings, given you have the
permissions.
In your case I'd first verify that layer 2 is working
From my experience, tcpdump connects to the interface and you will see
all traffic regardless of firewall settings, given you have the
permissions.
In your case I'd first verify that layer 2 is working correctly (layer
2 is ethernet or wifi). So I'd use the utilities provided by
"wpa_suppl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 23 Oct 2021, Uwe Sauter via arch-general wrote:
Does the following quote, copied from
https://wiki.archlinux.org/title/Network_Debugging#Tcpdump, relevant?
they can only see outbound packets the firewall passes through:
[https://su
Does the following quote, copied from
https://wiki.archlinux.org/title/Network_Debugging#Tcpdump, relevant?
they can only see outbound packets the firewall passes through:
[https://superuser.com/questions/925286/does-tcpdump-bypass-iptables]
Perhaps you should disable the firewall, or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 22 Oct 2021, u34--- via arch-general wrote:
Erich Eckner via arch-general wrote:
Hi fellow-archers,
I'm running a software accesspoint with hostapd for several years now.
Since some weeks, clients cannot talk to each other directly any
Erich Eckner via arch-general wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi fellow-archers,
>
> I'm running a software accesspoint with hostapd for several years now.
> Since some weeks, clients cannot talk to each other directly anymore, also
> IPv6 broke (the latter migh
