<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom="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" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-3423420718518803005</atom:id><lastBuildDate>Mon, 09 Sep 2024 21:39:13 +0000</lastBuildDate><category>Linux</category><category>Networking</category><category>Cisco</category><category>General</category><category>Loadbalancing</category><category>debian</category><category>CentOS</category><category>ssh</category><category>wireshark</category><category>client</category><category>desktop</category><category>dns</category><category>gnome</category><category>install</category><category>jessie</category><category>BGP</category><category>EX</category><category>FreeDesktop.org</category><category>HP-UX</category><category>IS-IS</category><category>Juniper</category><category>Juniper ethernet</category><category>Junos</category><category>console</category><category>conversations</category><category>ddns</category><category>editcap</category><category>email</category><category>encryption</category><category>error</category><category>esxi</category><category>evolution</category><category>exchange</category><category>f5 plugin</category><category>freeBSD</category><category>gzrecover</category><category>gzrt</category><category>inodes</category><category>kde</category><category>keepalive</category><category>macos</category><category>menu</category><category>office365</category><category>ospf</category><category>pcap</category><category>qnap</category><category>search</category><category>search-domain</category><category>searchdomain</category><category>serial</category><category>tcpprep</category><category>tcpreplay</category><category>tcprewrite</category><category>tools</category><category>tunnel</category><category>vim-cmd</category><category>virtualization</category><category>wheezy</category><title>IT journal</title><description>YAIJ - Yet another IT journal</description><link>http://yy27.blogspot.com/</link><managingEditor>noreply@blogger.com (Valentin)</managingEditor><generator>Blogger</generator><openSearch:totalResults>30</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-5658993758642774749</guid><pubDate>Wed, 26 Jul 2017 09:55:00 +0000</pubDate><atom:updated>2017-07-26T12:53:17.442+02:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">f5 plugin</category><category domain="http://www.blogger.com/atom/ns#">wireshark</category><title>Install f5 wireshark plugin f5ethtrailer.so on MacOS</title><atom:summary type="text">The documentation I could find on F5 devcentral about installing the f5 wireshark plugin goes about compiling wireshark from sources, patching the code to include the f5 plugin, etc.
After downloading the 2.2.0 version I could see that the plugin is already in binary format, namely f5ethtrailer.so (this goes for all platforms, except windows where this is a dll file).

To install the plugin in </atom:summary><link>http://yy27.blogspot.com/2017/07/install-f5-f5ethtrailerso-wireshark.html</link><author>noreply@blogger.com (Valentin)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjZE9uSkFQxNFm42Jk_e8j9IK27xfEuPM7_R89ay1M9XcUoyEtUsWT0yXCa8_pjCoUMjNjbYfZD4AIPUS9Dcceye3dtgDFM725y4jnSkh1eRi2xPaPuEeTiql5MjWKD3SRlXKvycJwaYJ4/s72-c/Screen+Shot+2017-07-26+at+11.50.27.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-5748665156305134470</guid><pubDate>Tue, 18 Jul 2017 23:44:00 +0000</pubDate><atom:updated>2017-07-19T01:51:30.838+02:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">error</category><category domain="http://www.blogger.com/atom/ns#">EX</category><category domain="http://www.blogger.com/atom/ns#">freeBSD</category><category domain="http://www.blogger.com/atom/ns#">inodes</category><category domain="http://www.blogger.com/atom/ns#">Juniper</category><category domain="http://www.blogger.com/atom/ns#">Junos</category><title>Juniper &quot;error: Could not create temporary directory&quot;</title><atom:summary type="text">Got into an issue a couple of days ago on a Junos EX virtual chassis where the following was being reporded

&gt; show system snapshot media internal member 0
fpc0:
--------------------------------------------------------------------------
error: Could not create temporary directory


The command tries to create a temporary directory into the /tmp filesystem and it fails.
Going to the shell prompt </atom:summary><link>http://yy27.blogspot.com/2017/07/juniper-ex-error-could-not-create.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-6902301838189392621</guid><pubDate>Wed, 14 Jun 2017 09:22:00 +0000</pubDate><atom:updated>2023-09-29T09:34:04.642+02:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">dns</category><category domain="http://www.blogger.com/atom/ns#">General</category><category domain="http://www.blogger.com/atom/ns#">macos</category><category domain="http://www.blogger.com/atom/ns#">search-domain</category><category domain="http://www.blogger.com/atom/ns#">searchdomain</category><title>MacOS append search-domain</title><atom:summary type="text">I recently started using a Mac laptop (with MacOS Sierra) for work and one thing soon saw was that the search-domains were not appended when trying to use utilities such as ping or ssh (tough the configuration in the network preferences lists domain.com in the list of search-domains).

So, saying I have host1.domain.com using the following:
ping host1 would not resolve host1 (no search-domain </atom:summary><link>http://yy27.blogspot.com/2017/06/macos-append-search-domain.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-3685451414647879651</guid><pubDate>Mon, 16 Jan 2017 12:57:00 +0000</pubDate><atom:updated>2017-06-14T11:23:28.786+02:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">ddns</category><category domain="http://www.blogger.com/atom/ns#">dns</category><category domain="http://www.blogger.com/atom/ns#">General</category><category domain="http://www.blogger.com/atom/ns#">Linux</category><category domain="http://www.blogger.com/atom/ns#">qnap</category><title>DDNS and QNAP NAS</title><atom:summary type="text">I was looking recently to allow remote access into my home QNAP NAS from remote locations.
My IP address at home is dynamic so I needed a DDNS provider and some port forwarding on the home router.
My setup at home is simple. My internet connection is over a DSL line. I have a DSL router from the ISP serving as an Wifi access point for my devices at home. It also has 4 ethernet ports and to one of</atom:summary><link>http://yy27.blogspot.com/2017/01/ddns-and-qnap.html</link><author>noreply@blogger.com (Valentin)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj8JhqU0YWgvw26cakK57Oy49iDrDUwStf7ZBecg5YVdyIcKNXSy8cFSpTVx1gCPGZIPXOAB8aD4RDjp0xikbYzNv2jRTPLhEY2AluRo8BPS8AAGzChVv72t_qCC8qLDr57a4Z_fLQK_Pw/s72-c/ddns_qnap.PNG" height="72" width="72"/><thr:total>4</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-8881515963155335592</guid><pubDate>Sun, 08 Jan 2017 19:51:00 +0000</pubDate><atom:updated>2017-01-08T22:22:46.548+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">IS-IS</category><category domain="http://www.blogger.com/atom/ns#">Networking</category><title>IS-IS notes</title><atom:summary type="text">General: 
- routing protocol for ISO CLNP (Connectionless Network Protocol)
- NET (Network Entity Title) required by configuration (L3 address) Has different formats. One practical is below:
&amp;nbsp;&amp;nbsp; Area (1-13 bytes)| System ID (6 bytes) | Selector (1 byte) (eg. 47.000|1921.6810.0001|00)
&amp;nbsp;&amp;nbsp; Selector is 00 in a NET. The NET must begin with one octet (eg 47) and end with one octed (</atom:summary><link>http://yy27.blogspot.com/2017/01/general-routing-protocol-for-iso-clnp.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-204458963994991255</guid><pubDate>Tue, 03 Jan 2017 22:47:00 +0000</pubDate><atom:updated>2017-01-03T23:47:23.631+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">BGP</category><category domain="http://www.blogger.com/atom/ns#">Networking</category><title>BGP notes</title><atom:summary type="text">Neighbor states:

Idle: all connections are refused
Connect: wait for TCP to establish
Active: initiates the TCP connections
OpenSent: Local waits for Open message from peer. After receiving open, if no errors BGP sends keepalive
OpenConfirm: BGP waits for keepalive or notification
Established: Can exchange update, notification and keepalive

Message types:

Open: sent when TCP 3way is complete. </atom:summary><link>http://yy27.blogspot.com/2017/01/bgp-notes.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-7582787694251865746</guid><pubDate>Tue, 03 Jan 2017 16:10:00 +0000</pubDate><atom:updated>2017-01-03T23:49:05.459+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Networking</category><category domain="http://www.blogger.com/atom/ns#">ospf</category><title>OSPF notes</title><atom:summary type="text">Packet types:
Hello (type1): used to discover neighbors, build and maintain adjacencies
DBD(type2): database description packets. These are a summary of the topological database. Detects MTU mismatches (fragmentation is not allowed). Have bits I (start of DBD), M (more ackets DB), MS(master/slave used to decides who starts sending DBD first)
LSR(type3): link state request. Request specific link </atom:summary><link>http://yy27.blogspot.com/2017/01/ospf-notes.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-5088100233971606566</guid><pubDate>Wed, 14 Dec 2016 13:09:00 +0000</pubDate><atom:updated>2016-12-15T14:02:00.840+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">debian</category><category domain="http://www.blogger.com/atom/ns#">desktop</category><category domain="http://www.blogger.com/atom/ns#">Linux</category><category domain="http://www.blogger.com/atom/ns#">search</category><title>Catfish fails to update database</title><atom:summary type="text">I have just tried&amp;nbsp;Catfish&amp;nbsp;for local files search. I am using it (at time of writing version 1.2.2) with Debian Jessie &amp;nbsp;and Xfce desktop.
Every time I opened catfish I was prompted to update the database as it was never updated. I was updating this with administrative rights, but after closing and opening the application the same message was displayed.







From the message prompt</atom:summary><link>http://yy27.blogspot.com/2016/12/catfish-fails-to-update-database-in.html</link><author>noreply@blogger.com (Valentin)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhrvH3JYMqBPGbHIlQOtaK7GSWbe8Ge_6DfTUkJ56hVh05WVgCmNjyuffcRxHOMaX4XF1jRVGjFBWy6ws90LvnHAOaZfgep-Etx8zOcfujcejTFDhnz5tYKquozQfUSaixoB1k3XdzTiQs/s72-c/catfish.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-3826122661186439683</guid><pubDate>Fri, 11 Dec 2015 16:24:00 +0000</pubDate><atom:updated>2015-12-11T17:30:10.637+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">esxi</category><category domain="http://www.blogger.com/atom/ns#">Linux</category><category domain="http://www.blogger.com/atom/ns#">ssh</category><category domain="http://www.blogger.com/atom/ns#">vim-cmd</category><category domain="http://www.blogger.com/atom/ns#">virtualization</category><title>cli remote management of ESXi virtual machines over ssh</title><atom:summary type="text">One of the ways to manage ESXi virtual machines is through vim-cmd commands. You can look at a quick tutorial of the command here.

Let&#39;s say there are a multitude of ESXi servers in your environment and you&#39;d like to manage some virtual machines through cli.
One way to do this is to run vim-cmd commands over ssh. For example, I have 2 ESXis named in the example esxi1 and esxi2. On both of them I</atom:summary><link>http://yy27.blogspot.com/2015/12/cli-remote-management-of-esxi-virtual.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-7877509838846573288</guid><pubDate>Thu, 13 Aug 2015 10:05:00 +0000</pubDate><atom:updated>2015-12-10T16:34:17.924+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">editcap</category><category domain="http://www.blogger.com/atom/ns#">Juniper ethernet</category><category domain="http://www.blogger.com/atom/ns#">pcap</category><category domain="http://www.blogger.com/atom/ns#">wireshark</category><title>How to remove Juniper ethernet encapsulation from pcap packet capture </title><atom:summary type="text">
When capturing packets on a Junos device, the output packet capture will include a Juniper ethernet header.
Example of such capture:


tcpdump -c1 -nvvr capture.pcap

reading from file JTAC.pcap, link-type JUNIPER_ETHER (Juniper Ethernet)

14:58:06.569634

&amp;nbsp;Juniper PCAP Flags [Ext], PCAP Extension(s) total length 16

&amp;nbsp; &amp;nbsp;Device Media Type Extension TLV #3, length 1, value Ethernet </atom:summary><link>http://yy27.blogspot.com/2015/08/how-to-remove-juniper-ethernet.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-903007266561309081</guid><pubDate>Thu, 14 May 2015 13:48:00 +0000</pubDate><atom:updated>2015-12-10T16:39:05.668+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">gzrecover</category><category domain="http://www.blogger.com/atom/ns#">gzrt</category><category domain="http://www.blogger.com/atom/ns#">Linux</category><category domain="http://www.blogger.com/atom/ns#">tools</category><title>Recovering corrupted gzip files.  gzip: compressed_file.gz:  unexpected end of file</title><atom:summary type="text">

A tool to recover gzip corrupted compressed files is gzrecover. This comes with in the recovery toolkit package gzrt.


$gzip -d compressed_file.gz
gzip: compressed_file.gz: unexpected end of file

$file compressed_file.gz
compressed_file.gz: gzip compressed data, from Unix

$gzrecover compressed_file.gz
$ls compressed_file*
compressed_file.gz compressed_file.recovered

</atom:summary><link>http://yy27.blogspot.com/2015/05/recovering-corrupted-gzip-files-gzip.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-4012764929809482401</guid><pubDate>Tue, 12 May 2015 14:03:00 +0000</pubDate><atom:updated>2015-12-10T17:19:35.199+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">client</category><category domain="http://www.blogger.com/atom/ns#">debian</category><category domain="http://www.blogger.com/atom/ns#">encryption</category><category domain="http://www.blogger.com/atom/ns#">Linux</category><category domain="http://www.blogger.com/atom/ns#">Networking</category><category domain="http://www.blogger.com/atom/ns#">ssh</category><category domain="http://www.blogger.com/atom/ns#">tunnel</category><title>ssh tunnels set up and port forwarding</title><atom:summary type="text">
SSH tunnels allow you to forward a local TCP port to a remote machine and vice versa. The tunnel option is available in many ssh clients. I will give the example here on how to create SSH tunnels with&amp;nbsp;putty&amp;nbsp;and the openssh-client.
I will consider in the below that we want to access the SERVER on port 80 (http server).


Scenario 1. SSH tunnel setup with local port forwarding.





The </atom:summary><link>http://yy27.blogspot.com/2015/05/ssh-tunnels-set-up-and-port-forwarding.html</link><author>noreply@blogger.com (Valentin)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh6ks_1RjScB9jv8UT20xDmEUQBKhZr-yfcQx8tTYt__aD5dAGCFrcHLnplKlFo3rROkzlNgaO_dK4Zd6VOuYX0hcNgqCaRiJVFXRQCYUysf_iSqD57wXfHzUOc_uHCfsc6pbX0fI4lMqM/s72-c/scenario1.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-7489154983391870170</guid><pubDate>Thu, 07 May 2015 13:15:00 +0000</pubDate><atom:updated>2015-12-10T17:23:33.766+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">desktop</category><category domain="http://www.blogger.com/atom/ns#">FreeDesktop.org</category><category domain="http://www.blogger.com/atom/ns#">gnome</category><category domain="http://www.blogger.com/atom/ns#">install</category><category domain="http://www.blogger.com/atom/ns#">jessie</category><category domain="http://www.blogger.com/atom/ns#">kde</category><category domain="http://www.blogger.com/atom/ns#">Linux</category><category domain="http://www.blogger.com/atom/ns#">menu</category><title>Linux gnome add menu and desktop entry for applications</title><atom:summary type="text">

Users can create shortcuts for an application to appear in menus, desktop, &amp;nbsp;etc. by creating a .desktop file. This desktop file contains a listings of configuration for the application. In order for your desktop environment to &quot;see&quot; this file, this .desktop file will have to be placed either in /usr/share/applications - for system wide applications - or in ~/.local/share/applications - if </atom:summary><link>http://yy27.blogspot.com/2015/05/linux-add-menu-and-desktop-entry-for.html</link><author>noreply@blogger.com (Valentin)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-453_kRe5bpJJLZOP19Rl8MZgvgAVf30XBQR2Lf5cBLpZHAg4KPz_17GuakTwzyfACWn0kUVy5DEV308aB_XN73I-3tCZbiZF2cnH5RGfKE03Fi9iFU1qU-T96Vr_D9pTBXCMqOsgzfk/s72-c/TinyCA.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-2778710014109456434</guid><pubDate>Fri, 01 May 2015 11:59:00 +0000</pubDate><atom:updated>2015-12-10T17:32:02.687+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">client</category><category domain="http://www.blogger.com/atom/ns#">debian</category><category domain="http://www.blogger.com/atom/ns#">email</category><category domain="http://www.blogger.com/atom/ns#">evolution</category><category domain="http://www.blogger.com/atom/ns#">exchange</category><category domain="http://www.blogger.com/atom/ns#">gnome</category><category domain="http://www.blogger.com/atom/ns#">jessie</category><category domain="http://www.blogger.com/atom/ns#">Linux</category><category domain="http://www.blogger.com/atom/ns#">office365</category><title>Connect Evolution email client to Exchange office365 server</title><atom:summary type="text">


Evolution&amp;nbsp;is a personal information management application that provides integrated mail, calendaring and address book functionality.

To connect to office365 exchange you will need the evolution program and the evolution-ews plugin.





Installation:
% sudo apt-get install evolution evolution-ews

Account setup:

1. Obtain the information about your domain&#39;s office365 servers.
To find </atom:summary><link>http://yy27.blogspot.com/2015/05/connect-evolution-email-client-to.html</link><author>noreply@blogger.com (Valentin)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgdIBZ-Oqo_oCiAoaiPJNAaCfYt6IUzhPAvSfsvdJwdaFNQ0SMS1YwpjwDG6EUI3Vb4Frl5qR_FYaxeztFuTvZ_DUpf0RH6GbJtSrE_re0TwIEUQiFL_o4ixdEvKxOFIdMUYpNCnnWOLRQ/s72-c/Identity.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-7941632984548306269</guid><pubDate>Wed, 11 Feb 2015 21:24:00 +0000</pubDate><atom:updated>2015-12-10T17:39:13.484+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">console</category><category domain="http://www.blogger.com/atom/ns#">debian</category><category domain="http://www.blogger.com/atom/ns#">install</category><category domain="http://www.blogger.com/atom/ns#">Linux</category><category domain="http://www.blogger.com/atom/ns#">serial</category><category domain="http://www.blogger.com/atom/ns#">wheezy</category><title>Installing Debian wheezy from USB over serial console </title><atom:summary type="text">

I wanted to install Debian wheezy on a machine without a video card and no CDROM.
I had a 1GB USB and I tried initially the easy way, as described in https://www.debian.org/releases/stable/amd64/ch04s03.html.en#usb-copy-isohybrid by just copying the cd image to my /dev/sda (USB stick) but I did not got any output on the console.

I copied the iso file to another linux machine, mounted it as a </atom:summary><link>http://yy27.blogspot.com/2015/02/installing-debian-wheezy-from-usb-over.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-1825996534869466738</guid><pubDate>Tue, 03 Feb 2015 18:39:00 +0000</pubDate><atom:updated>2015-02-03T19:39:13.062+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">conversations</category><category domain="http://www.blogger.com/atom/ns#">Networking</category><category domain="http://www.blogger.com/atom/ns#">wireshark</category><title>How to identify top traffic speakers with wireshark conversations</title><atom:summary type="text">
Among other very useful and interesting things that wireshark can show in a packet capture, it can also display the top traffic conversations based on various criteria such as IP addresses, L2 ethernet addresses, IPv6 address or L4 information.


The conversation list is available from the Statistics -&amp;gt; Conversations menu.





Below an example taken showing the top bps rate (B-&amp;gt;A </atom:summary><link>http://yy27.blogspot.com/2015/02/how-to-identify-top-traffic-speakers.html</link><author>noreply@blogger.com (Valentin)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh0d88kN1BcLt1djEmYBp9BI1uuLk1Kw6sYXohKAK7-_PD8C2UYPxF5PZHrjuGp-_UpCJBLU5lDwe3996mWlMY7B32_cBfglLr5KMJzUG4sk-F0Vu_EhphwZhGAherFWiY_wvRiygvtWJc/s72-c/wireshark_conversation.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-5113988452531988006</guid><pubDate>Mon, 02 Feb 2015 15:34:00 +0000</pubDate><atom:updated>2015-12-10T17:54:05.288+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">CentOS</category><category domain="http://www.blogger.com/atom/ns#">keepalive</category><category domain="http://www.blogger.com/atom/ns#">Linux</category><category domain="http://www.blogger.com/atom/ns#">ssh</category><title>ssh keepalives and tcp keepalives in openssh</title><atom:summary type="text">
The SSH connection can be kept alive either with SSH keepalive packets (encrypted) or with TCP keepalive packets. This allows also to detect hanging sessions and disconnect the hanging client/server when a connection has become inactive.

On a open SSH server, to control the SSH keepalive packets the parameters are:
ClientAliveCountMax 3 (default)
ClientAliveInterval 0 (default) - means the SSH </atom:summary><link>http://yy27.blogspot.com/2015/02/open-ssh-keepalive.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-8766689685001433553</guid><pubDate>Thu, 29 Jan 2015 08:57:00 +0000</pubDate><atom:updated>2015-12-11T12:25:31.555+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Linux</category><category domain="http://www.blogger.com/atom/ns#">Networking</category><category domain="http://www.blogger.com/atom/ns#">tcpprep</category><category domain="http://www.blogger.com/atom/ns#">tcpreplay</category><category domain="http://www.blogger.com/atom/ns#">tcprewrite</category><title>Replaying packets with tcpreplay</title><atom:summary type="text">
Tcpreplay&amp;nbsp;is a suite of tools that allows editing and replaying previously captured traffic in libpcap format. This can come handy in many situations, one common use is traffic pattern based behavior re-creation in a lab environment.
Tcpreplay suite comes with the following tools:

tcpprep - multi-pass pcap file pre-processor which determines packets as client or server and creates cache </atom:summary><link>http://yy27.blogspot.com/2015/01/replaying-packets-with-tcpreplay.html</link><author>noreply@blogger.com (Valentin)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO95DeVVFEURonzgN7VOqsthHLj0zPY3_1opQ3hBqpA7WC7l7RcfF7LkJXxZ9i1M8BARJpyfWynzVdIFQ8t1CArbBpMV8xdm1ixxh-KFyijORxKjUP71pAuvd6UQHQMJ_63Alfc6wgydQ/s72-c/1.gif" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-8004796910516161718</guid><pubDate>Wed, 22 Jul 2009 15:27:00 +0000</pubDate><atom:updated>2015-12-11T14:21:40.129+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Cisco</category><category domain="http://www.blogger.com/atom/ns#">Loadbalancing</category><category domain="http://www.blogger.com/atom/ns#">Networking</category><title>How to delete files from CSS11501</title><atom:summary type="text">The scope of this post is to show how to delete archived files on a Cisco CSS11501. In order to delete other files (core dumps, logs, etc) the procedure is similar, you just need to know what you want to delete.
In order to manipulate the files we need to go to debug mode:

CSS11501# llama

Then the ap_file command provides the &quot;File commands using Complete pathnames&quot;. To delete the </atom:summary><link>http://yy27.blogspot.com/2009/07/how-to-delete-files-from-css11501.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-5155514605582756995</guid><pubDate>Sat, 30 May 2009 00:33:00 +0000</pubDate><atom:updated>2015-12-11T15:14:49.402+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">CentOS</category><category domain="http://www.blogger.com/atom/ns#">General</category><category domain="http://www.blogger.com/atom/ns#">Linux</category><title>mdadm tips on Linux software RAID</title><atom:summary type="text">
mdadm is a tool for managing, creating and reporting on Linux software RAID arrays.

I will describe some tips which I found useful at the moment.
Improve RAID1 re-sync time with write-intent bitmap
The RAID driver writes out periodically bitmap information recording which areas of the RAID component have been modified since the RAID array was last in sync.

If, for example one of two members of</atom:summary><link>http://yy27.blogspot.com/2009/05/mdadm-tips-on-linux-software-raid.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-9088490872251062762</guid><pubDate>Mon, 04 May 2009 15:17:00 +0000</pubDate><atom:updated>2015-12-11T15:19:10.326+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Cisco</category><category domain="http://www.blogger.com/atom/ns#">Loadbalancing</category><category domain="http://www.blogger.com/atom/ns#">Networking</category><title>Cisco CSS11501 source groups and ACL</title><atom:summary type="text">
Few days ago I had to reconfigure a running CSS 11501 loadbalancer from an existing configuration in which traffic initiated from some services running in one VLAN towards any destination was source NAT-ed to a selective NAT which was based on the destination IP address.
What I wanted to do is almost exactly to what is described in this official Cisco document with the difference that I had more</atom:summary><link>http://yy27.blogspot.com/2009/05/css11500-source-groups-and-acl.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-7804423228612111307</guid><pubDate>Mon, 16 Mar 2009 13:30:00 +0000</pubDate><atom:updated>2015-12-11T15:25:48.689+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Cisco</category><category domain="http://www.blogger.com/atom/ns#">Loadbalancing</category><category domain="http://www.blogger.com/atom/ns#">Networking</category><title>VRRP master/master issue on CSS 11501 with 3550</title><atom:summary type="text">
In the picture illustrated in which two Cisco CSS 11501 Loadbalancers were providing a redundant setup with fate sharing, the route from the &quot;Servers&quot; networks towards the client network was provided through an IP setup on a redundant interface shared by the 2 Loadbalancers.

The VRRP announcements for the virtual routers holding redundant interfaces on vlans A,B between the two loadbalancers </atom:summary><link>http://yy27.blogspot.com/2009/03/vrrp-mastermaster-issue-on-css-11501.html</link><author>noreply@blogger.com (Valentin)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi2hgLxuZBosLakyNQnp03DK3t7SSIPyHlaWwxBSBLgykAxjEOeWaPEZeDAXZlFYMuF59a5TAHTnvQO54pMmkLQNv0WGic-v7KFDNnnsma5GQzDA1G4vdHnijrZg1CxXRy2CM87NptK8Hc/s72-c/topology.bmp" height="72" width="72"/><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-8777273492690920699</guid><pubDate>Sun, 22 Feb 2009 16:05:00 +0000</pubDate><atom:updated>2015-12-11T15:30:26.575+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">HP-UX</category><title>HP-UX  ephemeral port range for TCP/UDP connections</title><atom:summary type="text">
For HP-UX (click here for latest release) you can tune the UDP local ephemeral port range separately from the TCP local ephemeral port range.

In a previous post it was shown how to alter/view the ephemeral port range for a Linux system.

To follow up the example from my Linux post in order to set on HP-UX the local port range from 15000 till 61000 we can use the ndd utility for the change on </atom:summary><link>http://yy27.blogspot.com/2009/02/hp-ux-ephemeral-port-range-for-tcpudp.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-8924451560649413942</guid><pubDate>Thu, 05 Feb 2009 23:08:00 +0000</pubDate><atom:updated>2015-12-11T15:32:32.883+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">General</category><category domain="http://www.blogger.com/atom/ns#">Linux</category><title>Linux ephemeral port range for TCP/UDP connections over IPv4</title><atom:summary type="text">
The range of ephemeral ports a client program can use (unless otherwise specified by the program) on modern Linux OS distributions by default is from 32768 till 61000 (for systems with more than 128 MB RAM) and from 1024 till 4999 (or even less) for systems with less than 128MB of RAM. This range is defined in the kernel parameter /proc/sys/net/ipv4/ip_local_port_range and it affects both TCP as</atom:summary><link>http://yy27.blogspot.com/2009/02/linux-ephemeral-port-range-for-tcpudp.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-3423420718518803005.post-2447821491853446048</guid><pubDate>Tue, 03 Feb 2009 11:21:00 +0000</pubDate><atom:updated>2015-02-02T20:59:47.764+01:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Cisco</category><category domain="http://www.blogger.com/atom/ns#">Loadbalancing</category><category domain="http://www.blogger.com/atom/ns#">Networking</category><title>Cisco CSS 11500 series internal services</title><atom:summary type="text">
By default the Cisco CSS 11501 series loadbalancers will create an implicit internal service to check the availability of the gateways for its static defined routes.
This internal service monitors the availability of the route which goes through a specific gateway by sending ICMP keepalives to that gateway. In that way if the internal service is in &quot;Alive&quot; state, the route for which the internal</atom:summary><link>http://yy27.blogspot.com/2009/02/cisco-css-11500-series-internal.html</link><author>noreply@blogger.com (Valentin)</author><thr:total>0</thr:total></item></channel></rss>