Last Update: Instead of doing it with windows, I decided to create LXC (whatever linux version) and make it share the wifi over an Ethernet port that will be passed through to it.
Un-f*ing-believable! Just installed Windows 10 machine and it supports this Atheros wifi card with one click of updating driver.....crazy....I thought linux was much better in terms of compatibility regardless of bridging etc., just for basic functionality without so much manual configuration...
That's ok :) at least you're trying to help. I tried the same (including pass) with dhcp and I think I also tried with static IP but I'll try again...Thank you very much for taking the time to answer.
Update: Still not working...the wifi card at least appears as a network device in the GUI and under "ip a" but shows this message when trying to activate it and connect a known wifi network defined in /etc/network/interfaces
The real shame and bummer here is that even windows would have a...
For everyone who wants to know and/or had the same problem, this is the only thing that fixed the crash messages printed to the screen/console and also made the wireless card appear under "ip a". Now the only thing left to check is if the wifi connection will be stable
I need wifi to communicate with the outside world. The main VM will be pfSense. dd-wrt will act as access point just to get internet access. It only needs 256mb of ram so I think it's fine. I would just put pfsense on this device but FreeBSD doesn't support the wifi module it came with...
One option is to follow the link you sent (even though I tried something like that), hope that it works and then set the wifi to be wlan and use NAT for everything else. The other option (sounds better I think) is to install dd-wrt (or similar) on as a VM and use that a access point to provide...
Hi,
I'm having a problem with Qualcomm Atheros QCA6174 802.11ac (M.2 2230) wireless NIC.
I installed proxmox on a protectli device and it works fine except for this wifi card. The adapter doesn't show up in /etc/network/interfaces.
I see this adapter only when I run the "lspci" command. What...
Updating about the latency issue: After a few tests and a vibrant post on the pfSense forum, it turns out it has nothing to do with proxmox, virtualization or pfSense itself. It's the asymmetric DSL PPPoE connection and the ISP. Got the same result (high upload "loaded" value) on fast.com when I...
Thank you I checked prices and if you want 2GB RAM it would cost more than 75$. For that price you can buy a good Motherboard-CPU combo add a little extra money and have a machine that is either a monster Firewall or a mini server that acts as a firewall, NAS (basic) and other services or micro...
I'm moving back to a bare metal (mini itx case) pfSense install. Not just because of the issue described here but also because of many other issues that come with virtualizing whatever runs/manges/protects your entire infrastructure/network. It makes sense only if your entire enviroment is...
I decided to try and virtualize pfsense because sometimes you don't have a spare bare metal hardware to dedicate to it or you do but it's just not worth it for the little amount of resources that pfsense needs (in small to medium networks).
Everything works fine except for one weird issue that...
I already got the behavior I wanted but with one extra cable. I'll change it later to be completely internal (except the PCI-E passthrough of course).
Currently I'm passing an Intel PCI-E card to the FW VM and connecting the host with a cable to a switch that is controlled by the FW VM via that...
My setup is currently like this - I physically connect the motherboard's NIC (vmbr0) to a switch that is controlled by the FW VM (via its passed through PCI-E Intel card).
1. In order to achieve it internally without any loop cabling, I need to follow your suggestion, correct?
2. If I do as...
sgdisk --zap-all /dev/nvme0n1 Solved the problem, but thank you anyway for your response.
If you may please answer my other question :) - https://forum.proxmox.com/threads/route-all-vms-through-a-firewall-vm-confused-about-bridges.74906/#post-333886
I understand your point and the scenarios of not having remote access if pfSense goes down and I too feel that the firewall should be a standalone bare metal equipment but currently I don't have spare parts for something so minimal as firewall (in terms of hardware) and I don't wanna waste...
Ok...I understand but my setup is a little different. Also, I've read your post.
I'm passing a PCI-E Intel network card to the firewall VM. On the motherboard I have only one NIC (Realtek).
All that is left for me to do is route all VMs through a vmbr(x) bridge.
But I still have some questions...
I want all my VMs to go through my firewall VM. I know I need to bridge all of them but when I check the network on the host it shows the pve IP I chose during install.
Do I need to add a new Linux Bridge for every VM or just use the same vmbr0 for all of them and proxmox will do the rest and...
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.