On Tue, 10 Nov 2009, Gert Doering wrote:
No. Routers will never reassemble transit traffic.
Never is a strong word. It seems "ip virtual-reassembly" do it. It looks
like it at least reassembles them in memory and delays them before
forwarding them (as fragments) from the debug and counters. On a
virtual 7200:
Router#show ip virtual-reassembly fa1/0
FastEthernet1/0:
Virtual Fragment Reassembly (VFR) is ENABLED...
Concurrent reassemblies (max-reassemblies): 16
Fragments per reassembly (max-fragments): 32
Reassembly timeout (timeout): 3 seconds
Drop fragments: OFF
Current reassembly count:0
Current fragment count:0
Total reassembly count:23
Total reassembly timeout count:3
Not that you'd want to do it, but still.
---------
typedef struct me_s {
char name[] = { "Thomas Habets" };
char email[] = { "tho...@habets.pp.se" };
char kernel[] = { "Linux" };
char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt"; };
char pgp[] = { "A8A3 D1DD 4AE0 8467 7FDE 0945 286A E90A AD48 E854" };
char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" };
} me_t;
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
