Boniforti Flavio wrote:
>> I thought you wanted to measure the compressed ssh packets 
>> that transport the tunnel, not the uncompressed data as it is 
>> seen locally going in and out of the tunnel..
>>     
>
> Yes, I'd like to measure what is being transferred from my WAN-side to
> the other WAN-side (therefore you're right when talking about
> *compressed* data).
> If you're saying that to measure that sort of data, I'd better watch
> what's travelling on TCP port 22, why didn't I see anything being
> transferred to/from that port?
> I used these rules:
>
> iptables -I INPUT -s remotehost -d localhost -p tcp --sport 22
> iptables -I OUTPUT -s localhost -d remotehost -p tcp --dport 22
>
> I thought these could be right, because of this netstat output:
>
> storebox:~# netstat -na | grep remotehost
> tcp        0      0 172.16.16.222:50097     remotehost:22
>   
You have 'localhost' in your rules, which means 127.0.0.1, but the 
connection is really with your ethernet IP address.  I'd just omit the 
local side of those rules and track everything going to the remote IP 
address.

-- 
  Les Mikesell
   lesmikesell AT gmail DOT com


------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com 
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/