Encountered problem when using pptp in Linux - linux

I tried to use pptp in Ubuntu 10.10 and encountered the following error (ip address, username, and password have been omitted)
sudo pptpsetup --create vpn --server
XXX --username XXX --password XXX
--start Using interface ppp0 Connect: ppp0 <--> /dev/pts/1 CHAP
authentication succeeded Cannot
determine ethernet address for proxy
ARP local IP address XXX remote IP
address XXX
Could anyone figure out why?

Are you sure that is an error?
From the known working log:
...
rcvd [IPCP ConfAck id=0x3 <addr 168.192.232.42>]
Cannot determine ethernet address for proxy ARP
local IP address 168.192.232.42
remote IP address 168.192.232.31
...

Related

Host ping failed Virt-Management failed to get a response

I installed ubuntu-server in Virt-Management.
I cannot get a response using the following command
ubuntu-server ip: 10.0.2.15
my host ip : 192.168.124.10
ping 10.0.2.15
PING 10.0.2.15 (10.0.2.15) 56(84) 字节的数据。
But ubuntu can get a response
Please see the picture below

Remote access to OpenShift Local (CRC) running on Win11

I've got CRC running on Windows 11 and I would like to connect there from a RHEL9 VM.
CRC listening on 127.0.0.1:6443
Port forwarding rule created on Win machine to fwd connections on 192.168.1.156 (local intf) to 127.0.0.1:
$ netsh interface portproxy show v4tov4
Listen on ipv4: Connect to ipv4:
Address Port Address Port
192.168.1.156 9000 127.0.0.1 6443
Added rule in firewall to allow connections to port 9000
From the VM:
[test#workstation ~]$ telnet 192.168.1.156 9000
Trying 192.168.1.156...
Connected to 192.168.1.156.
Escape character is '^]'.
Connection closed by foreign host.
[test#workstation ~]$ oc login -u developer -p developer https://192.168.1.156:9000
The server is using a certificate that does not match its hostname: x509: certificate is valid for 10.217.4.1, not 192.168.1.156
You can bypass the certificate check, but any data you send to the server could be intercepted by others.
Use insecure connections? (y/n): y
Error from server (InternalError): Internal error occurred: unexpected response: 412
Any idea on how I can fix this and be able to connect from my VM towards CRC?
thanks

How to SSH from one Raspberry PI to a Raspberry PI running inside VirtualBox

I have a Raspberry PI running on 192.168.1.xx and I'm trying to SSH from this PI to a second PI running inside VirtualBoxVM.
On VM (using NAT) I have port forwarding enabled by:
Host Port -> 2222 Guest Port -> 22
However when I try to ssh from PI1 to PI2:
ssh -p 2222 pi#localhost -vvvv
I get the following error:
debug1: connect to address 127.0.0.1 port 2222: Connection refused
ssh: connect to host localhost port 2222: Connection refused
I can SSH into the PI2 from my MBP (so I know SSH is correctly set up), but cannot from PI1. I can't figure out why PI2 is only refusing connection from PI1?
Running ifconfig on PI2:
eth0 Link encap:Ethernet HWaddr 08:00:27:41:cb:b4
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
You are forwarding port 2222 from your host computer's network interfaces to your VM.
You are attempting to connect to port 2222 on localhost from your other computer.
You need to connect to port 2222 on the host machine, not your other computer.
ssh -p 2222 pi#ip_of_macbook_pro -vvvv

Ping a virtualbox machine from the host machine shows "Destination Host Unreachable"

I don't know why but I can't ping a virtual machine node from the host. I have created a network:
vboxnet1:
IPv4 Address: 192.168.57.0
IPv4 Network Mask: 255.255.255.0
IPv6 Address: fe80:0000:0000:0000:0800:27ff:fe00:0000
IPv6 Network Mask Length: 64
Then I have created a virtual machine with 2 interfaces:
adapter 1: NAT
adapter 2: Host-only Adapter. Name: vboxnet1
Check "Cable Connected"
Then I have Installed CentOS 7 on VM.
edit: /etc/sysconfig/network-scripts/ifcfg-eth0:
DEVICE=eth0
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
ONBOOT=yes
edit: /etc/sysconfig/network-scripts/ifcfg-eth1:
TYPE=Ethernet
IPADDR=192.168.57.111
NETMASK=255.255.255.0
BOOTPROTO=static
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=eth1
DEVICE=eth1
ONBOOT=yes
"ip addr" on VM shows that eth0 is 10.0.2.15/24 and eth1 is 192.168.57.111/24
"route -n" on host machine shows:
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
192.168.56.0 0.0.0.0 255.255.255.0 U 0 0 0 vboxnet0
192.168.57.0. 0.0.0.0 255.255.255.0 U 0 0 0 vboxnet1
Virtual machines can ping each other. Also, Virtual machines can ping the host machine but the host machine can't ping virtual machines.
Can somebody explain why it isn't working?
I used a bridge network because security isn't a concern in my setup.
Here is a summary of tutorial in the link from #ser99.sh
Select the virtual machine that you want to connect to your network:
Rightclick your virtual machine and select settings --> network settings --> bridge network:
Start up your virtual machine and select a suitable static IP address:
Verify that you have access to other computers:
If you want connect your host machine with guest machines, you can use "bridge network"
http://www.thegeeky.space/2015/06/how-to-set-and-run-bridge-virtual-network-on-CentOS-Kali-Linux-Windows-in-Virtualbox-with-practical-example.html

Virtual IP failover on 2 Linux box

I have 2 Linux VM Box.
VM1 ip is 192.168.0.4
VM2 ip is 192.168.0.5
GW: 192.168.0.1, net mask: 255.255.255.0
1)I have added a virtual ip on VM1
ifconfig eth0:1 192.168.0.10 netmask 255.255.255.0 up
Then I can ping it successfully from my client
2)removed the virtual ip on VM1
ifconfig eth0:1 192.168.0.10 netmask 255.255.255.0 down
Then I can NOT ping it successfully from my client
3)Add the same virtual ip on VM2
ifconfig eth0:1 192.168.0.10 netmask 255.255.255.0 up
!!I failed to ping this ip!!
however 1-2 hours later, I can ping it successfully.
3)Add the same virtual ip on VM2
however 1-2 hours later, I can ping it successfully.
Try flushing the ARP table on the client:
ip neigh flush all dev eth0
Also, I believe having the second VM send gratuitous ARPs after getting the new IP will solve the problem.

Resources