Hi JF,
On Thu, 12 Nov 2009, JF Cliche wrote:
> I am behind two NAT routers (Linksys running DD-WRT) with port
> forwarding up to the machine running pmacct, and yet pmacct reports SSH
> traffic to the forwarded port with the public (external, non-NATed)
> addresses. I thought all traffic shoul
Hi JF,
As Karl said, libpcap looks what's on the wire and pmacct doesn't
get further up in the packet layering. You can always do a quick
check by verifying what tcpdump sees.
While on NAT & Linux, and perhaps not related to this specific
issue: the "uacctd" daemon has been introduced in pmacct
On 11/11/2009 11:24:34 PM, JF Cliche wrote:
> Maybe a newbie question, so I'll be brief:
>
> I am behind two NAT routers (Linksys running DD-WRT) with port
> forwarding up to the machine running pmacct, and yet pmacct reports
> SSH traffic to the forwarded port with the public (external,
> non-NAT
Maybe a newbie question, so I'll be brief:
I am behind two NAT routers (Linksys running DD-WRT) with port
forwarding up to the machine running pmacct, and yet pmacct reports
SSH traffic to the forwarded port with the public (external,
non-NATed) addresses. I thought all traffic should be seen as c