For my understanding:
When I have a port on the managed switch on which I want to use traffic of multiple vlans (the Proxmox Server is on one of them, containing VMs in the other vlans) , then I need to tag all these vlans on that port on the managed switch?
And then in Proxmox (having an IP...
Hi,
I currently have a Proxmox server-pc (1 NIC) running amongst others an OPNSense VM.
In the OPNSense VM I defined a LAN with several VLANs.
In Proxmox I created a VLAN aware virtual NIC vmbr1 (the LAN) and every VLAN is attached to its own connection which is vmbr1 and a tag) I am able to...
Hi,
I currently have a Proxmox server-pc (1 NIC) running amongst others an OPNSense VM.
In the OPNSense VM I defined a LAN with several VLANs.
In Proxmox I created a VLAN aware virtual NIC vmbr1 (the LAN) and every VLAN is attached to its own connection which is vmbr1 and a tag) I am able to...
Hi I'm moving exactly the opposite direction.
I currently have a Proxmox server-pc (1 NIC) running amongst others an OPNSense VM.
In the OPNSense VM I defined a LAN with several VLANs.
In Proxmox I created a VLAN aware virtual NIC vmbr1 (the LAN) and every VLAN is attached to its own...
Hi Mira, as it occurred again today I checked. Indeed the ping wanted to go to a IPv6 address, which did not succeed.
I removed (commented in fact with #) the standard ipv6 entries in /etc/hosts and rebooted the machine.
Pinging now worked with ipv4.
Is this all there is to it or do I have to...
Yes, this is the only connectivity problem I have. And it does not occur always, so a firewall rules should have blocked it always.
It is now 3 weeks later, and again my subscription is "invalid". :(
No, it doesn't.
When I run the CLI command "pvesubscription update" it gives the time-out. Also when rerunning a few minutes after reissuing the subscription on the shop.
Today I rerun this command approximately 1 hour after reissuing the subscription, and then it worked again and Proxmox...
Hi,
Can anyone tell me if they also experience the following error, which I have almost every month:
Error checking subscription: https://shop.proxmox.com/modules/servers/licensing/verify.php: Network Error: timed out reading response
Therefore updates are not coming in.
This is usually fixed...
Hi Lorenz,
I already have a working separate VM running OpenVPN for which I indeed do a portforward of 1194 from a.b.c.d. to 192.168.x.6 (the IP of the OpenVPN-VM).
I however want to change from a separately running VM to the build-in PfSense OpenVPN.
The problem is in the configuration of...
internet router PC with Proxmox host VMs (on "x")
public ip: a.b.c.d. ===> Powerline adapter connected to router ===> Powerline adapter 2 ===> HUB ==> 192.168.x.21 ===> 192.168.x.50+...
Hi,
I have attached a view on (a part of) my network map.
A port forward is needed indeed when trying to connect from outside. The problem in the first place is the fact the local WAN ip address 192.168.x.70 is not known on the internet, but a.b.c.d is.
Hi,
I have installed PfSense as a VM on Proxmox with 2 vmbr's. (By the way my machine is only equipped with one physical NIC.)
The gateway of the router is at 192.168.x.1. Proxmox has an IP of 192.168.x.21, my PfSense VM has a IP address of 192.168.x.70. (Which is set as the WAN IP of vmbr0)...
OK, well now at least I've got the pinging working now from one of my laptops, and from that laptop I now also can use the webconfigurator of PfSense. Thanks for your help!!
Hi ph0x,
Thanks again for your answer. :)Luckily point 1-4 were already in place ;), so I guess indeed the static route is not in place.
Would this be the command to be entered on the Proxmox Host that would do it?
route add -net 192.168.100.0 netmask 255.255.255.0 dev vmbr1
Or should it be a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.