Created on 08-06-2008 05:13 AM
9.164151 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 9.164575 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 9.173824 10.24.1.1 -> 10.24.10.1: ip-proto-50 156 9.174828 10.24.10.1 -> 10.24.1.1: ip-proto-50 364 9.174828 truncated-ip - 20 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 364 9.183676 10.24.10.1 -> 10.24.1.1: ip-proto-50 308 9.183676 truncated-ip - 21 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 308 9.183970 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 9.184073 10.24.10.1 -> 10.24.1.1: ip-proto-50 92 9.184073 truncated-ip - 20 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 92 9.265988 10.24.1.1 -> 10.24.10.1: ip-proto-50 84 9.278419 10.24.10.1 -> 10.24.1.1: ip-proto-50 108 9.278419 truncated-ip - 19 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 108 9.287059 10.24.10.1 -> 10.24.1.1: ip-proto-50 244 9.287059 truncated-ip - 18 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 244 9.287436 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 9.295359 10.24.10.1 -> 10.24.1.1: ip-proto-50 1460 9.295359 truncated-ip - 19 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1460 9.296935 10.24.10.1 -> 10.24.1.1: ip-proto-50 460 9.296935 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 460 9.297291 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 9.303517 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.303517 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.309656 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.309656 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.310627 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 9.312327 10.24.10.1 -> 10.24.1.1: ip-proto-50 724 9.312327 truncated-ip - 15 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 724 9.318821 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.318821 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.319606 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 9.325128 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.325128 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.328197 10.24.10.1 -> 10.24.1.1: ip-proto-50 836 9.328197 truncated-ip - 18 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 836 9.328880 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 9.334591 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.334591 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.340721 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.340721 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.340923 10.24.10.1 -> 10.24.1.1: ip-proto-50 172 9.340923 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 172 9.341633 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 9.347794 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.347794 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.348879 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 9.351979 10.24.10.1 -> 10.24.1.1: ip-proto-50 988 9.351979 truncated-ip - 18 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 988 9.358363 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.358363 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.359311 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 9.364560 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.364560 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 9.369774 10.24.10.1 -> 10.24.1.1: ip-proto-50 1268 9.369774 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1268 9.370619 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 9.374457 10.24.10.1 -> 10.24.1.1: ip-proto-50 1140 9.374457 truncated-ip - 14 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1140 9.377278 10.24.10.1 -> 10.24.1.1: ip-proto-50 724 9.377278 truncated-ip - 21 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 724 9.377864 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 9.384344 10.24.10.1 -> 10.24.1.1: ip-proto-50 1420 9.384344 truncated-ip - 17 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1420 9.481649 10.24.10.1 -> 10.24.1.1: ip-proto-50 116 9.481649 truncated-ip - 20 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 116 9.482494 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 11.638381 10.24.10.1 -> 10.24.1.1: ip-proto-50 92 11.638381 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 92 11.638849 10.24.1.1 -> 10.24.10.1: ip-proto-50 92 15.635853 10.24.1.1 -> 10.24.10.1: ip-proto-50 92 15.669933 10.24.10.1 -> 10.24.1.1: ip-proto-50 100 15.669933 truncated-ip - 14 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 100 15.731477 10.24.1.1 -> 10.24.10.1: ip-proto-50 132 16.044901 10.24.10.1 -> 10.24.1.1: ip-proto-50 76 16.044901 truncated-ip - 20 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 76 16.108037 10.24.1.1 -> 10.24.10.1: ip-proto-50 148 16.154262 10.24.10.1 -> 10.24.1.1: ip-proto-50 76 16.154262 truncated-ip - 20 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 76 18.405066 10.24.10.1 -> 10.24.1.1: ip-proto-50 92 18.405066 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 92 18.405469 10.24.1.1 -> 10.24.10.1: ip-proto-50 92 22.615196 10.24.10.1 -> 10.24.1.1: ip-proto-50 84 22.615196 truncated-ip - 20 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 84 22.615595 10.24.1.1 -> 10.24.10.1: ip-proto-50 84 22.634223 10.24.10.1 -> 10.24.1.1: ip-proto-50 76 22.634223 truncated-ip - 20 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 76 22.635951 10.24.10.1 -> 10.24.1.1: ip-proto-50 356 22.635951 truncated-ip - 21 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 356 22.642641 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 22.642641 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 22.643239 10.24.1.1 -> 10.24.10.1: ip-proto-50 76 22.668604 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 22.668604 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 22.674708 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468 22.674708 truncated-ip - 16 bytes missing! 10.24.10.1 -> 10.24.1.1: ip-proto-50 1468Thanks for reading! stephan
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
> ping -f -l 1400 192.168.x.xGood luck
Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com
Created on 08-06-2008 06:55 AM
Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com
Created on 08-06-2008 07:13 AM
diagnose hardware deviceinfo nic interface_nameIf you have errors, run the command additional times and see if the count grows. You may have an autonegotiation issue as I did, or a duplex mismatch.
Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com
Created on 08-07-2008 12:03 AM
FG400A-2 # diagnose hardware deviceinfo nic port4 Description Intel(R) PRO/100 M Desktop Adapter Driver_Name e100 Driver_Version 2.1.29 PCI_Vendor 0x8086 PCI_Device_ID 0x1229 PCI_Subsystem_Vendor 0x8086 PCI_Subsystem_ID 0x0070 PCI_Revision_ID 0x0010 PCI_Bus 3 PCI_Slot 6 IRQ 20 System_Device_Name port4 Current_HWaddr 00:09:0F:09:00:03 Permanent_HWaddr 00:09:0F:84:76:ED Part_Number ffffff-0ff Link up Speed 100 Duplex full FlowControl receive/transmit State up Rx_Packets 2877827 Tx_Packets 1022152 Rx_Bytes 1619676618 Tx_Bytes 452862314 Rx_Errors 0 Tx_Errors 10 Rx_Dropped 0 Tx_Dropped 0 Multicast N/A Collisions 0 Rx_Length_Errors 0 Rx_Over_Errors 0 Rx_CRC_Errors 0 Rx_Frame_Errors 0 Rx_FIFO_Errors 0 Rx_Missed_Errors 0 Tx_Aborted_Errors 0 Tx_Carrier_Errors 10 Tx_FIFO_Errors 0 Tx_Heartbeat_Errors 0 Tx_Window_Errors 0 Rx_TCP_Checksum_Good 0 Rx_TCP_Checksum_Bad 0 Tx_TCP_Checksum_Good 0 Tx_TCP_Checksum_Bad 0 Tx_Single_Collision_Frames 0 Tx_Multi_Collision_Frames 0 Tx_Deferred 0 Rx_Symbol_Errors 0 Tx_Pause_Frames 0 Rx_Pause_Frames 0 Rx_Control_Unknown_Opcodes 0 Tx_TCO_Packets 0 Rx_TCO_Packets 0 Rx_Interrupt_Packets 0 Rx_Polling_Packets 2879708 Polling_Interrupt_Switch 0Rx/TxBytes and Packtes increase, other than that, only Rx_Polling_Packets increase. On the 60Bs:
# diagnose hardware deviceinfo nic wan1 Description sundance Ethernet driver1.01+LK1.21 chip_id 6 IRQ 5 System_Device_Name wan1 Current_HWaddr 00:09:0f:79:0a:ae Permanent_HWaddr 00:09:0f:79:0a:ae State up Link up Speed 100 Duplex full Rx_Packets 621178 Tx_Packets 963582 Rx_Bytes 112144056 Tx_Bytes 479493981 Collisions 0 Rx_Missed_Errors 0 Tx_Carrier_Errors 0 and # diagnose hardware deviceinfo nic wan1 Description sundance Ethernet driver1.01+LK1.21 chip_id 6 IRQ 5 System_Device_Name wan1 Current_HWaddr 00:09:0f:79:05:62 Permanent_HWaddr 00:09:0f:79:05:62 State up Link up Speed 100 Duplex full Rx_Packets 478361 Tx_Packets 601930 Rx_Bytes 232205448 Tx_Bytes 510926723 Collisions 0 Rx_Missed_Errors 0 Tx_Carrier_Errors 0100/Full is correct everywhere... Thanks stephan
Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com
Created on 08-07-2008 07:11 AM
Created on 08-12-2008 12:00 AM
The truncated-ip message is an expected behavior. What happens is that when Fortigate gets packets through the VPN it tries to match the packet header as a normal packet but it does not match thats why it shows it as truncated packet. Its normal for VPN traffic and it does not create any performance problem on the network or on the unit.You will not see truncated-ip messages when sniffing on interface any - this is something like when do a trace on a LAN interface with Wireshark and get currupted TCP checksums. Everything fine, just the sniffer getting something wrong :-) Thanks.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1688 | |
1087 | |
752 | |
446 | |
228 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.