Your server settings indicate that you have 2 different networks.
Are your VMs using VMBR1? If so, and you don't actually have a 172.16.1.x subnet on your network, that's the problem.
Try it from the console. I am willing to bet that the SSH config is set to not allow root to SSH in. You will need to log in on console and make your changes. Either add another user to SSH in or set the SSHD config to allow root.
Why would you need port mirroring for this to work? This is actually a pretty standard setup.
Create a bridge with a NIC you want to use to a VMBRx, build a VM with that VMBR attached as it's 'WAN', and attach the other VMBR to the VM as it's LAN. Connect other VMs to the 'LAN' VMBR and tell...
Pro tip: If you mark your thread as solved, nobody can help you. If it was really solved, others might like to read what the fix was.
If you still cannot figure this out, you need to provide more information about your Proxmox configuration. It sounds like you have NAT enabled on this...
WHAT?
The QNAP doesn't have iSCSI, CIFS/SAMBA, or NFS?!!
WTF kind of NAS doesn't operate the most basic of NAS functions? How do you access files on it?
REALLY doubtful, considering how niche the request is. This sounds like something a cpanel-type application could use the API for. Someone will have to write it unless you want to start doing so. Maybe there is something out there similar...I don't know
you can't connect to ext3. cifs is the term used interchangeably for SAMBA share. ext3 is a filesystem, and cifs/smb/samba is a file sharing network protocol. completely different things. you NEED to use cifs to connect to a samba share.
you probably do not need the domain name. if it...
Yep.
TCPDUMP on the vmbr should have shown you everything.
I can attest that tagging VLANs from within the guest works well. I have been running virtual routers for years in ProxMox
I run virtual routers and tag vlans in and out all the time. what issue are you having? As long as your switch supports the VLAN tagging, it will just work.
Set up a virtual router on each VM host, and route the networks together, or create a VPN tunnel between the networks to simulate a real world scenario of having a remote office talking back to your DC
I know about Tapatalk...as I said, I have deployed it to several forums over the years.
Odd that it was totally cool with you guys up until this new forum software. Whatever though. I won't get to read the forums much any more now.
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.