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

Incoming search terms:

  • install Net55-r8168 on esxi 6 5
  • https://advanxer com/blog/2017/10/adding-realtek-8168811184118118-based-nics-to-esxi-6-5/
  • 8168/8111
  • strange9op
  • https://yandex ru/clck/jsredir?from=yandex ru;search;web;;&text=&etext=1838 EM7JH_yWdZ14P83XktAmhGryOtKRSW-ebj34z3vvmEyTH8sI2VlXIyJer-XQOIAr 72eadea037b273f731d3dfa8eb3a07fa489e7b33&uuid=&state=_BLhILn4SxNIvvL0W45KSic66uCIg23qh8iRG98qeIXme
  • https://yandex ru/clck/jsredir?from=yandex ru;search;web;;&text=&etext=1837 WLVAVHFbsHmm8vwkuLuQLntDUFl08HhPEWUJldr-poq_yANr1_oop1vqtOQXjwWN 560477478af8c1abe13f81cb84c37f9784bccf5a&uuid=&state=_BLhILn4SxNIvvL0W45KSic66uCIg23qh8iRG98qeIXme
  • https://yandex ru/clck/jsredir?from=yandex ru;search;web;;&text=&etext=1835 5uLGOpllG05R-lUKP5R605hb1YhxsMJEJeKdfwC-BzqcPkROs4UTjNqFpCseSJSY 227fac816aebf5112bc7e7b003feeb4e08f5a9eb&uuid=&state=_BLhILn4SxNIvvL0W45KSic66uCIg23qh8iRG98qeIXme
  • https://yandex ru/clck/jsredir?from=yandex ru;search;web;;&text=&etext=1830 RZxRQ2FHvJa_O9z8bj86mhfdZmkr-IfsAzLBVk04sQ9yyQTBkJQxvNgR_Faf1Rp4 10e3524e94d6e8606c3f5d8f6763b9ec07d58af5&uuid=&state=_BLhILn4SxNIvvL0W45KSic66uCIg23qh8iRG98qeIXme
  • https://yandex ru/clck/jsredir?from=yandex ru;search;web;;&text=&etext=1828 MpAC1zLF0Mp0i8z9Cl31DbsliYveTxG4FVs9wJrF1qkrU5bHVyEIhctPNY4aigvA 7a5a637074d5bca5b39362b9f329b9f7cd0a532e&uuid=&state=_BLhILn4SxNIvvL0W45KSic66uCIg23qh8iRG98qeIXme
  • ESXi-Customizer-PS execution policy
  • adding realtek drivers to esxi 6 5
  • westgfq

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:

  • enable tracert on cisco ASA
  • allow tracert asa
  • asa tracert
  • can you trace route from a cisco asa
  • Cisco ASA 5525X allowing trace route

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:

  • https://yandex ru/clck/jsredir?from=yandex ru;search;web;;&text=&etext=1824 9gQOlAAQU8Ge1EAhKP2VZUIc2q-WZOPpgk2L5vc5h8a6hy9E0_6eGzzEaY1d0eFX 330323684685c4a6eaf848b4d4f0838c3e68e5c5&uuid=&state=_BLhILn4SxNIvvL0W45KSic66uCIg23qh8iRG98qeIXme

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:

  • graylog syslog 514
  • https://yandex ru/clck/jsredir?from=yandex ru;search;web;;&text=&etext=1825 CYnBY5_SCrDy8UwcjgCmujx7n7o8g_jDeKg_5BPc3ZSVWZUKGiCvvbOVZifC0Rwk 5ef2f6e1aacc0fe99f61a172d0dcbea3b9ac139b&uuid=&state=_BLhILn4SxNIvvL0W45KSic66uCIg23qh8iRG98qeIXme
  • https://yandex ru/clck/jsredir?from=yandex ru;search;web;;&text=&etext=1832 kzZXKHyT1W-ei0gyq8wNqi1VZrA4w-sZ63TwRuhDGHzv2fnM-PRsXQHwH_6GHsru 0a83139f8ac5c535160089439cbe41a5241831c2&uuid=&state=_BLhILn4SxNIvvL0W45KSic66uCIg23qh8iRG98qeIXme

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

Incoming search terms:

  • unable to add torrent buffalo