To monitor IPv6 traffic using tcpdump you can use the option “-i ip6″:
tcpdump -i ethX ip6
- Released Zabbix-Reporter-0.05 #cpan #zabbix
http://t.co/6qpm6kxGJ221.05.2013 19:54 - GeoGuessr:
http://t.co/sNw883hRDx20.05.2013 07:51 - Daft Punk rock with Get Lucky
http://t.co/TQCDQqMznr14.05.2013 18:01 - Released Zabbix-Reporter-0.04 #cpan #zabbix
http://t.co/EHzFkgLe4t13.05.2013 20:12 - Released Zabbix-Reporter-0.03 #cpan #zabbix
http://t.co/zS0RQ4eqEJ05.05.2013 11:10 - @psy_oppa
watch the #happening from germany at
http://t.co/n2yzUB37bH13.04.2013 10:51 - Released Zabbix-Reporter-0.02 #cpan #zabbix
http://t.co/s3HixRpS3G29.03.2013 20:04 - Released Zabbix-Reporter-0.01 #cpan #zabbix
http://t.co/e9Mj2DHX3P27.03.2013 23:51 - Trouble accessing your #dovecot mail server from your mobile? Make sure to allow plenty of connections.26.03.2013 12:35
- @puppetlabs
Most #puppet #hiera docs are outdated or inaccurate. Watch out.26.03.2013 11:53
Banner
You have a little mistake, -i is a option for the interface.
For IPv6 you use: “tcpdump ipv -i eth1″
Thats wrong also
Its:
tcpdump -i ethX ipvY
X: Ethernet Port
Y: 4 or 6 for IPv4 or IPv6
WordPress ate my interface. Of course you can’t specify the protocol as an interface