<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:blogger='http://schemas.google.com/blogger/2008' xmlns:georss='http://www.georss.org/georss' xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-36141300</id><updated>2024-11-01T13:19:51.389+01:00</updated><category term="web"/><category term="review"/><category term="Windows"/><category term="Microsoft"/><category term="network"/><category term="multimedia"/><category term="Fortinet"/><category term="cisco"/><category term="SSL"/><category term="MSI"/><category term="blogger"/><category term="DVD"/><category term="Kerio"/><category term="DNS"/><category term="Linux"/><category term="MikroTik"/><category term="cloud"/><category term="development"/><category term="IIS"/><category term="ISA"/><category term="email"/><category term="AWS"/><category term="IE"/><category term="IPv6"/><category term="photo"/><category term="s60"/><category term="BSOD"/><category term="F5"/><category term="embedded"/><category term="AdvancedInstaller"/><category term="Genealogy"/><category term="Geolocation"/><category term="Google"/><category term="MAC"/><category term="Meru"/><category term="VoIP"/><category term="azure"/><category term="iFolder"/><title type='text'>The world seen from an IT consultant&#39;s perspective</title><subtitle type='html'>What &lt;b&gt;I&lt;/b&gt; care about...</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://blog.helge.net/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default?alt=atom'/><link rel='alternate' type='text/html' href='http://blog.helge.net/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default?alt=atom&amp;start-index=26&amp;max-results=25'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>319</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-36141300.post-4539866710796725493</id><published>2017-09-19T10:17:00.002+02:00</published><updated>2017-09-19T10:17:34.766+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="SSL"/><category scheme="http://www.blogger.com/atom/ns#" term="web"/><title type='text'>How to create a certificate request with a SAN extension</title><content type='html'>Here is how to create a SSL certificate with subject alternate names (SAN). This extension is required by newer browsers.&lt;br /&gt;
&lt;div class=&quot;picture&quot;&gt;&lt;img alt=&quot;Lock and chain&quot; src=&quot;http://static.helge.net/images/clipart/400/7639877.thb.jpg&quot; height=&quot;263&quot; width=&quot;350&quot; /&gt;&lt;/div&gt;&lt;br /&gt;
First you need to create a private key to use with your certificate.&lt;br /&gt;
&lt;div class=&quot;listbox&quot;&gt;openssl genrsa 2048 &amp;gt; priv.key&lt;/div&gt;We now need to create a configuration file with the needed details. An example for www.helge.net is provided. Save this file as openssl.cnf.&lt;br /&gt;
&lt;div class=&quot;listbox&quot;&gt;[ req ]&lt;br /&gt;
default_bits = 2048&lt;br /&gt;
default_keyfile = priv.key&lt;br /&gt;
distinguished_name = my_DN&lt;br /&gt;
encrypt_key = no&lt;br /&gt;
prompt = no&lt;br /&gt;
string_mask = nombstr&lt;br /&gt;
req_extensions = v3_req&lt;br /&gt;
&lt;br /&gt;
[ my_DN ]&lt;br /&gt;
C = NO&lt;br /&gt;
L = Oslo&lt;br /&gt;
O = Helge Olav Helgesen&lt;br /&gt;
CN = www.helgenet&lt;br /&gt;
&lt;br /&gt;
[ v3_req ]&lt;br /&gt;
basicConstraints = CA:FALSE&lt;br /&gt;
keyUsage = digitalSignature, keyEncipherment, dataEncipherment&lt;br /&gt;
extendedKeyUsage = serverAuth, clientAuth&lt;br /&gt;
subjectAltName = DNS: www.helge.net, DNS: helge.net, IP:1.1.1.1&lt;br /&gt;
&lt;br /&gt;
[ req_distinguished_name ]&lt;br /&gt;
0.organizationName = Helge Olav Helgesen&lt;br /&gt;
organizationalUnitName = IT&lt;br /&gt;
commonName = www.helge.net&lt;br /&gt;
&lt;/div&gt;When this is done you have to create the request.&lt;br /&gt;
&lt;div class=&quot;listbox&quot;&gt;openssl req -new -key priv.key -out cert.csr -config openssl.cnf -days 1000 -sha256&lt;/div&gt;You can now send your CSR to an online certificate authority. They will know  what to do with it. In return they will send back a certificate you can use with  your web server.&lt;br /&gt;
More detailed information can be found &lt;a href=&quot;http://www.openssl.org/docs/HOWTO/certificates.txt&quot; target=&quot;_blank&quot;&gt; here&lt;/a&gt;.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/4539866710796725493'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/4539866710796725493'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2017/09/how-to-create-certificate-request-with.html' title='How to create a certificate request with a SAN extension'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-6690252897485333422</id><published>2015-09-29T13:51:00.001+02:00</published><updated>2015-09-29T13:51:39.134+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="cisco"/><title type='text'>Disable device tracking on 4500X</title><content type='html'>&lt;p&gt;Today I came across an issue that does not appear to have a good solution. Cisco’s device tracking feature is known to cause IP conflicts on Windows based clients. So you won’t turn it on unless you really need it.&lt;/p&gt;
&lt;p&gt;Cisco has lots of ways to try solve this issue but none worked for me. The 4500X is running 03.07.01.&lt;/p&gt;
&lt;p&gt;After upgrading some Cisco 3750X switches to 4500X on a network with MACSec encryption enabled between switches it appears that ipdt is automatically on port that you encrypt causing lots of IP address conflicts. If you look at the output you’ll see that the port has registered two features:&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;switch#show ip device tracking int t1/32&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;--------------------------------------------&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;Interface TenGigabitEthernet1/32 is: STAND ALONE&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;&lt;span style=&quot;color: #ff2600;&quot;&gt;IP Device Tracking = Enabled&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;IP Device Tracking Probe Count = 3&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;IP Device Tracking Probe Interval = 30&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;IPv6 Device Tracking Client Registered Handle: 2&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;IP Device Tracking Enabled Features:&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;&lt;span style=&quot;color: #ff2600;&quot;&gt;HOST_TRACK_CLIENT_CTS&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;&lt;span style=&quot;color: #ff2600;&quot;&gt;HOST_TRACK_CLIENT_SM&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The port configuration is as follows:&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;interface TenGigabitEthernet1/32&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt; switchport mode trunk&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt; cts manual &lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;  no propagate sgt&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;  sap pmk my-key mode-list gcm-encrypt   &lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;end&lt;/p&gt;
&lt;p&gt;The only way I have found to solve this issue is to apply the command below.&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;interface TenGigabitEthernet1/32&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt; ip device tracking maximum 0&lt;/p&gt;
&lt;p&gt;After this change device tracking was disabled on the port.&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;switch#show ip device tracking int t1/32&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;--------------------------------------------&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;Interface TenGigabitEthernet1/32 is: STAND ALONE&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;&lt;span style=&quot;color: #ff2600;&quot;&gt;IP Device Tracking = Disabled&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;IP Device Tracking Probe Count = 3&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;IP Device Tracking Probe Interval = 30&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;IPv6 Device Tracking Client Registered Handle: 2&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;IP Device Tracking Enabled Features:&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;&lt;span style=&quot;color: #ff2600;&quot;&gt;HOST_TRACK_CLIENT_TRACK_HOST_UPTO_MAX&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;HOST_TRACK_CLIENT_CTS&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;HOST_TRACK_CLIENT_SM &lt;/p&gt;
&lt;p&gt;Some additional reading:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;http://www.cisco.com/c/en/us/support/docs/ip/address-resolution-protocol-arp/118630-technote-ipdt-00.html&quot;&gt;IP device tracking overview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst4500/15-1/XE_330SG/configuration/guide/config/swmacsec.html&quot;&gt;MACSec encryption&lt;/a&gt; &lt;/li&gt;
&lt;/ul&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/6690252897485333422'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/6690252897485333422'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2015/09/disable-device-tracking-on-4500x.html' title='Disable device tracking on 4500X'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-7264279938633493283</id><published>2014-11-18T17:55:00.001+01:00</published><updated>2014-11-18T17:55:59.937+01:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="SSL"/><category scheme="http://www.blogger.com/atom/ns#" term="Windows"/><title type='text'>How to list certification authorities in a domain</title><content type='html'>&lt;p&gt;Often when you go to a customer you need to see if they have a certification authority. The easiest way to do so is to run this command:&lt;/p&gt;
&lt;p class=&quot;computertext&quot;&gt;certutil -config - -ping&lt;/p&gt;
&lt;p&gt;And you will get a list of CA in the domain.&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/7264279938633493283'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/7264279938633493283'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/11/how-to-list-certification-authorities.html' title='How to list certification authorities in a domain'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-8040407084816500950</id><published>2014-11-11T10:07:00.001+01:00</published><updated>2014-11-11T10:07:40.312+01:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Microsoft"/><title type='text'>NPS events not showing up in event viewer</title><content type='html'>&lt;p&gt;Issue: Windows 2008 event viewer, can’t find any event logs for successful or rejected authentications even if the NPS is configured to log to the event viewer.&lt;/p&gt;
&lt;p&gt;Solution is to run this command:&lt;/p&gt;
&lt;p class=&quot;computertext&quot;&gt;auditpol /set /subcategory:&quot;Network Policy Server&quot; /success:enable /failure:enable&lt;/p&gt;
&lt;p&gt;Source: &lt;a href=&quot;http://support.microsoft.com/kb/951005&quot;&gt;Microsoft KB 951005&lt;/a&gt;&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/8040407084816500950'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/8040407084816500950'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/11/nps-events-not-showing-up-in-event.html' title='NPS events not showing up in event viewer'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-6015879148810790640</id><published>2014-10-04T00:21:00.001+02:00</published><updated>2014-10-04T00:21:45.386+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="embedded"/><category scheme="http://www.blogger.com/atom/ns#" term="network"/><title type='text'>iperf performance on Raspberry PI model B</title><content type='html'>&lt;p&gt;iperf is  a great tool to measure the performance on your network. It works by measuring how much data can be sent  between two hosts.&lt;/p&gt;
&lt;p&gt;When using iperf many variables come into play; like latency, bandwidth between the hosts, OS performance, the switches and the hardware on your computers. Because of this it is good have an idea of what the Raspberry can perform and what you can expect from it.&lt;/p&gt;
&lt;p&gt;In my test there was a big difference between inbound and outbound traffic as seen from the Raspberry.&lt;/p&gt;
&lt;p&gt;Traffic from Pi: 93Mb/sec&lt;br /&gt;Traffic to Pi: 70Mb/sec&lt;/p&gt;
&lt;p&gt;During the test the Pi CPU load was about 95 %, indicating that without &lt;a href=&quot;http://www.raspberrypi.org/introducing-turbo-mode-up-to-50-more-performance-for-free/&quot;&gt;overclocking&lt;/a&gt; you can’t expect more from this box.&lt;/p&gt;
&lt;h3&gt;Test configuration&lt;/h3&gt;
&lt;p&gt;This is the configuration I ran for test. The test was done by sending traffic in one direction successively.&lt;/p&gt;
&lt;p class=&quot;picture&quot;&gt;&lt;img title=&quot;Network setup&quot; src=&quot;http://static.helge.net/images/2014/10/141003_raspberry_pi.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;p&gt;My Pi was installed with Raspbian GNU/Linux 7 3.12.28 and iperf installed from apt-get. My Mac was running iperf installed via Brew. The Pi was a fresh install and only with other default daemons running.&lt;/p&gt;
&lt;p&gt;The Raspberry Pi is equipped with a 100Mb interface.&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/6015879148810790640'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/6015879148810790640'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/10/iperf-performance-on-raspberry-pi-model.html' title='iperf performance on Raspberry PI model B'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-8420348721468208389</id><published>2014-09-26T15:04:00.001+02:00</published><updated>2014-09-26T15:04:05.746+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="SSL"/><title type='text'>Watch out for your SHA-1 signed certificates</title><content type='html'>&lt;p&gt;Microsoft and Google are with their browsers two major consumers of SSL certificates. They have both announced that they no longer will support certificates signed with SHA1.&lt;/p&gt;
&lt;p&gt;But they both hanlde this differently. Google Chrome will on their side give a certificate warning for all SSL certificates signed with SHA1 beginning in January 2015 for certificates that expire after 2017. Microsoft will (from current statements) only give a warning after 2017 for SHA-1 signed certificates.&lt;/p&gt;
&lt;p&gt;To ensure a smooth migration you need to make sure that both your servers and clients support the new SHA-2 (SHA-256) signing scheme. Expect older servers not to support this and plan for an upgrade.&lt;/p&gt;
&lt;p&gt;Sources:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;http://blogs.technet.com/b/pki/archive/2013/11/12/sha1-deprecation-policy.aspx&quot;&gt;Microsoft SHA1 deprecation policy&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility&quot;&gt;SHA-256 compatibility list&lt;/a&gt;, from GlobalSign.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;http://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html&quot;&gt;Google Chrome&lt;/a&gt; policy.&lt;/li&gt;
&lt;/ul&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/8420348721468208389'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/8420348721468208389'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/09/watch-out-for-your-sha-1-signed.html' title='Watch out for your SHA-1 signed certificates'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-3271925969632073646</id><published>2014-09-18T00:07:00.001+02:00</published><updated>2014-09-18T00:07:24.549+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="cisco"/><title type='text'>The exact route limit on the Cisco 3850</title><content type='html'>&lt;p&gt;In a previous post I wrote about the &lt;a href=&quot;http://blog.helge.net/2013/10/too-many-routes-on-cisco-switch.html&quot;&gt;route limit&lt;/a&gt; on the Cisco 3850 platform. After the issue earlier this year with the Cisco routers hitting the &lt;a href=&quot;http://www.datacenterknowledge.com/archives/2014/08/13/bgp-routing-table-size-limit-blamed-for-tuesdays-website-outages/&quot;&gt;limit of 512k routes&lt;/a&gt; in hardware I think I have to clarify how many routes the Cisco 3850 platform supports. Cisco only releases these numbers for their &lt;a href=&quot;https://supportforums.cisco.com/document/12202206/size-internet-global-routing-table-and-its-potential-side-effects&quot;&gt;big routers&lt;/a&gt;. The specification states 27000 routes.&lt;/p&gt;
&lt;p&gt;To see the exact number of routes you can query the router directly.&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;my-switch#sho platform tcam utilization asic all           &lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;CAM Utilization for ASIC# 0&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt; Table                                              Max Values        Used Values&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt; --------------------------------------------------------------------------------&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt; Directly or indirectly connected routes            32768/7680        119/4538&lt;/p&gt;
&lt;p&gt;As you can see the router support 32768 directly connected routes and 7680 indirectly connected routes. A directly connected route is a host connected via L2 to the switch (like a host on a directly connected subnet) whereas indirectly connected routes are routes that are routed via another IP address.&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/3271925969632073646'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/3271925969632073646'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/09/the-exact-route-limit-on-cisco-3850.html' title='The exact route limit on the Cisco 3850'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-7965842824850949916</id><published>2014-09-17T23:53:00.001+02:00</published><updated>2014-09-17T23:53:34.503+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MikroTik"/><title type='text'>How to properly downgrade your MirkoTik</title><content type='html'>&lt;p&gt;It is not easy to downgrade your MikroTik router. In the documentation you’ll find that you can use the “/system package downgrade” to downgrade your router. But this often leaves you with a router that only partially works after the downgrade. IPSec related stuff is known to stop working after the downgrade.&lt;/p&gt;
&lt;p&gt;So how to downgrade? I do it this way:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Get a backup of your configuration using “/export compact”. If you already downgraded your firewall this will not work. You then have to extract just parts of the configuration like “/ip addr ex com” and “/ip route ex com” to get the basic stuff.&lt;/li&gt;
&lt;li&gt;Downgrade your router to the version you are aiming for.&lt;/li&gt;
&lt;li&gt;Create a script file basic.rsc and upload it to the router. This file should contain as little as possible. Just what you need to log on to the router again.&lt;/li&gt;
&lt;li&gt;Do a factory reset using “/system reset-configuration keep-users=yes run-after-reset=basic.rsc”.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;You have to use the extension .rsc or the script won’t run. If there are any configuration errors in this file nothing is executed. That is why you should keep it as small as possible. Just add the lines needed to log into the router. You usually need some IP addresses, routes and perhaps VLAN configuration.&lt;/p&gt;
&lt;p&gt;There is a bug on many versions of the RouterOS that is important to notice. If the script file is less than about 512 bytes the router can’t read it either. If your file is small  you will have to add some lines like “# dummy text to make this a big file” to the end of the file.&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/7965842824850949916'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/7965842824850949916'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/09/how-to-properly-downgrade-your-mirkotik.html' title='How to properly downgrade your MirkoTik'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-7347161824926090952</id><published>2014-09-17T23:40:00.001+02:00</published><updated>2014-09-17T23:54:09.035+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MikroTik"/><title type='text'>RouterOS ICMP fragmentation needed bug</title><content type='html'>&lt;p&gt;On several MikroTik routers, at least one tile and ppc platforms the router won’t send back “ICMP fragmentation needed” packets to the sender if the packet is to big to be sent out on another interface. This bug makes PMTU not work and many applications is broken because of this.&lt;/p&gt;
&lt;p&gt;This issue is found on at RouterOS 6.19. By downgrading to 6.6 this issue disapperars.&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/7347161824926090952'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/7347161824926090952'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/09/routeros-icmp-fragmentation-needed-bug.html' title='RouterOS ICMP fragmentation needed bug'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-117154627361682630</id><published>2014-09-16T18:52:00.001+02:00</published><updated>2014-09-16T18:52:54.370+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="cisco"/><title type='text'>Configure WLC to block client-client traffic</title><content type='html'>&lt;p&gt;When you configure a guest network where the network is unencrypted you often want to block client-to-client traffic so end users cannot communicate directly.&lt;/p&gt;
&lt;p&gt;&lt;img style=&quot;display: block; margin-left: auto; margin-right: auto;&quot; title=&quot;&quot; src=&quot;http://static.helge.net/images/2014/09/wlc-traffic.gif&quot; alt=&quot;&quot; width=&quot;&quot; height=&quot;&quot; border=&quot;0&quot; /&gt;&lt;/p&gt;
&lt;p&gt;This is easy to implement in a setting with only one wireless controller as shown in the diagram.&lt;/p&gt;
&lt;p&gt;To configure you need to find the WLAN ID. This is easy to see by typing the command “show wlan summary” on the CLI. When you have found the ID from display you enable it by typing the command &quot;config wlan peer-blocking drop #”.&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/117154627361682630'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/117154627361682630'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/09/configure-wlc-to-block-client-client.html' title='Configure WLC to block client-client traffic'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-8598002672548073705</id><published>2014-08-14T17:16:00.001+02:00</published><updated>2014-08-14T17:16:48.802+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Fortinet"/><category scheme="http://www.blogger.com/atom/ns#" term="IPv6"/><title type='text'>IPv6 fail on Fortigate</title><content type='html'>&lt;p&gt;&lt;strong&gt;Issue&lt;/strong&gt;: Clients does to receive IPv6 addresses using stateless autoconfiguration. Clients with static IP works as normal. In the system log we see lots of message like “sendmsg: no buffer space available”.&lt;/p&gt;  &lt;p&gt;This is seen on FortiOS 5.0.7.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Solution&lt;/strong&gt;: kill the radvd process on the firewall. This has no side-effects as the process only implements IPv6 routing messages.&lt;/p&gt;  &lt;p&gt;In case you can’t find the process ID, try “diag sys top 10 99” and see if you can find it. You kill the process with the command “diag sys kil 9 &amp;lt;pid&amp;gt;”.&lt;/p&gt;  &lt;p&gt;Sources:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;&lt;a href=&quot;http://en.wikipedia.org/wiki/Radvd&quot; rel=&quot;nofollow&quot; target=&quot;_blank&quot;&gt;radvd&lt;/a&gt; on Wikipedia. &lt;/li&gt; &lt;/ul&gt;  </content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/8598002672548073705'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/8598002672548073705'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/08/ipv6-fail-on-fortigate.html' title='IPv6 fail on Fortigate'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-5710073104645195328</id><published>2014-08-11T14:24:00.001+02:00</published><updated>2014-08-11T14:24:04.887+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="cisco"/><category scheme="http://www.blogger.com/atom/ns#" term="Microsoft"/><category scheme="http://www.blogger.com/atom/ns#" term="network"/><title type='text'>NPS event 6273 reason code 16</title><content type='html'>&lt;p&gt;&lt;strong&gt;Issue&lt;/strong&gt;: can not authenticate users or computers, “Authentication failed due to a user credentials mismatch. Either the user name provided does not map to an existing user account or the password was incorrect.”&lt;/p&gt;  &lt;p&gt;All RADIUS secrets and NPS policies are correct.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Environment&lt;/strong&gt;: NPS running on Windows 2012 R2 domain controller, client on Windows 7 enterprise. Using either Allied Telesis or Cisco switches.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Cause&lt;/strong&gt;: Windows 7 validates the server certificate only by using the Subject field on the certificate. When NPS is installed on a domain controller it will use a certificate template for domain controllers. These sertificates does not fill in the subject field of the certificate.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Solution&lt;/strong&gt;: Grated domain controllers access to the Computer template and issued a new certificate based on this template. Reconfigured NPS to use that one instead.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Source&lt;/strong&gt;: By reading trough a very long &lt;a href=&quot;http://social.technet.microsoft.com/Forums/windowsserver/en-US/76644dcc-911d-451e-b7f1-39269db43ac7/nps-event-6273-reason-code-16&quot; rel=&quot;nofollow&quot; target=&quot;_blank&quot;&gt;article from Technet about this error&lt;/a&gt; this solution appeared to me.&lt;/p&gt;  </content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/5710073104645195328'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/5710073104645195328'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/08/nps-event-6273-reason-code-16.html' title='NPS event 6273 reason code 16'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-2988264068121896669</id><published>2014-06-16T00:59:00.001+02:00</published><updated>2014-06-16T01:01:35.312+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="cisco"/><title type='text'>Multicast drop with LACP</title><content type='html'>&lt;p&gt;Today I had a strange problem on a network with a stack of Cisco 3750X running IOS 15.0(2)SE4.&lt;/p&gt;
&lt;p&gt;All unicast traffic was working but for some reason I noticed that multicast traffic (more specifically OSPF Hello packets) between routers did not pass. One of the routers was configured as a trunk ports with many VLANs and LACP.&lt;/p&gt;
&lt;p&gt;What I saw was that the firewall could se one router, one router could see both the firewall and the other router and the second firewall could only see the first router.&lt;/p&gt;
&lt;p class=&quot;picture&quot;&gt;&lt;img src=&quot;http://static.helge.net/2014/06/3750x_lacp_drop.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt;
&lt;p&gt;This happened after a reload of the entire switch stack, something that I have done many times before. So I can not tell for sure exactly what I did different to cause this problem this time. The switch is configured for src-dst-ip load balancing.&lt;/p&gt;
&lt;p&gt;This seems to be a bug within the Cisco switch as the quick fix that worked for me was to take down one of the ports in the port-channel and later bring it back up.&lt;/p&gt;
&lt;p&gt;Troubleshooting commands that you can use. I did not so I am not sure what its result would be.&lt;/p&gt;
&lt;p&gt;show platform forward gigabitEthernet 1/0/2 vlan 333 1111.2222.3333 3333.2222.1111&lt;br /&gt;test etherchannel load-balance interface po 2 mac c000.1111.1111 2222.2222.2222&lt;br /&gt;test etherchannel load-balance interface po 2 ip 172.30.126.1 224.0.0.5&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/2988264068121896669'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/2988264068121896669'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/06/multicast-drop-with-lacp.html' title='Multicast drop with LACP'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-907434310065927628</id><published>2014-06-16T00:31:00.001+02:00</published><updated>2014-06-16T00:31:30.483+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="cisco"/><title type='text'>Cisco IOS 15.0(2)SE6 is buggy</title><content type='html'>&lt;p&gt;I just upgraded a few Cisco 3750X stacks to this version and all stacks started to misbehave. What I saw before I had to roll back to 15.0(2)SE4 was that:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;99 % CPU load, shared between a 802.1x process and a hrpc hlfm request process.&lt;/li&gt;
&lt;li&gt;Slow console, probably because of the CPU load.&lt;/li&gt;
&lt;li&gt;The switch did not learn MAC addresses on many ports, both port-channels and standalone ports. (All ports I checked was trunk ports.)&lt;/li&gt;
&lt;li&gt;MACSec (using the service module) rekeying timed out and dropped its association to the other party. (Using a pre-shared key.)&lt;/li&gt;
&lt;li&gt;Lots of packet loss.&lt;/li&gt;
&lt;/ul&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/907434310065927628'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/907434310065927628'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/06/cisco-ios-1502se6-is-buggy.html' title='Cisco IOS 15.0(2)SE6 is buggy'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-8310837134731272255</id><published>2014-06-06T17:52:00.001+02:00</published><updated>2014-06-06T17:54:40.008+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="cisco"/><title type='text'>Cisco hpm main process</title><content type='html'>&lt;p&gt;This process does not show up often in Cisco documentation but it can still do CPU hogs.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;%SYS-3-CPUHOG: Task is running for (2098)msecs, more than (2000)msecs (3/1),process = hpm main process.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The “pm” part of the name is for “Port Manager”, I have still not figured out what the first letter is for. You will find these processes at least on all Cisco 2960, Cisco 3560 and Cisco 3750 series switches.&lt;/p&gt;
&lt;p&gt;The hpm processes (there are three of them, at least on the Cisco 3750 series) handles events related to port changes. This includes link up/link down events, configuration changes etc. If you experience CPU related issues to this process you should check for flapping ports (cabling) first and then spanning-tree issues.&lt;/p&gt;
&lt;p&gt;Related commands:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;show platform pm counters&lt;/li&gt;
&lt;li&gt;debug platform pm hpm-events&lt;/li&gt;
&lt;/ul&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/8310837134731272255'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/8310837134731272255'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/06/cisco-hpm-main-process.html' title='Cisco hpm main process'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-7925964819802243954</id><published>2014-06-06T11:17:00.001+02:00</published><updated>2014-06-06T11:17:40.040+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="SSL"/><title type='text'>Error connecting with openssl s_client towards ADFS 3.0</title><content type='html'>&lt;p&gt;OpenSSL is your friend for whatever you want to do. But sometimes you get strange error messages like this one:&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;openssl s_client -connect 172.16.1.1:443&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;CONNECTED(00000003)&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;write:errno=104&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;openssl s_client -connect 172.16.1.1:443&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;CONNECTED(00000003)&lt;/p&gt;
&lt;p style=&quot;margin: 0px; font-size: 11px; font-family: Menlo;&quot;&gt;write:errno=54&lt;/p&gt;
&lt;p&gt;But what does it mean? The difference in the two outputs above is the version of OpenSSL used to connect to the ADFS server.&lt;/p&gt;
&lt;p&gt;The root cause of not being able to connect lies within the SSL protocol and how Microsoft chose to implement it on Windows 2012 R2. In the SSL specification you have something called &lt;a href=&quot;http://en.wikipedia.org/wiki/Server_Name_Indication&quot;&gt;SNI&lt;/a&gt; that let the client specify what host it want to connect to. Windows does not return a default certificate when SNI is not present and just tears down the connection. SNI is created to share an IP / port between several SSL certificates.&lt;/p&gt;
&lt;p&gt;There are two viable ways to solve this issue, depending how you want to proceed.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;You can run openssl with the parameter &quot;-servername xxx.com” to send the name of the virtual host you want to bind to.&lt;/li&gt;
&lt;li&gt;You can change the binding on the AD FS server to bind for an IP address instead of a host name. You can read more &lt;a href=&quot;http://social.msdn.microsoft.com/Forums/vstudio/en-US/d514b5a0-c01c-4ce4-b589-bca890e5921d/how-to-properly-setup-lb-probe-for-adfs-30-servers&quot;&gt;here&lt;/a&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If you are interested in SNI on Windows you can read more &lt;a href=&quot;http://blog.kloud.com.au/2013/04/18/an-overview-of-server-name-indication-sni-and-creating-an-iis-sni-web-ssl-binding-using-powershell-in-windows-server-2012/&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/7925964819802243954'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/7925964819802243954'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/06/error-connecting-with-openssl-sclient.html' title='Error connecting with openssl s_client towards ADFS 3.0'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-4449151161698572604</id><published>2014-05-24T12:34:00.001+02:00</published><updated>2014-05-24T12:34:53.439+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Fortinet"/><title type='text'>Fortigate SNMP interface counters is broken on most platforms</title><content type='html'>&lt;p&gt;&lt;a href=&quot;ftp://www.ietf.org/rfc/rfc1157.txt&quot;&gt;SNMP&lt;/a&gt; is one of the most important protocols for managing network equipment. All vendors have some kind of support for SNMP.&lt;/p&gt;
&lt;p&gt;The only thing worse than not supporting SNMP is actually a broken SNMP support. And here we have the Fortigate firewalls. By reading the technical documentation, &lt;a href=&quot;http://docs.fortinet.com/d/fortigate-fortios-handbook-hardware-acceleration-for-fortios-5.0&quot;&gt;FortiOS 5 hardware acceleration&lt;/a&gt; handbook you’ll find this:&lt;/p&gt;
&lt;div class=&quot;page&quot; title=&quot;Page 15&quot;&gt;
&lt;div class=&quot;section&quot;&gt;
&lt;div class=&quot;layoutArea&quot;&gt;
&lt;div class=&quot;column&quot;&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;span style=&quot;font-size: 10.000000pt; font-family: &#39;HelveticaNeueLTStd&#39;;&quot;&gt;Except for the NP6, network processors do not count offloaded packets, and offloaded packets are not logged by traffic logging and are not included in traffic statistics and traffic log reports. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style=&quot;font-size: 10.000000pt; font-family: &#39;HelveticaNeueLTStd&#39;;&quot;&gt;NP6 processors support per-session traffic and byte counters, Ethernet MIB matching, and reporting through messages resulting in traffic statistics and traffic log reporting.&lt;/span&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;Basically this means that the SNMP interface counters are incorrect for all traffic that is offloaded by the hardware (FortiASIC) except for on units with an NP6 processor. As of writing the only models with an NP6 processor are the 1500D and the 3700D. Most other models will, when a session can be hardware offloaded, report incorrect values.&lt;/p&gt;
&lt;p&gt;This is most important on VLAN interfaces as you can’t see where the traffic is flowing unless you have other equipment on your network that can report this correctly.&lt;/p&gt;
&lt;h3&gt;Other limitations with the Fortigate network processors&lt;/h3&gt;
&lt;p&gt;If you read the hardware accel guide thoroughly you’ll also find lots of other limitations on hardware accelerated traffic. Please note that what features are supported varies with the different network processors.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;No IPv6 support (all IPV6 packets are handled in software).&lt;/li&gt;
&lt;li&gt;Traffic must enter and exit on the same FortiASIC chip. Older units may have more than one NPU that are separated from each other. Newer units seems to have removed this limitation.&lt;/li&gt;
&lt;li&gt;Traffic shaping counters are separate for NPU and CPU leaving you with no good shaping.&lt;/li&gt;
&lt;li&gt;QoS is in general not supported on the NPU.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Why do we want hardare acceleration?&lt;/h3&gt;
&lt;p&gt;If you read the product specification you’ll see that a given model have some performance parameters, including firewall throughput, IPS troughput, antivirus throughput and IPSec throughput. All these numbers are based on maximum performance, that is hardware accelerated performance.&lt;/p&gt;
&lt;p&gt;As soon as packets are processed by the CPU the performance drops significantly. If you compare the numbers on the Fortigate 90D (with an NP4) and the Fortigate 100D (with a content processor instead of an NPU) you’ll see how the FortiASIC performs.&lt;/p&gt;
&lt;p&gt;On their mid-range and high-end products the performance is only met by using FortiASIC.&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/4449151161698572604'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/4449151161698572604'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/05/fortigate-snmp-interface-counters-is.html' title='Fortigate SNMP interface counters is broken on most platforms'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-2124337640432185933</id><published>2014-05-22T19:16:00.001+02:00</published><updated>2014-05-22T19:16:39.815+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Fortinet"/><title type='text'>Missing session table from FortiOS5</title><content type='html'>&lt;p&gt;If you have used Fortigate firewalls for a while you probably have found - and learned to love - the current session table. This tab disappeared with FortiOS5, leaving us only with the policy monitor, showing us only the top policies.&lt;/p&gt;
&lt;p&gt;A way to get around this is to either search for the session using the CLI or enter your browser into /system/widget/session_table on the firewall.&lt;/p&gt;
&lt;p&gt;Tested on FortiOS 5.0.7. This widget seems to work very slow on firewalls with lots of concurrent sessions.&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/2124337640432185933'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/2124337640432185933'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/05/missing-session-table-from-fortios5.html' title='Missing session table from FortiOS5'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-7265045660695849003</id><published>2014-05-19T13:32:00.001+02:00</published><updated>2014-05-19T13:32:15.858+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Fortinet"/><title type='text'>Upgrading a Fortigate firewall</title><content type='html'>&lt;p&gt;Even though Fortigate upgrades often are painless if you read the release notes I have seen that some times configuration objects disappear. As a last step of each upgrade you should log in to the CLI and see if any commands was rejected during the upgrade.&lt;/p&gt;
&lt;p class=&quot;codesnippet&quot;&gt;config global&lt;br /&gt;diagnose debug config-error-log read&lt;/p&gt;
&lt;p&gt;If you are using VDOMs this command has to be run from the global configuration.&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/7265045660695849003'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/7265045660695849003'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/05/upgrading-fortigate-firewall.html' title='Upgrading a Fortigate firewall'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-4135324335942036901</id><published>2014-05-10T14:55:00.001+02:00</published><updated>2014-05-10T15:55:03.377+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Meru"/><title type='text'>Configuring SNMP on a Meru controller</title><content type='html'>&lt;p&gt;Often you want to configure SNMP on a device in order to be able to poll it. On the Meru it is easy to configure SNMP, as it is available in both the GUI and CLI. The hard part is to start the SNMP daemon as it only can be done from the CLI.&lt;/p&gt;
&lt;p&gt;To add a new community from CLI go into configure mode (&quot;configure terminal” from the login menu) and type something like “snmp-server community mycommunity 0.0.0.0 ro”. You have to replace &lt;strong&gt;mycommunity&lt;/strong&gt; with your community and if you want to limit who can query the controller replace 0.0.0.0 with the IP address you want to query from.&lt;/p&gt;
&lt;p&gt;To start the SNMP daemon log in to the controller and type “snmp start”. This command is persistent on reload.&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/4135324335942036901'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/4135324335942036901'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/05/configuring-snmp-on-meru-controller.html' title='Configuring SNMP on a Meru controller'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-6847682767492224866</id><published>2014-04-28T19:10:00.003+02:00</published><updated>2014-04-28T19:10:44.550+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="development"/><category scheme="http://www.blogger.com/atom/ns#" term="web"/><title type='text'>PHP based CRUD generators</title><content type='html'>&lt;p&gt;I found an interesting article about different &lt;a href=&quot;http://logicpool.com/archives/297&quot;&gt;CRUD rapid application development platforms&lt;/a&gt;. So I started to dig some more into this. After reading a bit about them I ended up with two applications that I decided to try out. It is &lt;a href=&quot;http://bigprof.com/appgini/&quot;&gt;AppGeni&lt;/a&gt; and &lt;a href=&quot;http://scriptcase.net/&quot;&gt;ScriptCase&lt;/a&gt;. I also looked into a developer framework; &lt;a href=&quot;http://www.sencha.com/products/extjs/&quot;&gt;Sencha Ext JS&lt;/a&gt; with their &lt;a href=&quot;http://www.sencha.com/products/architect/&quot;&gt;Architect&lt;/a&gt; that I will compare with.&lt;/p&gt;
&lt;h1&gt;AppGeni&lt;/h1&gt;
&lt;p&gt;AppGeni is a Windows based application. You run it from your PC and model your database offline. When you are ready you can deploy it onto your existing web server. When you the first time run the code on the web server it will ask for how to connect to the database and then create / modify the tables that are needed. AppGeni also creates its own tables for users, groups and permissions. It will also extend existing tables with fields needed by the application.&lt;/p&gt;
&lt;p&gt;For its price AppGeni is a good CRUD generator for small datasets. I will not use it as an interface to existing databases because it also will extend / modify the database. There are no charting options in AppGeni, this can be a drawback depending on what you want to accomplish.&lt;/p&gt;
&lt;p&gt;The generated web page adapts to different screen sizes (phone, tablet, PC) and can be customized with the right knowledge.&lt;/p&gt;
&lt;h1&gt;ScriptCase&lt;/h1&gt;
&lt;p&gt;My first impression of this product was “poor support” and “bugs not fixed for several years&quot;, something I found by reading the forums and looking for other reviews. This scared me a little and I started to look into other tools. But I soon realized that ScriptCase has some unique features and seem to have lots of features. The biggest win for them is that they have a web based approach. All editing is done by using a web browser.&lt;/p&gt;
&lt;p&gt;In ScriptCase terms a project is a group of applications. An application is what you design and create. One application can be  a grid view, something to enter data or a report. You design and tailor this application to your specific needs. Within a project (and sometimes even in an application) you can connect to several databases to collect data.&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/6847682767492224866'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/6847682767492224866'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/04/php-based-crud-generators.html' title='PHP based CRUD generators'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-5418122857859028987</id><published>2014-04-28T19:10:00.001+02:00</published><updated>2014-04-28T19:10:19.656+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="email"/><title type='text'>Unibox MAC mail client review</title><content type='html'>&lt;p&gt;&lt;a href=&quot;http://www.uniboxapp.com&quot;&gt;Unibox&lt;/a&gt; is an email application for Mac OS X. As am really missing a good mail client to use I downloaded a trial to check it out.&lt;/p&gt;
&lt;p&gt;How it differs from “traditional” mail clients are that it focuses on the other party, not on the thread, subject or date. So my inbox(es) are sorted by date on the parties that I have sent or received emails from. With an unread count for that party.&lt;/p&gt;
&lt;p&gt;When I have selected a user I see all mails to/from that user sorted by date, as found in all my folders I have selected to be visible. From there I can select a thread that I want to review, and see all e-mails sent/received in that thread for all recipients.&lt;/p&gt;
&lt;p&gt;Here is a list of my thoughts from using the eval:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;It is not easy to move emails, for me they seem to stay in the inbox when I have read them. The way Unibox organizes emails make this work well.&lt;/li&gt;
&lt;li&gt;When I send an mail that recipient moves to the top of the list with the recipients unread-count. Over time I have lots of emails I have not responded to, making it hard to see when I have new emails that I should attend to now.&lt;/li&gt;
&lt;li&gt;Sent and deleted emails are shown for each user, it can take some time to scroll down to the unread emails.&lt;/li&gt;
&lt;li&gt;When working with multiple accounts Unibox does not try to use the best outgoing account. (Even when working on just one account it want to send new mails using the default account.)&lt;/li&gt;
&lt;li&gt;No calendar support built into Unibox.&lt;/li&gt;
&lt;li&gt;No address book support in Unibox, it uses only the Mac configured address books.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This is tested on build 189.&lt;/p&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/5418122857859028987'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/5418122857859028987'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/04/unibox-mac-mail-client-review.html' title='Unibox MAC mail client review'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-1251892860109703715</id><published>2014-04-13T21:51:00.003+02:00</published><updated>2014-04-13T21:51:34.874+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MAC"/><title type='text'>Problems with memory card on Garmin GPSes</title><content type='html'>I recently had a problem with a Garmin GPS (GPSMAP 60CSx) that crashed each time I updated the memory card with maps on my MAC. The root cause of the problem lies with the Mac writing some hidden folders into the memory card. It&#39;s some MAC metadata (._DS_Store, _.AppDouble, .Folders.)&lt;br /&gt;
&lt;br /&gt;
The best solution I have found (except using a Windows based computer) is a small tool called &lt;a href=&quot;http://www.zeroonetwenty.com/blueharvest/&quot; rel=&quot;nofollow&quot; target=&quot;_blank&quot;&gt;BlueHarvest&lt;/a&gt; that removes these folders for you.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/1251892860109703715'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/1251892860109703715'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/04/problems-with-memory-card-on-garmin.html' title='Problems with memory card on Garmin GPSes'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-116157842437631329</id><published>2014-02-26T15:54:00.000+01:00</published><updated>2014-02-26T15:54:00.420+01:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Linux"/><title type='text'>How to install Duplicity on CentOS</title><content type='html'>&lt;p&gt;&lt;a href=&quot;http://duplicity.nongnu.org/&quot; target=&quot;_blank&quot;&gt;Duplicity&lt;/a&gt; is a command line tool to back up your critical data. I don’t intend to explain how to use this tool here but just how to install it in three simple steps on CentOS 6.&lt;/p&gt;  &lt;p&gt;First you’ll have to conncet to EPEL:&lt;/p&gt;  &lt;p class=&quot;codesnippet&quot;&gt;yum -y install http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm&lt;/p&gt;  &lt;p&gt;Then you have to install some dependencies.&lt;/p&gt;  &lt;p class=&quot;codesnippet&quot;&gt;yum install gcc librsync-devel python-devel python-lockfile wget&lt;/p&gt;  &lt;p&gt;When this is done you can download the source file from the homepage, extract it and install it.&lt;/p&gt;  &lt;p class=&quot;codesnippet&quot;&gt;wget source.tar.gz tar xzf source.tar.gz cd to-new-dir ./setup.py install &lt;/p&gt;  &lt;p&gt;And you are done.&lt;/p&gt;  </content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/116157842437631329'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/116157842437631329'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/02/how-to-install-duplicity-on-centos.html' title='How to install Duplicity on CentOS'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-36141300.post-737545845614619640</id><published>2014-02-26T11:01:00.000+01:00</published><updated>2014-02-26T11:01:00.147+01:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Fortinet"/><title type='text'>OIDs for FortiOS 5</title><content type='html'>&lt;p&gt;A few years ago I wrote a note about &lt;a href=&quot;http://blog.helge.net/2008/06/oids-for-fortigtate-firewalls.html&quot;&gt;OIDs on FortiOS 3&lt;/a&gt;. Fortinet have changed their MIBs so here are the values that can be used to do SNMP monitoring on FortiOS 5.&lt;/p&gt;  &lt;p class=&quot;picture&quot;&gt;&lt;img alt=&quot;Speed gauge&quot; src=&quot;http://static.helge.net/images/clipart/400/21920991.thb.jpg&quot; width=&quot;350&quot; height=&quot;350&quot; /&gt;&lt;/p&gt;  &lt;p&gt;Here are the updated values:&lt;/p&gt;  &lt;table cellspacing=&quot;0&quot; cellpadding=&quot;2&quot; width=&quot;400&quot; border=&quot;1&quot;&gt;&lt;tbody&gt;     &lt;tr&gt;       &lt;td valign=&quot;top&quot; width=&quot;200&quot;&gt;CPU load&lt;/td&gt;        &lt;td valign=&quot;top&quot; width=&quot;200&quot;&gt;.1.3.6.1.4.1.12356.101.4.1.3.0&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td valign=&quot;top&quot; width=&quot;200&quot;&gt;Memory usage&lt;/td&gt;        &lt;td valign=&quot;top&quot; width=&quot;200&quot;&gt;.1.3.6.1.4.1.12356.101.4.1.4.0&lt;/td&gt;     &lt;/tr&gt;      &lt;tr&gt;       &lt;td valign=&quot;top&quot; width=&quot;200&quot;&gt;Number of current sessions&lt;/td&gt;        &lt;td valign=&quot;top&quot; width=&quot;200&quot;&gt;.1.3.6.1.4.1.12356.101.4.1.8.0&lt;/td&gt;     &lt;/tr&gt;   &lt;/tbody&gt;&lt;/table&gt;  &lt;div id=&quot;scid:0767317B-992E-4b12-91E0-4F059A8CECA8:fdd66d89-1142-4c52-9029-337ac74a7143&quot; class=&quot;wlWriterEditableSmartContent&quot; style=&quot;float: none; padding-bottom: 0px; padding-top: 0px; padding-left: 0px; margin: 0px; display: inline; padding-right: 0px&quot;&gt;Technorati Tags: &lt;a href=&quot;http://technorati.com/tags/Fortigate&quot; rel=&quot;tag&quot;&gt;Fortigate&lt;/a&gt;,&lt;a href=&quot;http://technorati.com/tags/FortiOS5&quot; rel=&quot;tag&quot;&gt;FortiOS5&lt;/a&gt;&lt;/div&gt;  </content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/737545845614619640'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36141300/posts/default/737545845614619640'/><link rel='alternate' type='text/html' href='http://blog.helge.net/2014/02/oids-for-fortios-5.html' title='OIDs for FortiOS 5'/><author><name>Helge Olav Helgsen</name><uri>http://www.blogger.com/profile/03275847410058577036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://www.helge.net/GPS/images/IMG_2987.jpg'/></author></entry></feed>