Step 1: Install ESXi PowerShell Module
Run PowerShell with elevated privilege (run as administrator)

PS D:\> Install-Module -Name PowerShellGet -Force
PS D:\> Install-Module -Name VMware.PowerCLI

Step 2: Changing the Windows PowerShell Script Execution Policy

PS D:\Set-ExecutionPolicy Unrestricted

Step 3: Download ESXi-Customizer-PS
Go to https://www.v-front.de/p/esxi-customizer-ps.html and download ESXi-Customizer-PS-v2.5.1.ps1 and move the script to D:\ (to ease our job)

Step 4: Run PowerShell script

PS D:\> .\ESXi-Customizer-PS-v2.5.1.ps1 -vft -load net55-r8168

Notes:
net55-r8168 is the package name from https://vibsdepot.v-front.de/wiki/index.php/List_of_currently_available_ESXi_packages containing Realtek NICs driver.
PS D:>.\ESXi-Customizer-PS-v2.5.1.ps1 -help for more customization

I was under impression that allowing icmp in the service policy will enable tracert to work. I was wrong. After scouting around I found below tweaks that will enable tracert to run correctly.

1. Set decrement TTL
ASA# configure terminal
ASA(config)# policy-map global_policy
ASA(config-pmap)# class class-default
ASA(config-pmap-c)# set connection decrement-ttl
ASA(config-pmap-c)# exit

2. Permit icmp control messages
ASA(config)# access-list inbound permit icmp any any time-exceeded
ASA(config)# access-list inbound permit icmp any any unreachable

3. Permit icmp connection, which you should already have šŸ˜€
ASA(config)# access-list outbound permit icmp any any

References:
http://www.cisco.com/c/en/us/td/docs/ios/sec_data_plane/configuration/guide/12_4/sec_data_plane_12_4_book/sec_fwall_icmp_insp.html

http://www.petenetlive.com/KB/Article/0000753.htm

Incoming search terms:

  • trtaceroute asa
  • allow trace through asa 5525

It seems that Ubuntu/Debian (or perhaps other distros as well) prefer IPv6 DNS records instead of IPv4 when applicable and some times this results in loss of connectivity or similar problems.
I ran into this issue today while trying to update an old VPS with apt-get/aptitude. Specifically, security.ubuntu.com was being resolved in an unreachable IPv6 address and I had to wait some minutes for timeout every time.
Fortunately, there is an easy fix for this; you just have to edit the file located at: /etc/gai.conf which is the configuration for getaddrinfo(). There you have to uncomment line ~54 which reads: ā€œprecedence ::ffff:0:0/96 100ā€³, and you are all set! (assuming that every other option is commented out by default as in my case).

gai

Reference: http://bruteforce.gr/make-apt-get-use-ipv4-instead-ipv6.html

Scenario:

Using Microsoft Windows built in VPN Client to connect to remote PPTP VPN server through Cisco ASA firewall.

Symptom:

Error 619

Solution:

In ASA Firewall, enter below command.
ASA-active#conf t
ASA-active(config)#policy-map global_policy
ASA-active(config-pmap)# class inspection_default
ASA-active(config-pmap-c)#inspect pptp
ASA-active(config-pmap-c)#exit
ASA-active(config)#access-list $Inbound_Interface_ACL permit gre $source_ip/network any
ASA-active(config)#access-list $Inbound_Interface_ACL permit permit tcp $source_ip/network any eq pptp

Common Troubleshooting in Windows VPN Client

1. Open VPN Properties window, go to Security tab.
2. Change “Type of VPN” to PPTP

Incoming search terms:

  • pptp through cisco vpn

Problem

Received error “Could not bind UDP syslog input to address /0.0.0.0:514, Failed to bind to: /0.0.0.0:514, Address already in use” when adding log input using UDP 514 (default syslog port).

Explanation

In UNIX/LINUX, assigned port 1024 and below require root privilege. Either you run graylog2 as root (not recommended) or follow below workaround.

Solution

1. Create new Syslog UDP inputs and listen to any port (ex: 5514).
2. Manipulate traffic using iptable:
iptables -t nat -A PREROUTING -i eth0 -p udp -m udp --dport 514 -j REDIRECT --to-ports 5514

Incoming search terms:

  • Failed to bind to udp 514 in graylog

Problem: Upgraded Insight Reporter from v3.2.0 to 3.4.0, existing traffic database show disconnected

insight1

Workaround/Solution:
1) To get Sybase JDBC Connector
Download JConnect from this linkĀ http://www.sybase.com/products/allproductsa-z/softwaredeveloperkit/jconnect
Extract and Install it in Insight Server

./setup.bin -i console

Go toĀ /opt/sybase/jConnect-7_0/classes and copyĀ conn4.jar and Ā jTDS3.jar into Cisco Insight directory (/home/user/Insight/apache-tomcat-6.0.20/webapps/insight/WEB-INF/lib/)
Restart tomcat

/etc/init.d/tomcat-user stop
/etc/init.d/tomcat-user start

2) To determine SCE CM db schema info
Go to your SCE CM server and execute cm file located atĀ /home/user/cm/bin

./cm version
CM CD Version 3.7.5 Build 105

insight2

Both Jar files can be downloaded from here:
http://dl.advanxer.com/stuff/Software/CiscoInsight/SybaseJDBC/

Since The Pirate Bay usingĀ magnetĀ link to initiate torrent download, i’m having issue with my Ī¼TorrentĀ running in Linkstation. Below is theĀ symptom:

Magnet links can be added but don’t start, they sit at 0 seeders and peers and display the null error mentioned previously in the event log:

JS error: [778] Unable to get value of the property '262': object is null or undefined

 

FIX
Copy magnet link from TPB, and paste into Ī¼Torrent.
Right click on the torrent list and select Properties
Look at the tracker section, add this line as additional tracker:

http://tracker.ccc.de:80/announce

Wait for few seconds, you will see some seeders and leechers coming to you

Source:
http://forums.buffalotech.com/t5/Storage/Bittorent-not-Working-after-Firmware-update/m-p/103520/highlight/true#M49903