naxva.blogg.se

Then each vm I wanted to be “behind” pfsense went into the “isolated” network.

Stuck a nic in each network attached to the pfsense vm. However, due to the nature of my setup I created a “nat” network and an “isolated” network within KVM. Kind I have a CentOS7 host with pfSense in KVM as well. So what’s the right way to set this up, and how can I get it to receive a hostname like all my other clients? Instead, I have to connect to it by its IP address. But, it occasionally disconnects – maybe the lease runs out and it doesn’t ask for another? And also, it doesn’t take a hostname/domainname by which other LAN clients can connect to it. This connects as a LAN client and it gets an IP address and it connects to the internet. What I’ve done on the host is make a MACVLAN bridge link, and then run dhclient to connect: ip link add link eno2 name macvlan0 address BLABLA type macvlan mode bridgeīLABLA is a made-up mac address. But my issues are about trying to connect the host machine as a LAN client.Īctually, it sort-of works. Other KVM clients succesfully connect on the LAN MACVTAP bridged port, as do other physical machines. Using virtio drivers and using virt-manager. I’d like to ask, what’s the proper way of doing this, and how to fix one particular problem? My situation is thus:ĬentOS 7 host with a pfSense KVM guest, to which the physical WAN ethernet port is MACVTAP passthrough-ed and the physical LAN port is MACVTAP bridged, both successfully. So I almost have this working, but it’s highly hacky and doesn’t work properly.