search for: linux_sll

A STATEFUL firewall with ?ip any any? can and will still block asymmetric communications due to the firewall keeping track of state (hence tha name stateful firewall). Tcpdump on your servers /other/ NICs and you?ll see the tftp traffic leaving your server on some other NIC (probably on with the default route). The upstream firewall will then block the tftp response if it never saw the tftp

...k there are many environments that restrict users but give access to tcpdump via sudo. With this option tcpdump can execute any command: $ ./tcpdump -V tcpdump version 4.1.1 $ sudo ./tcpdump -i any -G 1 -z ./test.sh -w dump port 55555 [sudo] password for user: tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes (generate some traffic on port 55555) root@blaa ~/temp/tcpdump-4.1.1$ id uid=0(root) gid=0(root) groups=0(root) $ cat test.sh: #!/bin/bash /bin/bash Is this known and accepted? Could this option maybe be implemented differently? Regards, tazo === 8< ==...

...an see no pkt is leaving. If it were leaving S, but A were not > receiving then I would think firewall > is dropping it. > > [ S ~]$ sudo tcpdump -A -nniany host 192.168.1.10 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 > bytes > > 16:40:08.390939 IP 192.168.1.10.35553 > 192.168.1.20.69: 16 RRQ "file" > netascii > E..,J1 at .>..n./...oAt...E..#...file.netascii................... > 16:40:13.391133 IP 192.168.1.10.35553 > 192.168.1.20.69: 16...

...vices there is no packet seen: [...] rt1:~# tcpdump -n -i imq0 Warning: arptype 65535 not supported by libpcap - falling back to cooked socket tcpdump: WARNING: imq0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on imq0, link-type LINUX_SLL (Linux cooked), capture size 68 bytes [...] and there is no packet seen. I have sent the packet to imq0 by: rt1:~# iptables -I PREROUTING -t mangle -j IMQ --todev 0 and there is no other entry in mangle table. There is also no firewall entry and no entry in nat table. The ifconfig command show, t...

....br helvio.junior at safetrend.com.br Em 05/06/2017 17:22, thelma at sys-concept.com escreveu: > Yes, it is working! > > tcpdump -ni any port 4569 > dropped privs to tcpdump > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes > 14:20:42.184521 IP 10.0.0.108.4569 > 10.0.0.100.4569: UDP, length 53 > 14:20:42.184921 IP 10.0.0.100.4569 > 10.0.0.108.4569: UDP, length 37 > 14:20:42.190529 IP 10.0.0.108.4569 > 10.0.0.100.4569: UDP, length 83 > 14:20:42.190639 IP 10...

...t at backup-1:~# ping 172.16.1.5 PING 172.16.1.5 (172.16.1.5) 56(84) bytes of data. >From 172.16.1.5 icmp_seq=1 Destination Net Unknown root at backup-1:/etc/tinc/tiutl# tcpdump -i any icmp -n tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 20:26:22.990261 IP 172.16.0.11 > 172.16.1.5: ICMP echo request, id 3012, seq 5, length 64 20:26:22.990322 IP 172.16.1.5 > 172.16.0.11: ICMP net 172.16.1.5 unreachable - unknown, length 92 root at gateway-1:/etc/tinc/tiutl# tcpdump -i any icmp -n (not...

Am 15.06.2020 um 21:50 schrieb Luca Bertoncello: > What do you mean now? If I can use the full available band or if I can > download exactly 50Mbs? > The answer to the first question is: YES! That's why I use a traffic > shaper... ;) > The answer to the second question is: NO. I made a speedtest right now > and I get only ~18Mbps download. And some other information, too.

...t at backup-1:~# ping 172.16.1.5 PING 172.16.1.5 (172.16.1.5) 56(84) bytes of data. >From 172.16.1.5 icmp_seq=1 Destination Net Unknown root at backup-1:/etc/tinc/tiutl# tcpdump -i any icmp -n tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 20:26:22.990261 IP 172.16.0.11 > 172.16.1.5: ICMP echo request, id 3012, seq 5, length 64 20:26:22.990322 IP 172.16.1.5 > 172.16.0.11: ICMP net 172.16.1.5 unreachable - unknown, length 92 root at gateway-1:/etc/tinc/tiutl# tcpdump -i any icmp -n (not...

...root at backup-1:~# ping 172.16.1.5 PING 172.16.1.5 (172.16.1.5) 56(84) bytes of data. From 172.16.1.5 icmp_seq=1 Destination Net Unknown root at backup-1:/etc/tinc/tiutl# tcpdump -i any icmp -n tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 20:26:22.990261 IP 172.16.0.11 > 172.16.1.5: ICMP echo request, id 3012, seq 5, length 64 20:26:22.990322 IP 172.16.1.5 > 172.16.0.11: ICMP net 172.16.1.5 unreachable - unknown, length 92 root at gateway-1:/etc/tinc/tiutl# tcpdump -i any icmp -n (not...

You can use tcpdump in your server to verify if it is receiving the packets. tcpdump -ni any port 4569 So you have more than one ip in the server? On 5 Jun 2017 9:13 pm, <thelma at sys-concept.com> wrote: > No, I don't think it is IP table issue, I've not upgraded dd-wrt for a > while and it was zoiper was working OK with my previous version of > asterisk. > >

...nd of analysis from a span port on a switch... But that doesn't explain the missing packets from DT. Similar results on that side: jeff at jasper:~/Personal/StratusTalk/wotinder/Luca/tmp$ tcpdump -nr testDSL.pcap src 91.49.58.181 | wc -l reading from file testDSL.pcap, link-type LINUX_SLL (Linux cooked) 8048 jeff at jasper:~/Personal/StratusTalk/wotinder/Luca/tmp$ tcpdump -nr testDSL.pcap dst 91.49.58.181 | wc -l reading from file testDSL.pcap, link-type LINUX_SLL (Linux cooked) 4076 I'm making an assumption that 91.49.58.181 is your side of the DSL, and t...

...-A OUTPUT -p tcp -m string --algo bm --string GET -j DROP [root at tst-sniffer tmp]# tcpdump -i any -X tcp port 80 tcpdump: WARNING: Promiscuous mode not supported on the "any" device tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes 18:50:02.413280 IP tst-sniffer.qualcomm.com.49297 > ir1.fp.vip.sk1.yahoo.com.http: S 651414485:651414485(0) win 5840 <mss 1460,sackOK,timestamp 10144916 0,nop,wscale 7> 0x0000: 4500 003c 0741 4000 4006 d8c5 0a38 0635 E..<.A at .@....8.5...

....16.1.5 > PING 172.16.1.5 (172.16.1.5) 56(84) bytes of data. > From 172.16.1.5 icmp_seq=1 Destination Net Unknown > > root at backup-1:/etc/tinc/tiutl# tcpdump -i any icmp -n > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on any, link-type LINUX_SLL (Linux cooked), capture size > 262144 bytes > 20:26:22.990261 IP 172.16.0.11 > 172.16.1.5: ICMP echo request, id 3012, > seq 5, length 64 > 20:26:22.990322 IP 172.16.1.5 > 172.16.0.11: ICMP net 172.16.1.5 > unreachable - unknown, length 92 > > root at gateway-1:/etc/tinc/...

...Transfer timed out. As you can see no pkt is leaving. If it were leaving S, but A were not receiving then I would think firewall is dropping it. [ S ~]$ sudo tcpdump -A -nniany host 192.168.1.10 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 16:40:08.390939 IP 192.168.1.10.35553 > 192.168.1.20.69: 16 RRQ "file" netascii E..,J1 at .>..n./...oAt...E..#...file.netascii................... 16:40:13.391133 IP 192.168.1.10.35553 > 192.168.1.20.69: 16 RRQ "file" netascii...

...n see no pkt is leaving. If it were leaving S, but A were not > receiving then I would think firewall > is dropping it. > > [ S ~]$ sudo tcpdump -A -nniany host 192.168.1.10 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 > bytes Most likely the firewall on the system running your tftp client is blocking the traffic from the tftp server. The easiest way to test would be to put in a rule that allows all packets from the server (or to at least log them so you can see what's...

...t were leaving S, but A were not > > receiving then I would think firewall > > is dropping it. > > > > [ S ~]$ sudo tcpdump -A -nniany host 192.168.1.10 > > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > > listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 > > bytes > > > > 16:40:08.390939 IP 192.168.1.10.35553 > 192.168.1.20.69: 16 RRQ "file" > > netascii > > E..,J1 at .>..n./...oAt...E..#...file.netascii................... > > 16:40:13.391133 IP 192.168.1.10.35...

...s for 192.168.1.2: Packets: Sent = 2, Received = 0, Lost = 2 (100% loss), rx1000test:~# tcpdump -i GDC1 tcpdump: WARNING: arptype 778 not supported by libpcap - falling back to cooked socket tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on GDC1, link-type LINUX_SLL (Linux cooked), capture size 96 bytes 13:40:01.296907 IP 192.168.1.2 > 192.168.1.101: icmp 40: echo reply seq 7424 13:40:06.587157 IP 192.168.1.2 > 192.168.1.101: icmp 40: echo reply seq 7680 rx1000test:~# tcpdump -i eth1 not tcp port 22 tcpdump: verbose output suppressed, use -v or -vv for...

...UT=tunnel0 PHYSIN=eth1 SRC=10.10.30.251 DST=10.35.8.46 LEN=84 TOS=0x00 PREC=0x00 TTL=62 ID=26665 PROTO=ICMP TYPE=0 CODE=0 ID=61218 SEQ=1 traffic in is seen on tunnel0 whereas traffic out is seen on br0. tcpdump, though, gives me the correct information : tunnel0: listening on tunnel0, link-type LINUX_SLL (Linux cooked), capture size 96 bytes 14:20:30.077337 IP 10.10.30.251 > 10.35.8.46: icmp 64: echo request seq 0 14:20:30.092054 IP 10.35.8.46 > 10.10.30.251: icmp 64: echo reply seq 0 14:20:31.081619 IP 10.10.30.251 > 10.35.8.46: icmp 64: echo request seq 1 14:20:31.102690 IP 10.35.8.46 &g...

Hello, I have been playing with the XCP for a while now, and must say I''m very exited about the technology. I had no prior experience with Xen so it has taken me a while to understand the concepts, but now I feel most important issues are solved and I''ve purchased some hardware to build my (tiny) cloud on. The box is a Supermicro 1026TT-IBXF, so I have 2 x Ethernet and 1 x