I am setting up my raspberry pi as a VPN client using IPsec/L2TP.I am using the following guide Configure Linux VPN clients using the command line
There are several problems which I am encountring
After setting up all the settings, when I try to start the IPsec connection using ipsec up myvpn. I get the following error
/usr/local/sbin/ipsec: unknown IPsec command "up" ("ipsec --help" for list)
After setting up and rebooting my raspberry pi, when I run ipsec verify, I get the table status table of ipsec verify in which my pluto is not running(error 1) and
there is an error of ikev1.
My motivation is to setup VPN client on my raspberry pi using IPsec/L2TP so that I can access my remote VPN client.
Also I am setting up my IPsec/L2TP using strongSwan and xl2tpd but using Ipsec verify, on path ipsec verison is Libreswan 3.27 (netkey) on 4.14.98-v7+. i tried to change it but didn't succeeded.
Any recommendations regaridng above mentioned queries would be great and I shall be thanful.
Regards
Saqib
Related
I am attempting to connect MATLAB with a Raspberry Pi 3+. Using the application installer in MATLAB, I downloaded and installed the necessary support hardware (https://www.mathworks.com/hardware-support/raspberry-pi-matlab.html) and then used the configuration dialog in those apps to flash a microSD card. Booting the Pi with that card, I set up passwordless sudo and enabled SSH. Using an ethernet cable to connect my laptop with the Pi, I can ping the Pi from MATLAB, and I can SSH in using PuTTy. However, when I try to connect in MATLAB (having opened MATLAB in admin mode), I get the following error:
I'm not sure where to go from here -- this error isn't listed on MATLAB's help page, and I cannot find anything online. Any help is appreciated.
Answer is straightfoward: problem found between user and keyboard. The device address should ONLY be the IP address of the Pi.
I have been struggling a bit to get access to airflow from outsite my network.
I have airflow running on a raspberry pi 4, and all seems to be working just fine, I can access it via http://localhost:8080.
I have also set forwarding rules in my home router pointing to the raspberry pi:
The port forwarding is working since I can see it open using an external tool, and I have also set up a SSH port forwarding to access my raspberry pi from outside my local network.
So accessing http://my-public-ip:123 should be taking me to my aiflow web ui, but instead I just got "This site can't be reached".
Can anybody spot what I have done wrong or if I skipped any step of the process?
Thanks in advance.
Are you running Airflow with Docker or you have it installed? If using Docker, setting the webserver's service port to 127.0.0.1:8080:8080 it's the first step.
Secondly, you might need to look into the config webserver options. You will need to set the AIRFLOW__WEBSERVER__BASE_URL: 'http[s]://your_address/airflow' environment variable and install a reverse proxy (I suggest you nginx); you can find more details here. After you've done this, don't forget to also set the environment variable AIRFLOW__WEBSERVER__ENABLE_PROXY_FIX: 'true
I am new to Home Assistant and I currently have a disc image of the software installed on a Raspberry Pi 3b. I have managed to get this up and running successfully by connecting my PI to an internet connection via an ethernet cable and connecting my laptop to the same network wirelessly. The problem I am facing is that I wish to run this locally without an internet connection and simply connecting my laptop to the PI with the Ethernet cable does not seem to be working. I have tried looking around for support but I cannot seem to find much on the matter.
Home Assistant's default port is 8123 not 8023.
If there is a direct connection between your laptop and the Raspberry Pi then the chance is high that mDNS won't not work. Thus, homeassistant.local is not reachable.
Add a static IP address for your Home Assistant host and your laptop.
I want to install MATLAB and Simulink support package for Raspberry Pi. I follow this link to do . I directly connect my laptop with Raspberry Pi using Ethernat cable.
But i didn't get output.
while installing i got error - "Could not detect a Raspberry Pi board on "Local Area Connection". Check your Ethernet connection to Raspberry Pi.
The FDX/LNK/100 LEDs on the Raspberry Pi board should be illuminated.
For network trouble-shooting instructions see http://www.mathworks.com">The MathWorks Web Site"
Can anyone help to solve this problem?
I have also experienced your same issue but after proceeding in this way I solved it.
Before you put the SD card on the Raspberry Pi you need:
power off the Pi
connect the Ethernet cable to the host computer
finally power on the Pi
In addition you may take a look at this troubleshooting guide.
Try the following steps.
1. Open cmd and execute 'ipconfig'
check for a network interface with '169.x.x.x' ip address
If there is one, you could access your Pi via IP 169.254.0.2
If there is none, check if your Ethernet port is enabled and no static IP is configured.
The above steps make sure that your Ethernet port is in proper state.
Repeat the hardware setup with direct connection in the network settings.
I am trying to connect XenCenter 6.0 to Server installed with XENSERVER 6.0 but i can't connect.
It give me error when i try to connect :
"Unable to connect to server '192.xxx.xxx.xxx'.
The connection was refused.
Check that Xenserver is configured correctly on '192.xxx.xxx.xxx'."
Also When i was using another computer for connecting xencenter, It was disconnecting automatically every time i connect
Examine some details:
List item
the server is power-on
the network configuration is right.(try to use "ping" or "ssh" to check)
the firewall setting
duplicate IP address which has been used
There are two possible scenarios in this case .
Either
1. The xenserver physical machine is powered off.
Or
2. The network cable is not connected properly.
If the server is pingable, make sure xapi and xapi-ssl are running.
ssh to the xen server and check the following:
/etc/init.d/xapi status
/etc/init.d/xapi-ssl status
If they are not running restart them
/etc/init.d/xapi start
/etc/init.d/xapi-ssl start
might require a xe-toolstack-restart