Hello all,
I'm setting the DSCP on some traffic going out and getting in on my firewall.
With NFSEN I collect traffic from both segments, LAN and WAN Firewall sides.
On my firewall I set DSCP to 101110 for real-time traffic and I clearly see it
on Nprobe server on both segments, as soon as I filter with TCPDump:
tcpdump -i eth2 -vvv -n ip and ip[1]=0xb8
0xb8 is 184 in HEX.. and I see this on eth2 (WAN) and eth3 (LAN):
14:21:23.236494 IP (tos 0xb8, ttl 126, id 4388, offset 0, flags [DF], proto TCP
(6), length 450)
217.xx.xx.xx.47460 > 64.xx.xx.xx.https: Flags [P.], cksum 0x5af4 (correct),
seq 949:1359, ack 84, win 256, length 410
But as soon as I filter on NFSEN with syntax Tos 184 or tos 0xb8 I don't see
anything.
Is there any reason? Can someone help me a bit on this?
Thanks in advance,
Cordiali saluti,
[cid:image001.jpg@01CFE239.07CB4910]
Oliver Lagni
Product Specialist Networking
oliver.la...@lanewan.it<mailto:oliver.la...@lanewan.it>
+39 049 8843198 office phone
+39 049 8843206 fax
www.lanewan.it<http://www.lanewan.it/>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Nfsen-discuss mailing list
Nfsen-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
