Skip to content

Instantly share code, notes, and snippets.

@ironpillow
Created March 30, 2019 01:46
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ironpillow/97cb3dd6eb8e9d028a8231f142fae01f to your computer and use it in GitHub Desktop.
Save ironpillow/97cb3dd6eb8e9d028a8231f142fae01f to your computer and use it in GitHub Desktop.
## ping 8.8.8.8
### tcpdump -i wlan0-ap
01:39:50.795200 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:50.795234 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:50.796276 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:51.851467 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:51.851502 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:51.851986 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:52.891424 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:52.891457 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:52.891952 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:53.931695 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:53.931730 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:53.931904 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:54.971386 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:54.971420 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:54.971790 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:56.011680 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:56.011713 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:56.012081 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:57.051580 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:57.051615 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:57.051941 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:58.091382 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:58.091416 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:58.091901 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:59.131384 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:59.131418 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:59.131587 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:40:00.171557 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:40:00.171591 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:40:00.172078 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:40:01.211395 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:40:01.211430 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:40:01.211918 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:40:02.251417 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:40:02.251450 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:40:02.251620 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
### tcpdump -i br-lan
01:39:50.795309 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:50.795746 IP test-ap-001.58501 > 10.155.2.2.53: 18929+ PTR? 1.2.155.10.in-addr.arpa. (41)
01:39:50.796167 IP test-ap-001.37159 > 10.155.2.2.53: 59308+ PTR? 1.2.155.10.in-addr.arpa. (41)
01:39:50.796307 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:50.796319 IP 10.155.2.2.53 > test-ap-001.58501: 18929 NXDomain* 0/0/0 (41)
01:39:50.796397 IP 10.155.2.2.53 > test-ap-001.37159: 59308 NXDomain* 0/0/0 (41)
01:39:50.796828 IP test-ap-001.48848 > 10.155.2.2.53: 48684+ PTR? 36.2.155.10.in-addr.arpa. (42)
01:39:50.797157 IP 10.155.2.2.53 > test-ap-001.48848: 48684* 1/0/0 PTR pi01. (60)
01:39:50.797625 IP test-ap-001.60433 > 10.155.2.2.53: 4658+ PTR? 36.2.155.10.in-addr.arpa. (42)
01:39:50.797874 IP 10.155.2.2.53 > test-ap-001.60433: 4658* 1/0/0 PTR pi01. (60)
01:39:51.342403 ARP, Request who-has 10.155.2.1 tell test-ap-001, length 28
01:39:51.342729 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:51.851579 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:51.852022 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:52.891531 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:52.891988 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:53.931808 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:53.931929 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:54.971494 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:54.971824 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:56.011788 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:56.012117 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:56.332581 IP test-ap-001.46138 > ptbtime1.ptb.de.123: NTPv4, Client, length 48
01:39:56.333071 IP test-ap-001.49751 > 10.155.2.2.53: 29761+ PTR? 108.103.53.192.in-addr.arpa. (45)
01:39:56.333473 IP 10.155.2.2.53 > test-ap-001.49751: 29761 1/0/0 PTR ptbtime1.ptb.de. (74)
01:39:56.542517 IP ptbtime1.ptb.de.123 > test-ap-001.46138: NTPv4, Server, length 48
01:39:57.051691 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:57.051971 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:58.091491 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:58.091937 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:59.131491 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:39:59.131613 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:39:59.141694 ARP, Request who-has test-ap-001 tell 10.155.2.2, length 42
01:39:59.141739 ARP, Reply test-ap-001 is-at a4:c5:ef:e0:80:32 (oui Unknown), length 28
01:40:00.171667 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:40:00.172114 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:40:01.211504 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:40:01.211954 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:40:02.251523 ARP, Request who-has 10.155.2.1 tell pi01, length 28
01:40:02.251646 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:40:30.572584 IP test-ap-001.49490 > nu.binary.net.123: NTPv4, Client, length 48
01:40:30.573049 IP test-ap-001.45926 > 10.155.2.2.53: 17162+ PTR? 50.0.229.216.in-addr.arpa. (43)
01:40:30.573432 IP 10.155.2.2.53 > test-ap-001.45926: 17162 1/0/0 PTR nu.binary.net. (70)
01:40:30.643105 IP nu.binary.net.123 > test-ap-001.49490: NTPv4, Server, length 48
01:40:31.644537 IP test-ap-001.35711 > t1.time.bf1.yahoo.com.123: NTPv4, Client, length 48
01:40:31.644994 IP test-ap-001.51260 > 10.155.2.2.53: 5721+ PTR? 89.35.30.72.in-addr.arpa. (42)
01:40:31.645261 IP 10.155.2.2.53 > test-ap-001.51260: 5721 1/0/0 PTR t1.time.bf1.yahoo.com. (77)
01:40:31.743326 IP t1.time.bf1.yahoo.com.123 > test-ap-001.35711: NTPv4, Server, length 48
01:41:00.302059 IP 17.249.28.83.5223 > 10.155.2.77.49298: Flags [P.], seq 659764673:659764726, ack 4147221075, win 297, options [nop,nop,TS val 692145664 ecr 1353918118], length 53
01:41:00.302517 IP test-ap-001.56008 > 10.155.2.2.53: 32293+ PTR? 83.28.249.17.in-addr.arpa. (43)
01:41:00.302869 IP 10.155.2.2.53 > test-ap-001.56008: 32293 NXDomain 0/0/0 (43)
01:41:00.303325 IP test-ap-001.40438 > 10.155.2.2.53: 37305+ PTR? 77.2.155.10.in-addr.arpa. (42)
01:41:00.303557 IP 10.155.2.2.53 > test-ap-001.40438: 37305 NXDomain* 0/0/0 (42)
01:41:05.324029 IP test-ap-001.45677 > 10.155.2.2.53: 22085+ PTR? 162.133.214.34.in-addr.arpa. (45)
01:41:05.363565 IP 10.155.2.2.53 > test-ap-001.45677: 22085 1/0/0 PTR ec2-34-214-133-162.us-west-2.compute.amazonaws.com. (109)
01:41:05.445840 ARP, Request who-has test-ap-001 tell 10.155.2.2, length 42
01:41:05.445885 ARP, Reply test-ap-001 is-at a4:c5:ef:e0:80:32 (oui Unknown), length 28
01:41:13.684172 IP test-ap-001.52613 > 10.155.2.2.53: 52237+ PTR? 81.104.88.52.in-addr.arpa. (43)
01:41:13.743760 IP 10.155.2.2.53 > test-ap-001.52613: 52237 1/0/0 PTR ec2-52-88-104-81.us-west-2.compute.amazonaws.com. (105)
01:41:13.744212 IP test-ap-001.52294 > 10.155.2.2.53: 3126+ PTR? 11.2.155.10.in-addr.arpa. (42)
01:41:31.581860 IP6 fe80::a6c5:efff:fee0:8032 > ip6-allnodes: ICMP6, router advertisement, length 64
01:41:31.582505 IP test-ap-001.50705 > 10.155.2.2.53: 54486+ PTR? 2.3.0.8.0.e.e.f.f.f.f.e.5.c.6.a.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (90)
01:41:31.582917 IP 10.155.2.2.53 > test-ap-001.50705: 54486 NXDomain* 0/0/0 (90)
01:41:56.822567 IP test-ap-001.54142 > time.nullroutenetworks.com.123: NTPv4, Client, length 48
01:41:56.834220 IP time.nullroutenetworks.com.123 > test-ap-001.54142: NTPv4, Server, length 48
01:42:01.765945 ARP, Request who-has test-ap-001 tell 10.155.2.2, length 42
01:42:01.765992 ARP, Reply test-ap-001 is-at a4:c5:ef:e0:80:32 (oui Unknown), length 28
01:42:01.902410 ARP, Request who-has 10.155.2.1 tell test-ap-001, length 28
01:42:01.902721 ARP, Reply 10.155.2.1 is-at ae:3d:00:00:00:02 (oui Unknown), length 42
01:42:08.842578 IP test-ap-001.38556 > ptbtime1.ptb.de.123: NTPv4, Client, length 48
01:42:09.014423 IP ptbtime1.ptb.de.123 > test-ap-001.38556: NTPv4, Server, length 48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment