##Google Analz## ##Microsoft## ##Googel## Swanand: October 2014

Saturday, 11 October 2014

Assigned Internet Protocol Numbers

Assigned Internet Protocol Numbers

Registration Procedure(s)
IESG Approval or Standards Action
Reference
[RFC5237][RFC7045]
Note
In the Internet Protocol version 4 (IPv4) [RFC791] there is a field
called "Protocol" to identify the next level protocol.  This is an 8
bit field.  In Internet Protocol version 6 (IPv6) [RFC2460], this field
is called the "Next Header" field.
Note
Values that are also IPv6 Extension Header Types should be listed in the 
IPv6 Extension Header Types registry at [IANA registry ipv6-parameters].


Decimal Keyword Protocol IPv6 Extension Header Reference
0HOPOPTIPv6 Hop-by-Hop OptionY[RFC2460]
1ICMPInternet Control Message[RFC792]
2IGMPInternet Group Management[RFC1112]
3GGPGateway-to-Gateway[RFC823]
4IPv4IPv4 encapsulation[RFC2003]
5STStream[RFC1190][RFC1819]
6TCPTransmission Control[RFC793]
7CBTCBT[Tony_Ballardie]
8EGPExterior Gateway Protocol[RFC888][David_Mills]
9IGPany private interior gateway (used by Cisco for their IGRP)[Internet_Assigned_Numbers_Authority]
10BBN-RCC-MONBBN RCC Monitoring[Steve_Chipman]
11NVP-IINetwork Voice Protocol[RFC741][Steve_Casner]
12PUPPUP[Boggs, D., J. Shoch, E. Taft, and R. Metcalfe, "PUP: An Internetwork Architecture", XEROX Palo Alto Research Center, CSL-79-10, July 1979; also in IEEE Transactions on Communication, Volume COM-28, Number 4, April 1980.][[XEROX]]
13ARGUSARGUS[Robert_W_Scheifler]
14EMCONEMCON[<mystery contact>]
15XNETCross Net Debugger[Haverty, J., "XNET Formats for Internet Protocol Version 4", IEN 158, October 1980.][Jack_Haverty]
16CHAOSChaos[J_Noel_Chiappa]
17UDPUser Datagram[RFC768][Jon_Postel]
18MUXMultiplexing[Cohen, D. and J. Postel, "Multiplexing Protocol", IEN 90, USC/Information Sciences Institute, May 1979.][Jon_Postel]
19DCN-MEASDCN Measurement Subsystems[David_Mills]
20HMPHost Monitoring[RFC869][Bob_Hinden]
21PRMPacket Radio Measurement[Zaw_Sing_Su]
22XNS-IDPXEROX NS IDP["The Ethernet, A Local Area Network: Data Link Layer and Physical Layer Specification", AA-K759B-TK, Digital Equipment Corporation, Maynard, MA. Also as: "The Ethernet - A Local Area Network", Version 1.0, Digital Equipment Corporation, Intel Corporation, Xerox Corporation, September 1980. And: "The Ethernet, A Local Area Network: Data Link Layer and Physical Layer Specifications", Digital, Intel and Xerox, November 1982. And: XEROX, "The Ethernet, A Local Area Network: Data Link Layer and Physical Layer Specification", X3T51/80-50, Xerox Corporation, Stamford, CT., October 1980.][[XEROX]]
23TRUNK-1Trunk-1[Barry_Boehm]
24TRUNK-2Trunk-2[Barry_Boehm]
25LEAF-1Leaf-1[Barry_Boehm]
26LEAF-2Leaf-2[Barry_Boehm]
27RDPReliable Data Protocol[RFC908][Bob_Hinden]
28IRTPInternet Reliable Transaction[RFC938][Trudy_Miller]
29ISO-TP4ISO Transport Protocol Class 4[RFC905][<mystery contact>]
30NETBLTBulk Data Transfer Protocol[RFC969][David_Clark]
31MFE-NSPMFE Network Services Protocol[Shuttleworth, B., "A Documentary of MFENet, a National Computer Network", UCRL-52317, Lawrence Livermore Labs, Livermore, California, June 1977.][Barry_Howard]
32MERIT-INPMERIT Internodal Protocol[Hans_Werner_Braun]
33DCCPDatagram Congestion Control Protocol[RFC4340]
343PCThird Party Connect Protocol[Stuart_A_Friedberg]
35IDPRInter-Domain Policy Routing Protocol[Martha_Steenstrup]
36XTPXTP[Greg_Chesson]
37DDPDatagram Delivery Protocol[Wesley_Craig]
38IDPR-CMTPIDPR Control Message Transport Proto[Martha_Steenstrup]
39TP++TP++ Transport Protocol[Dirk_Fromhein]
40ILIL Transport Protocol[Dave_Presotto]
41IPv6IPv6 encapsulation[RFC2473]
42SDRPSource Demand Routing Protocol[Deborah_Estrin]
43IPv6-RouteRouting Header for IPv6Y[Steve_Deering]
44IPv6-FragFragment Header for IPv6Y[Steve_Deering]
45IDRPInter-Domain Routing Protocol[Sue_Hares]
46RSVPReservation Protocol[RFC2205][RFC3209][Bob_Braden]
47GREGeneric Routing Encapsulation[RFC2784][Tony_Li]
48DSRDynamic Source Routing Protocol[RFC4728]
49BNABNA[Gary Salamon]
50ESPEncap Security PayloadY[RFC4303]
51AHAuthentication HeaderY[RFC4302]
52I-NLSPIntegrated Net Layer Security TUBA[K_Robert_Glenn]
53SWIPEIP with Encryption[John_Ioannidis]
54NARPNBMA Address Resolution Protocol[RFC1735]
55MOBILEIP Mobility[Charlie_Perkins]
56TLSPTransport Layer Security Protocol using Kryptonet key management[Christer_Oberg]
57SKIPSKIP[Tom_Markson]
58IPv6-ICMPICMP for IPv6[RFC2460]
59IPv6-NoNxtNo Next Header for IPv6[RFC2460]
60IPv6-OptsDestination Options for IPv6Y[RFC2460]
61any host internal protocol[Internet_Assigned_Numbers_Authority]
62CFTPCFTP[Forsdick, H., "CFTP", Network Message, Bolt Beranek and Newman, January 1982.][Harry_Forsdick]
63any local network[Internet_Assigned_Numbers_Authority]
64SAT-EXPAKSATNET and Backroom EXPAK[Steven_Blumenthal]
65KRYPTOLANKryptolan[Paul Liu]
66RVDMIT Remote Virtual Disk Protocol[Michael_Greenwald]
67IPPCInternet Pluribus Packet Core[Steven_Blumenthal]
68any distributed file system[Internet_Assigned_Numbers_Authority]
69SAT-MONSATNET Monitoring[Steven_Blumenthal]
70VISAVISA Protocol[Gene_Tsudik]
71IPCVInternet Packet Core Utility[Steven_Blumenthal]
72CPNXComputer Protocol Network Executive[David Mittnacht]
73CPHBComputer Protocol Heart Beat[David Mittnacht]
74WSNWang Span Network[Victor Dafoulas]
75PVPPacket Video Protocol[Steve_Casner]
76BR-SAT-MONBackroom SATNET Monitoring[Steven_Blumenthal]
77SUN-NDSUN ND PROTOCOL-Temporary[William_Melohn]
78WB-MONWIDEBAND Monitoring[Steven_Blumenthal]
79WB-EXPAKWIDEBAND EXPAK[Steven_Blumenthal]
80ISO-IPISO Internet Protocol[Marshall_T_Rose]
81VMTPVMTP[Dave_Cheriton]
82SECURE-VMTPSECURE-VMTP[Dave_Cheriton]
83VINESVINES[Brian Horn]
84TTPTransaction Transport Protocol[Jim_Stevens]
84IPTMInternet Protocol Traffic Manager[Jim_Stevens]
85NSFNET-IGPNSFNET-IGP[Hans_Werner_Braun]
86DGPDissimilar Gateway Protocol[M/A-COM Government Systems, "Dissimilar Gateway Protocol Specification, Draft Version", Contract no. CS901145, November 16, 1987.][Mike_Little]
87TCFTCF[Guillermo_A_Loyola]
88EIGRPEIGRP[Cisco Systems, "Gateway Server Reference Manual", Manual Revision B, January 10, 1988.][Guenther_Schreiner]
89OSPFIGPOSPFIGP[RFC1583][RFC2328][RFC5340][John_Moy]
90Sprite-RPCSprite RPC Protocol[Welch, B., "The Sprite Remote Procedure Call System", Technical Report, UCB/Computer Science Dept., 86/302, University of California at Berkeley, June 1986.][Bruce Willins]
91LARPLocus Address Resolution Protocol[Brian Horn]
92MTPMulticast Transport Protocol[Susie_Armstrong]
93AX.25AX.25 Frames[Brian_Kantor]
94IPIPIP-within-IP Encapsulation Protocol[John_Ioannidis]
95MICPMobile Internetworking Control Pro.[John_Ioannidis]
96SCC-SPSemaphore Communications Sec. Pro.[Howard_Hart]
97ETHERIPEthernet-within-IP Encapsulation[RFC3378]
98ENCAPEncapsulation Header[RFC1241][Robert_Woodburn]
99any private encryption scheme[Internet_Assigned_Numbers_Authority]
100GMTPGMTP[[RXB5]]
101IFMPIpsilon Flow Management Protocol[Bob_Hinden][November 1995, 1997.]
102PNNIPNNI over IP[Ross_Callon]
103PIMProtocol Independent Multicast[RFC4601][Dino_Farinacci]
104ARISARIS[Nancy_Feldman]
105SCPSSCPS[Robert_Durst]
106QNXQNX[Michael_Hunter]
107A/NActive Networks[Bob_Braden]
108IPCompIP Payload Compression Protocol[RFC2393]
109SNPSitara Networks Protocol[Manickam_R_Sridhar]
110Compaq-PeerCompaq Peer Protocol[Victor_Volpe]
111IPX-in-IPIPX in IP[CJ_Lee]
112VRRPVirtual Router Redundancy Protocol[RFC5798]
113PGMPGM Reliable Transport Protocol[Tony_Speakman]
114any 0-hop protocol[Internet_Assigned_Numbers_Authority]
115L2TPLayer Two Tunneling Protocol[RFC3931][Bernard_Aboba]
116DDXD-II Data Exchange (DDX)[John_Worley]
117IATPInteractive Agent Transfer Protocol[John_Murphy]
118STPSchedule Transfer Protocol[Jean_Michel_Pittet]
119SRPSpectraLink Radio Protocol[Mark_Hamilton]
120UTIUTI[Peter_Lothberg]
121SMPSimple Message Protocol[Leif_Ekblad]
122SMSimple Multicast Protocol[Jon_Crowcroft][draft-perlman-simple-multicast]
123PTPPerformance Transparency Protocol[Michael_Welzl]
124ISIS over IPv4[Tony_Przygienda]
125FIRE[Criag_Partridge]
126CRTPCombat Radio Transport Protocol[Robert_Sautter]
127CRUDPCombat Radio User Datagram[Robert_Sautter]
128SSCOPMCE[Kurt_Waber]
129IPLT[[Hollbach]]
130SPSSecure Packet Shield[Bill_McIntosh]
131PIPEPrivate IP Encapsulation within IP[Bernhard_Petri]
132SCTPStream Control Transmission Protocol[Randall_R_Stewart]
133FCFibre Channel[Murali_Rajagopal][RFC6172]
134RSVP-E2E-IGNORE[RFC3175]
135Mobility HeaderY[RFC6275]
136UDPLite[RFC3828]
137MPLS-in-IP[RFC4023]
138manetMANET Protocols[RFC5498]
139HIPHost Identity ProtocolY[RFC5201]
140Shim6Shim6 ProtocolY[RFC5533]
141WESPWrapped Encapsulating Security Payload[RFC5840]
142ROHCRobust Header Compression[RFC5858]
143-252Unassigned[Internet_Assigned_Numbers_Authority]
253Use for experimentation and testingY[RFC3692]
254Use for experimentation and testingY[RFC3692]
255Reserved[Internet_Assigned_Numbers_Authority]

Problem viewing logs from disk on Fortigate 60D



With the new Fortigate 60D and Forti OS 5, the option to view log on disk may now be visible by default when configuring a new firewall.

To fix this, I recommend you to upgrade to the latest Forti OS (at least 5.0.3) and then reformat the log disk following these steps:

FG-60D/FWF-60D
Disk logging has been added back to the FG-60D and FWF-60D models. It is recommended to format the log disk after you enable this feature. To format the log disk, enter the following CLI command:


  • Set the GUI log location back to memory
  • config log setting
  • set gui-location memory
Format the log disk
execute formatlogdisk

Log disk is /dev/sda1.

Formatting this storage will erase all data on it, including logs,
quarantine files; WanOpt caches; and require the unit to reboot.

Do you want to continue? (y/n) [Enter y to continue]. y


  • Log now back in to the GUI after the reboot and the log disk should be available.

Thursday, 9 October 2014

FORTINET FORTIGATE MULTI WAN BASIC SETUP AND TIPS

Fortinet FortiGate firewalls offer multiple Internet support with flexibility in how the different Internet connections are utilized.
There are 2 different ways to configure a multi WAN setup on the firewall which is determined by what is required for the Internet connections.
The first way to configure a multi WAN is for a redundant scenario in which the secondary Internet connection is only used when the primary goes down.  In this scenario the secondary Internet’s static route (gateway) would have a higher metric than the primary so that it is not active when the primary is up. In order to configure a multi WAN setup for Internet redundancy a few steps must be performed which are listed below.
1. Configure the interface to be used for the secondary Internet connection (i.e. Ip address, netmask, administrative access options, etc.)
2. Configure the static route for the secondary Internet’s gateway with a metric that is higher than the primary Internet connection. If the secondary Internet is not a manual connection (i.e. DHCP or PPPoE) you will need to set the metric/distance within the interface settings.
3. Create dead gateway detection entries. These are required when using multiple Internet connections in order for the firewall to know what Internet connections are up/available. The setup for the dead gateway detection is quite simple; add an upstream IP address to be pinged by the FortiGate which will tell the firewall if the connection is up or down. – **see tip below.
4. Configure/copy all the required firewall rules that are needed for the secondary Internet connection, if the primary is WAN1 and the secondary is WAN2 then most or all of the firewall rules for WAN1 will need to be recreated for WAN2 in order to allow traffic when the WAN2 Internet connection is active.
The second type of mutli WAN setup is having both Internet connections active at the same time in order to utilize both connections simultaneously and still have redundancy.
When using both Internet connections at the same time a ECMP (Equal Cost Multi-Path) load balancing method must be selected. The options are “Source IP based” “Weighted load balance” or “Spillover”.
“Source IP based” is the default load balance method which works by using  a round robin method based on source IP addresses. The first outgoing session is routed out of the WAN1 while the second outgoing session from a different source IP address is routed out of the WAN2 Internet connection, then the next connection with a different source IP is routed out the WAN1 and so on for all new connections with different source IP’s.
“Weighted load balance” is used to control which Internet connection will be used more based on weights. For example if WAN1 has a weight of 10 and WAN2 has a weight of 20 then WAN2 would get more sessions as it has the higher value.
“Spillover” is used to control outgoing traffic based on bandwidth usage. For example if WAN1 has been configured with a spillover threshold of 5 Mbit then it will handle all traffic until the bandwidth usage hits 5 Mbit then it will start sending new sessions out of the WAN2 connection until the WAN1 bandwidth usages goes below 5 Mbit then it will send connections out the WAN1 again.
1. Configure the interface to be used for the secondary Internet connection (i.e. IP address, netmask, administrative access options, etc.)
2. Configure the static route for the secondary Internet’s gateway with a metric that is the same as the primary Internet connection. If the secondary Internet is not a manual connection (i.e. DHCP or PPPoE) you will need to set the metric/distance within the interface settings.
Tip – Using priority within the static route will tell the FortiGate which connection has higher priority when the distance/metric are the same. Use the default value of 0 for the priority of the connection you wish to be the primary and a higher priority for the secondary connection. The lower priority primary connection will be used when the FortiGate is not sure which default gateway to use for an outbound connection.
3. Create dead gateway detection entries. These are required when using multiple Internet connections in order for the firewall to know what Internet connections are up/available. The setup for the dead gateway detection is quite simple;  add an upstream IP address to be pinged by the FortiGate which will tell the firewall if the connection is up or down. – **see tip below.
4. Configure/copy all the required firewall rules that are needed for the secondary Internet connection, if the primary is WAN1 and the secondary is WAN2 then most or all of the firewall rules for WAN1 will need to be recreated for WAN2 in order to allow traffic when the WAN2 Internet connection is active.
Tip - To force outgoing traffic through one of the Internet connections regardless of what equal cost load balancing method is being used is accomplished by using policy routes.
Policy routes are very powerful and are checked even before the active route table so any mistakes made can disrupt traffic flows. Basically how they work is by matching all of the configured values within the policy route which can be source IP/network, destination IP/network, protocol, etc. then if a match is made the FortiGate checks for a firewall policy that will allow the traffic. Also if there were policy routes for WAN2 and WAN2 is currently down, then the FortiGate does not try to make any matches for policy routes going out WAN2.
**Tip – When creating dead gateway detection entries, ensure that the ping server IP being used is not the default gateway as default gateway routers are usually directly connected to the FortiGate and the FortiGate will think the connection is always up even if the Internet connection is actually down. This happens because the FortiGate is pinging a local device and not an upstream device through the Internet connection.

Fortinet Firewall CLI Commands

**********************
Fortinet Firewall Commands
**********************

// Health and Status
show [enter]               //Note that output is only non-default values.
show full-configuration   // Show all configurations on the device.
show system interface wan1 | grep -A2 ip // Show WAN and interface information.
get system info admin status // Show logged in users
get system status            // Show system hardware/software update versions
get hardware status          // Detailed hardware model information
get system performance status
get system performance top
show system interface // Interface Configuration
diagnose hardware deviceinfo nic // Interface Statistics/Settings
diagnose hardware sysinfo memory
diag debug crashlog read
diag hardware sysinfo shm     // Device should be in 0, if (>0) then conservemode
get system global | grep -i timer    // Show tcp and udp timers for halfopen and idle
get system session-ttl     // System default tcp-idle session timeout
execute ha manage <devid>    // send heartbeat accross management link.
get hardware nic
diagnose ip address list
get system interface physical
// ARP
diagnose ip arp list
// Track and Troubleshoot
get system session status      // Connection count for ingress/egress
get system session-info full-stat    // Displays session status with breakdown by state
get system session list       // Session list, protocol, expire, src nat, dst nat
diag sys session              // Basic output with no filters of diag sys session
diag sys session filter <option> <value>      // Capture filter based on src, dst, duraction, policy id, vd
// Packet capture
diag debug info     // Displays active debug
diag debug enable     // Enable debug
#diagnose debug flow filter (shows what filters are configured)
#diagnose debug flow filter clear (clear all filter)
#diagnose debug flow filter <options> <value> (configures the filter)
#diagnose debug flow show con enable <show output on console>
#diagnose debug flow show fun enable <show functions>
#diagnose debug flow trace start <number of lines> (to start the trace)
#diagnose debug flow trace stop (to stop the trace)
Example:
diagnose debug reset
diagnose debug enable
diagnose debug flow filter clear
diagnose debug flow filter saddr 192.168.10.1
diagnose debug flow filter dport 80
diagnose debug flow show con enable
diagnose debug flow show fun enable
diagnose debug flow trace start 20
diagnose sniffer packet <interface or ANY> ‘<arguments>’ <level 1-6>
example:
diagnose sniffer packet ANY ‘net 192.168.10.0/24 and not host 192.168.10.1 and port 80 and TCP’ 6
Syn packets only:
diag sniffer packet internal ‘tcp[13] == 2′
to stop:
diagnose debug reset
diagnose debug disable
// Enable packet capture in GUI
System -> Config -> Advanced
Setup packet capture filter, Check box to start, Uncheck to stop.
Download Debug Log
// Show identified devices
diag user device list
// Routes
Interface Up -> Multiple: Select lowest distance -> Dynamic: If same distance choose lowest metric -> Dynamic: If multiple have same distance/metric, depends on protocol -> All “Best Routes” places in table. Match goes to most exact subnet -> Policy routing applied before table lookups.
Route lookups are only for the first packet of each session.
All packets will use same path.
After topology change, routes are flushed and sessions relearned.
get system arp          // ARP Table
get router info routing-table all       // All routing table entries
get router info routing-table details <ip>         // Shows if custom static ordynamic routes exist for dest.
get router info kernel             // Raw kernel routing table
show router static    // Display static routes
// Restore image
execute restore image <firmware_file_name> <TFTP server_ipaddress>    // Restore an image from TFTP
// Provisioning
config system settings        // Configure for layer-3
set opmode nat
end
config system settings       // Configure transparent
set opmode transparent
end
config system global         // Set port for admin if VPN is sharing
set admin-sport 8443
set sslvpn-sport 443
end
config system global        // Enable SCP
set admin-scp enable
cofng system ntp            // Setup NTP
config ntpserver
edit 1
set server 10.0.0.0
end
edit 2
set server 10.0.0.1
end
set ntpsync enable
end
execute time
config system dns          // Setup DNS
set primary  0.0.0.0
set secondary 0.0.00
config log syslogd(2|3) setting     // Enable syslog
set status enable
set server <IP address>
set port 514
set facility user
end
diagnose log test     // Test logging
config system interface          // Setup IP Address
edit wan1
set mode static
set ip 172.16.0.0 255.255.255.0
set vlan id 50
end
config system interface          // LACP port aggregation
edit aggr1
set member “port8″ “port9″
end
config system zone             // Add interfaces to zone
edit outside
set interface internal1 internal 2
enable intrazone traffic
set intrazone allow
end
config router static       // Add default route
edit 1
set gateway 172.16.0.0
end
config router static       // Static route
edit2
set device port1
set dst 10.0.0.0 255.0.0.0
set gateway 10.0.1.1
// Vendor Notes
http://docs.fortinet.com/fgt.html
http://docs.fortinet.com/fgt/handbook/40mr3/fortigate-cli-40-mr3.pdf
http://docs.fortinet.com/fgt50.html

Featured post

Vicidial With WebRTC

Vicidial With WebRTC VICIDial is well known open source call center software. It has been in use by many small to large scaled con...