From: Sebastien v. <se...@ji...> - 2012-04-05 18:33:12
|
Hi WG, Basically all wireless users have public IPv6 address. Internally all IPv6 traffic from wireless interface go to the program (via tun/tap interface) and the filtering (if user has registered on the web portal or not) is done at this level. For information the same goes for IPv4. For wireless to uplink, it is just basic IPv6 routing (wireless and ethernet interface has different IPv6 prefixes). Best regards, -- Seb Le 05/04/12 19:43, WG a écrit : > Hi, > > Can someone explain how Pepperspot manages to capture user traffic on IPv6 > ? I understand that on IPv4 it can use the Linux NAT module through > iptables, but ip6tables doesn't support NAT, so I don't understand how > traffic aimed at a public IPv6 address is captured on the machine and > redirected to Pepperspot (localhost) itself. > > Kind regards, > > Wim > > > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > _______________________________________________ > Pepperspot-users mailing list > Pep...@li... > https://lists.sourceforge.net/lists/listinfo/pepperspot-users > |