Thanks. I've solved this problem. The tap devices are showing up in the interface list of wireshark, including tap devices. The tap devices can only have packets when you using them.
On Tue, Jun 9, 2015 at 3:07 PM, Martine Lenders <[email protected]> wrote: > Hi Xili, > did you use the tapsetup script (cpu/native/tapsetup.sh). Usually you need > to set the user for the tap interface to yourself. If you do it by hand: > > sudo ip tuntap add dev tap0 mode tap user ${USER} > > Also make sure you configured the setuid for wireshark correctly and are > in the wireshark user group: > https://ask.wireshark.org/questions/7976/wireshark-setup-linux-for-nonroot-user > > Hope this was helpful, > Martine > > 2015-06-09 20:32 GMT+02:00 Xili Wan <[email protected]>: > >> Hi, >> >> Another question is about using wireshark to monitor the native port. >> I installed wireshark on ubuntu and the plugin for RIOT, but found it >> cannot monitor tap devices (tap0, tap1). This is not the wireshark's >> problem, since it can monitor eth0 device. >> >> How to use the wireshark to monitor the native port? >> >> >> Thanks, >> >> >> Xili >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.riot-os.org/mailman/listinfo/users >> >> > > _______________________________________________ > users mailing list > [email protected] > http://lists.riot-os.org/mailman/listinfo/users > >
_______________________________________________ users mailing list [email protected] http://lists.riot-os.org/mailman/listinfo/users
