Yes you misunderstand... on the ppp0 interface is the traffic from the internetwork to your site and vice versa. That traffic is addressed to you at the 64. or 24. or whatever address.
Internal network traffic has the 192.168.1.x/24 address. Your gateway/router handles some of that doing the NAT. But traffic between nodes on that address just flows PAST the ntop host, not through it. If you want to monitor that traffic, then you need -i eth0, not -i ppp0 This really isn't ntop related, it's basic TCP/IP networking - I suggest you research that for a better understanding... -----Burton -----Original Message----- From: Hendrik Friedel [mailto:[EMAIL PROTECTED]] Sent: Sunday, August 18, 2002 2:03 PM To: 'Burton M. Strauss III' Subject: Re: [Ntop] Filtering > So, as an (educated) guess... > > 23:33:50.296691 192.168.1.11.vrcommerce > > c-24-130-148-94.we.client2.attbi.com.kazaa: . ack 1721674975 win 62788 > (DF) > > Your internal network (lan) is 192.168.0.x/24 Not exactly. Ist 192.168.1.x/24. > Your external interface is one of the two, either the 63. or > 217. interface It's a dynamic IP. So that doesn't help. > (it would really be smarter to turn off high volume > noise/stuff like Kazza during these tests) Not really possible (many users) > So if you want to monitor only the ppp0 link, that's the > filter expression, not the 192. one... Whant's 'that' ? ppp0? I already start ntop with -i ppp0. So only the traffic of ppp0 is displayed. Did I misunderstand you? What I want is that in DataRecieved and DateSent (for instance) only the local Clients (192.168.1.x are displayed. I don't care about what Server they connect do. I only care about the current troughput, the amount of data Sent and recieved (etc) of the PC's in my lan. That way I can tell the right users to stop causing so much traffic. Hendrik _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://lists.ntop.org/mailman/listinfo/ntop
