Re: [j-nsp] ip fragmentation, different mtu sizes

2013-12-20 Thread Phil Fagan
Are you trying to transit 1500 or terminate 1500? You should be able to pass and fragment. But maybe the mgmt plane won't frag if your trying the interface itself. hi, all: i have a genetic question regarding ip fragmentation. i have two routers; one is cisco and another is juniper. they

[j-nsp] ip fragmentation, different mtu sizes

2013-12-17 Thread snort bsd
hi, all: i have a genetic question regarding ip fragmentation. i have two routers; one is cisco and another is juniper. they connected back to back with default ethernet mtu (cisco 1522 and juniper 1518, of course with vlan on both ends). i understand that two vendors have different ways of

Re: [j-nsp] ip fragmentation, different mtu sizes

2013-12-17 Thread Brent Sweeny
you're correct that they calculate sizes differently. Cisco uses the payload size including headers; Juniper just the data-payload size, so for example a 9000 byte layer3 packet for Cisco = 9000 - 20B IP header - 8B ICMP header=8972B for Juniper. you can get them to send unfragmented ICMP packets

Re: [j-nsp] ip fragmentation, different mtu sizes

2013-12-17 Thread snort bsd
thanks. it is not about setting df bits. i didn't set df bits when i sent extended icmp pings between two routers and i wasn't interested in that. there are a few posts clearly explained the differences between two vendors in terms of mtu calculations. that is not the point here. what i am

Re: [j-nsp] ip fragmentation, different mtu sizes

2013-12-17 Thread Brent Sweeny
I believe it does show 'the expected ip fragmentation'. this is from a cisco 2921: tpr-oob#show ip traffic | in frag 0 fragmented, 0 fragments, 0 couldn't fragment tpr-oob#ping somehost size 1600 Type escape sequence to abort. Sending 5, 1600-byte ICMP Echos to somehost, timeout is 2