search for: pkts

...0) first packet: Sat Apr 14 15:05:57.502839 2007 last packet: Sat Apr 14 15:07:53.234397 2007 elapsed time: 0:01:55.731558 total packets: 425593 filename: snd_buf_off.log e->f: f->e: total packets: 175858 total packets: 249735 ack pkts sent: 175858 ack pkts sent: 249735 pure acks sent: 164954 pure acks sent: 8 sack pkts sent: 0 sack pkts sent: 0 dsack pkts sent: 0 dsack pkts sent: 0 max sack blk...

...Chris Rapier *I didn't disable TSO before taking these dumps so these pakets size don't necessarily correspond to the actual MTU. Ostermann's tcptrace -- version 6.6.7 -- Thu Nov 4, 2004 155626 packets seen, 155626 TCP packets traced elapsed wallclock time: 0:00:00.722889, 215283 pkts/sec analyzed trace file elapsed time: 0:00:19.943138 TCP connection info: 1 TCP connection traced: TCP connection 1: host a: delta host b: echo complete conn: yes first packet: Tue Apr 17 16:27:22.204583 2007 last packet: Tue Apr 17 16:2...

...captured file using the command: "tcptrace -l ": ========================================================================= =========================================================================   886 packets seen, 886 TCP packets traced   elapsed wallclock time: 0:00:00.024537, 36108 pkts/sec analyzed   trace file elapsed time: 0:00:23.034820   TCP connection info:   3 TCP connections traced:   TCP connection 1:  host a:        192.168.105.237:36069  host b:        192.168.105.211:20000  complete conn: no (SYNs: 1)  (FINs: 1)  first packet:  Sun Oct 16 16:21:21.332143 2005  last pac...

...using the shorewall status. Was hoping to know what logfile it is writing it to. Thanks in advance, Elmer -=-=-=-=-=-=-=-=-=- Shorewall-2.0.7 Status at hilo.webmerch.com - Wed Aug 4 18:10:30 PDT 2004 Counters reset Wed Aug 4 18:03:52 PDT 2004 Chain INPUT (policy DROP 4 packets, 1208 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 0 0 DROP !icmp -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 65 8740 eth0_in all -- eth0 * 0.0.0.0/0 0.0.0...

...sonal #-A OUTPUT -p tcp -m tcp --dport 80 -j MARK --set-mark 20 -A OUTPUT -p tcp -m tcp --dport 80 -j others -A personal -j MARK --set-mark 40 -A others -j MARK --set-mark 20 Here''s my iptables -L -v -t mangle -x output Chain PREROUTING (policy ACCEPT 580535 packets, 176796832 bytes) pkts bytes target prot opt in out source destination Chain INPUT (policy ACCEPT 573475 packets, 174919251 bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 5656 packets, 1810367 bytes) pkts...

...st, id 1584, seq 4, length 64 15:28:46.738332 IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id 1584, seq 5, length 64 15:28:47.756378 IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id 1584, seq 6, length 64 'iptables -L -vn' yields: Chain INPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 799 156K ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED 0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 22 1592 INPUT_direct all -- * * 0.0.0.0/0 0.0.0...

...outing table based on that mark. Am I headed down the right track? Or way off? Thanks Paul. Here is the output of shorewall status: Shorewall-2.0.4 Status at rama-kandra - Wed Sep 22 12:54:47 NZST 2004 Counters reset Wed Sep 22 12:49:21 NZST 2004 Chain INPUT (policy DROP 1 packets, 234 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 350 40966 accounting all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 DROP !icmp -- * * 0.0.0.0/0 0.0.0.0/0...

...scope link 127.0.0.0/8 dev lo scope link default via 213.58.230.49 dev eth1 [root@bassinka log]# [root@bassinka log]#shorewall status Shorewall-2.0.1 Chain at bassinka - Fri Feb 25 10:33:16 WET 2005 Counters reset Thu Feb 24 17:57:46 WET 2005 Chain INPUT (policy DROP 9 packets, 1024 bytes) pkts bytes target prot opt in out source destination 592 34399 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 0 0 DROP !icmp -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 299K 333M eth1_in all -- eth1 * 0.0.0.0/0 0.0.0...

...scope link 127.0.0.0/8 dev lo scope link default via 213.58.230.49 dev eth1 [root@bassinka log]# [root@bassinka log]#shorewall status Shorewall-2.0.1 Chain at bassinka - Fri Feb 25 10:33:16 WET 2005 Counters reset Thu Feb 24 17:57:46 WET 2005 Chain INPUT (policy DROP 9 packets, 1024 bytes) pkts bytes target prot opt in out source destination 592 34399 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 0 0 DROP !icmp -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 299K 333M eth1_in all -- eth1 * 0.0.0.0/0 0.0.0...

Hello Julien, Am Tue, 15 Jan 2019 09:30:23 +0100 schrieb Julien dupont <marcelvierzon at gmail.com>: > In that case I see: > IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id2135, seq1, length 64 > IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id2135, seq2, length 64 > IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id2135, seq3, length 64 > > Packet goes

...htb rate 100kbit tc qdisc add dev imq0 parent 10:10 handle 20: sfq iptables -t mangle -A POSTROUTING -p tcp --dport 80 -j IMQ ip link set imq0 up when i see the Iptables Out Put [root@bridge root]# iptables -xnvL -t mangle Chain PREROUTING (policy ACCEPT 122928 packets, 16888665 bytes) pkts bytes target prot opt in out source destination Chain INPUT (policy ACCEPT 15068 packets, 1185569 bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 116790 packets, 16553990 bytes) pkts bytes target prot opt...

...pr.org - Tue Feb 25 21:37:39 AST 2003 Counters reset Tue Feb 25 21:31:04 AST 2003 -------------- next part -------------- [H[JShorewall-1.3.14 Status at linux.ve1drg.ampr.org - Tue Feb 25 21:39:23 AST 2003 Counters reset Tue Feb 25 21:31:04 AST 2003 Chain INPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 79 12869 eth0_in all -- eth0 * 0.0.0.0/0 0.0.0.0/0 5 1015 eth1_in all -- eth1 *...

Dear List! I use a shorewall 2.0.8 on a Debian sarge system. I use a DSL connection to the Internet (ppp0 - eth1 to the modem) and a bridge to the local lan. The bridged config i''ve made with bridge.html from the shorewall site. The Bridge is between local net and a openvpn tap device. This works. I ccan make tunnels, and a can make a lot of things through the firewall. I can get a list

....145 dev eth0 [root@shields-svr00 shorewall]# Matthew Hodgett -------------- next part -------------- [H[2JShorewall-2.0.10 Status at shields-svr00.shields.shieldssecurity.com - Mon Nov 29 18:47:40 WIT 2004 Counters reset Mon Nov 29 18:19:40 WIT 2004 Chain INPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 0 0 DROP !icmp -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 63 8700 eth0_in all...

...tunl0 0.0.0.0 24.224.173.1 0.0.0.0 UG 0 0 0 eth0 -------------- next part -------------- [H[JShorewall-1.3.14 Status at linux.ve1drg.ampr.org - Thu Feb 27 19:10:53 AST 2003 Counters reset Wed Feb 26 20:50:34 AST 2003 Chain INPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 310 15500 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 16820 7400K eth0_in all -- eth0 * 0.0.0.0/0 0.0.0.0/0 332 45305 eth1_in all -- eth1 *...

...he output chain and then try to match that mark either in NAT OUTPUT or POSTROUTING I don''t seem to get the expected result. Any help or clue would be more than welcome. root@droopy:~/firewall > iptables-view -t mangle Chain PREROUTING (policy ACCEPT 33890 packets, 16M bytes) num pkts bytes target prot opt in out source destination Chain INPUT (policy ACCEPT 24751 packets, 12M bytes) num pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 9146 packets, 4557K bytes) num pkts bytes target prot opt in out sourc...

Hi, I wanted to implement some QOS on my Linux Box with HTB, but after some time spend on the configuration and tests, I still don''t manage to have some correct results. Here are the details : -ROOT 2000 kbits -HIGHPRIO SUBCLASS 50 kbits prio 0 -SUBCLASS1 750 kbits prio 1 -SERVICE1 250 kbits prio 1

Hello All, I am trying to setup a linux box as a forwarding router based of src IP. The problem is that it does forward the pkts to the intended server specified in the ip rule, but it also forwards it to the original dst (dst specified in the pkt). Here is the setup: [10.1.0.166] [192.168.1.225] | | |...

...like before... I got something like: # tc -s -d class show dev eth0 class htb 1: parent 1: class htb 1: parent 1: class htb 1: parent 1: class htb 1: parent 1: class htb 1: parent 1: class htb 1: parent 1: class htb 1: parent 1: # tc -s qdisc qdisc ingress ffff: dev eth0 Sent 0 bytes 0 pkts (dropped 0, overlimits 0) qdisc sfq 99: dev eth0 quantum 1514b perturb 10sec Sent 209435 bytes 1201 pkts (dropped 0, overlimits 0) qdisc sfq 32: dev eth0 quantum 1514b perturb 10sec Sent 8533 bytes 79 pkts (dropped 0, overlimits 0) qdisc sfq 31: dev eth0 quantum 1514b perturb 10sec Sent 66...

I have searched your FAQ''s and read the documentation on your site as well as googling. I am not able to figure this out. If you have any ideas can you please help. I am using the linux-ha failover with redundant firewalls. As part of the function of the linux-ha software consists a service called heartbeat which is a connection from each failover node through a serial cable or ethernet.