Hi, not sure if this is a question which has an easily available answer, but thought I would post just in case.
I've seen this at 2 sites now so it is pretty consistent.
-- Run ProxmoxVE on physical host with IP address 192.168.1.100
-- Run a KVM based VM of ClearOS at IP address 192.168.1.101
-- Configure PPTP / Poptop based VPN service on ClearOS, with "local" and "remote" PPTP IPs in the 192.168.1.X range
-- various other hosts in the 192.168.1.X network, physical or virtual
If I connect from a remote site via PPTP on the ClearOS VM (ie, port forwarding on the Public IP firewall device routes PPTP traffic inbound to the ClearOS VM's IP address).
-- I am able to access other servers in the internal LAN (192.168.1.X) without problem
-- but with one exception: I cannot access the Proxmox host itself (192.168.1.100) on which the ClearOS VM is running. Connections simply time out.
I wonder/suspect if this relates to how Poptop is setting up the local,remote IP bridge // and somehow (?) this doesn't play well with the local physical host where it is ultimately connecting (the ProxVE host). But it doesn't make a great deal of sense to me that I've got good access to other hosts in the network.
My usual workaround - is that I conect via PPTP, then RDP or remote to some other machine in the LAN - and from there I can access ProxVE web admin interface / or SSH to the ProxVE host. But it is slightly 'annoying'.
I suspect if I had a perfect understanding of precisely how PPTP via Poptop worked, I might understand better why this behaviour is observed.
Anyhow. If anyone has any thoughts, I'm certainly interested/happy/curious to hear them.
Thanks,
Tim
I've seen this at 2 sites now so it is pretty consistent.
-- Run ProxmoxVE on physical host with IP address 192.168.1.100
-- Run a KVM based VM of ClearOS at IP address 192.168.1.101
-- Configure PPTP / Poptop based VPN service on ClearOS, with "local" and "remote" PPTP IPs in the 192.168.1.X range
-- various other hosts in the 192.168.1.X network, physical or virtual
If I connect from a remote site via PPTP on the ClearOS VM (ie, port forwarding on the Public IP firewall device routes PPTP traffic inbound to the ClearOS VM's IP address).
-- I am able to access other servers in the internal LAN (192.168.1.X) without problem
-- but with one exception: I cannot access the Proxmox host itself (192.168.1.100) on which the ClearOS VM is running. Connections simply time out.
I wonder/suspect if this relates to how Poptop is setting up the local,remote IP bridge // and somehow (?) this doesn't play well with the local physical host where it is ultimately connecting (the ProxVE host). But it doesn't make a great deal of sense to me that I've got good access to other hosts in the network.
My usual workaround - is that I conect via PPTP, then RDP or remote to some other machine in the LAN - and from there I can access ProxVE web admin interface / or SSH to the ProxVE host. But it is slightly 'annoying'.
I suspect if I had a perfect understanding of precisely how PPTP via Poptop worked, I might understand better why this behaviour is observed.
Anyhow. If anyone has any thoughts, I'm certainly interested/happy/curious to hear them.
Thanks,
Tim