If I want to monitor a UDP stream and ensure that packets being sent from a source are getting to a receiver, as UDP has no sequence numbers etc etc and is "fire and forget", is the ID field for frangmentation a good way to ensure that the packets tally up from source to the receiver?
I have read on the www, this this could be a dangerous practice?
Can anyone tell me why? It seems to be logical to me, as the TCP stack sets the frag ID and I dont think this has the potential to get overwritten during transmission?
If you are talking about the Identifier field in the IP header, then it's only useful if you somehow could log all of the id's on the sending side and match them up with the id's on the receiving side.
There's no hard and fast rule that id's must be in sequential order(for instance, if I ping an OpenBSD box from Windows, my side sents sequential ID's but the replies are random id's). And even then, other protocols(TCP, ICMP) would get in the way of the sequentiality by stealing the id's for their own use. If you're counting on this, you're out of luck.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...