![]() ![]() Feel free to play with those filters in tcpdump and you will find nearly everything.įeel free to comment and i will add everything in more detail. So basically 192.168.1.1 will not be displayed on WAN port etc. Identification 32 bits identifier for reassembly. ![]() Initialized to zero for transmission ignored on reception. Keep in mind, XG has to NAT the traffic etc. that the IPv6 header and extensions headers which need to be processed at every hop cannotbe fragmented This is known as the 'Unfragmentable Part' in IPv6 jargon. The packet arrives on Port1, will transferred to br0 and leaves the appliance on Port2 with my MASQ ip. In my case, i am using a bridge, so i will see the packets 3 times. Tcpdump -ni Port3 host 192.168.1.2 and port 443įor better understanding, you can write the dump into a file with -b -w /tmp/dump.pcapĪnd you can open this file with wireshark and use the power of wireshark to troubleshoot. You can also specify the port with replacing any to the wanted interface (Port3). Basically you can use all kind of logical connectives like and, or, nor etc. ![]() I cannot recommend this because you will see the SSH Traffic as well.įilter the traffic with port PORTNUMBER and / or host IP_Address. You will see all the traffic on all Interfaces with all IPs. Refer to the man page of tcpdump for all kind of filter. Most of the time, i have to write down, how it is done, so i will summarize it here.įirst of all, get a SSH Session to your XG. I want to share my experience in dumping on XG with you. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |