I passed CCNP Route 642-813 in January before the exam changed thus completing all three exams. Route was the most challenging of the three exams for me because I am now taking the lead on projects that involve routing, which is part of why I wanted to peruse the certification. Exciting times and I’ve started to take a peek at the CCIE 5.0 exam.
I passed the CCNP TSHOOT exam yesterday and I have to say that this exam was my favorite out of all the Cisco ones that I have taken so far. The exam format of solving trouble tickets was a welcome change that I felt was really applicable to an Engineer’s daily tasks.
The official Cisco Press TSHOOT book, Bull’s Eye exam preparation strategies, and building the official lab topology out in GNS3 helped me prepare for the exam. I did update my GNS3 version to 1.0+ and needed to convert my project files to the new 1.0+ JSON format with gns3-converter.
I had a hard time finding details on how to setup port forwarding with Private Internet Access so I wanted to share the details on how to set it up on a Debian system. The following directions will help you find your local IP access, request a port from Private Internet Access for Port Forwarding, configure your local firewall to allow inbound connections, and confirm that your application is listening on the specified port.
Here is a overview of the network topology with a remote user requesting to talk to your machine at home over the VPN connection to Private Internet Access with Port Forwarding setup on port 12345.
- Obtain the VPN IP address by looking at the IP addresses in ifconfig. On my machine, the interface is a tun0 interface.
- Create a unique client ID with head -n 100 /dev/urandom | md5sum | tr -d ” -” > ~/.pia_client_id
- Request a port for port forwarding with curl -d “user=your_username&pass=your_password&client_id=$(cat ~/.pia_client_id)&local_ip=10.xxx.xxx.xxx” https://www.privateinternetaccess.com/vpninfo/port_forward_assignment
- Modify firewall to allow inbound traffic with sudo iptables -A INPUT -p tcp –dport 12345:12345 -j ACCEPT
- Set your application to listen on port 12345
- Confirm that your application is listening with sudo netstat -anp | grep 12345
I was at the Advanced Light Source User Meeting as a representative of LBLnet today talking about the architecture of the Science DMZ to enable big data transfers across the WAN. We had an elegant poster that showed how the DMZ architecture fits into the enterprise design. There are still groups that are saving large data sets to hard drives and shipping them to the destination location rather than attempting to utilize the network and we want to help change that paradigm.
Credit for the majority of the design goes to my co-worker Michael at smitasin.com.
Good news as the following layer 2 security features were added in 13.2 release of Junos:
We’re still running the recommended 12.3R6.6 in production at this time so we’re going to have to test the 13.2 features in the lab before putting them on production systems.
For the longest time I would never advocate Poweline Ethernet as a viable solution for getting connectivity into a troublesome area. I felt that the technology was prone to interference and therefore an unreliable solution that could never deliver a consistent connection.
After a few failed attempts to trace Cat5 cable into the garage in my San Francisco apartment in order to connect two pairs to get 100MBPS connectivity between the front and back of the apartment, I decided to try out a Powerline Ethernet solution. I picked up a pair of TP-LINK 200Mbps units and was surprised at the setup procedure. It was fairly easy and I had the units connected in under five minutes.
Of course I wanted to test performance so I started to graph latency to the wireless router on the other side of the apartment.
An iperf test also showed a solid 28.9 Mbits/second transfer rate.
C:\tools>iperf -c 10.10.1.27 -p 200 -t 120 ------------------------------------------------------------ Client connecting to 10.10.1.27, TCP port 200 TCP window size: 8.00 KByte (default) ------------------------------------------------------------  local 10.10.1.60 port 58742 connected with 10.10.1.27 port 200 [ ID] Interval Transfer Bandwidth  0.0-120.0 sec 413 MBytes 28.9 Mbits/sec C:\tools>
Overall I’ve been impressed by the performance and now have Ethernet extended to the other half of the apartment. Not bad for a $30 connectivity solution.
EX-2200 and EX-3300 series switches running 12.3R3.4 have a bug where Receiver signal average optical power values don’t display correctly. The recommended version that contains a fix for this bug is12.3R4-S1. We’ve tested this update on a few switches and it had resolved the bug.
user@j33s> show interfaces diagnostics optics ge-0/1/0 Physical interface: ge-0/1/0 Laser bias current : 5.566 mA Laser output power : 0.2820 mW / -5.50 dBm Module temperature : 31 degrees C / 88 degrees F Module voltage : 3.3680 V Receiver signal average optical power : 0.0000 mW / - Inf dBm
user@j33> show interfaces diagnostics optics ge-0/1/0 Physical interface: ge-0/1/0 Laser bias current : 5.508 mA Laser output power : 0.2810 mW / -5.51 dBm Module temperature : 31 degrees C / 88 degrees F Module voltage : 3.3680 V Receiver signal average optical power : 0.2811 mW / -5.51 dBm