During normal circumstances the DL/UL will just continue when a VPN goes up/down. With the new external IP. This is NOT what we want to happen since it rips off the anonymity, so we need to do some stuff to prevent it.
One application that solves this is VP NetMon, a software that can turn off an application when the network change. It’s very simple so even your grandma could set it up. Here is an example of a test setup:
Personally I use a PPTP-VPN (and yes, i know it’s not secure in that matter but I can never believe we need anything more if we are not dealing drugs or shit like that).
With PPTP there is a much better way. We know it uses TCP1723 to negotiate the tunnel and then GRE for data. So with only 3 rules we have a setup that will block the computer if the VPN goes down, i.e. only communicate on the VPN IP.
So we need to:
1) Allow creating the tunnel
2) Allow traffic over GRE
3) Block anything else
Here are example rules in pfSense for this setup, they works like a charm:
First, you need to console into the switch and run the following commands:
ip address 192.168.2.2 255.255.255.0
ip ssh filetransfer
password manager user-name <your username> plaintext <your password>
When the above commands are executed, you can use WinSCP to logon to the switch. WinSCP places part-files when uploading as default wich is not allowed, so we have to turn this off in before we connect. This is done via “Tools – Preferences -> Transfers -> Endurance -> Enable transfer resume….. -> Disable”
Rename the downloaded firmware to just primary or secondary. No .swi-ending.
Overwrite the with the same name in the /os-folder on the switch.
Do a “show flash” from shell and you’ll see when you are ready to reboot.
Now type “boot” and have fun 🙂
It’s always confusing which one to press to do what. This is it basically:
Clear: Press for 1 second and you will reset your password. The switch will to nothing else, so it can imo be done during working hours.
Reset + Clear: Press both of them and the switch will fall back to it’s factory default config.
All in Swedish since those were build into MANY Swedish houses in the 80’s.
“Reverse engineerat” orginalelschema för de vanliga FTX elboxarna (vevex) som byggdes in i en sjuklig mängd hus, speciellt i början av 80-talet.
Byggde om hela min elbox med 1-wire-sensorer och relästyrning istället. Givetvis styrt över nätverk. Kanske följer fortsättning på detta? Beror på vad jag orkar.
Download SPP…wait…create USB-stick…wait…boot server on USB-stick….wait….launch ACU..create array…wait..boot server…
If you used the HP ESXi ISO while installing ESXi (you did wrong if you didn’t) it’ll also install the hpssacli tool wich can make the above process in a couple of minutes. Just follow the steps:
- Enable SSH on host
- Login to SSH
- Run command: /opt/hp/hpssacli/bin/hpssacli ctrl all show config
- Look for the unassigned disk
- If single (or RAID0) disk, run: /opt/hp/hpssacli/bin/hpssacli ctrl slot=0 create type=ld drives=<YOUR DRIVE ID> raid=0
If RAID1 run: /opt/hp/hpssacli/bin/hpssacli ctrl slot=0 create type=ld drives=<YOUR DRIVE ID>,<YOUR SECOND DRIVE ID> raid=1
If RAID5 run: /opt/hp/hpssacli/bin/hpssacli ctrl slot=0 create type=ld drives=<YOUR DRIVE ID>,<YOUR SECOND DRIVE ID>,<YOUR THIRD DRIVE ID> raid=5
Now you can go back to vSphere and create your datastore as usual.