FreeBSD a server and bhyve

[Pete Wright]

On 8/11/20 12:38 PM, Odhiambo Washington wrote:
>
>
> On Tue, 11 Aug 2020 at 20:23, Pete Wright <pete at nomadlogic.org 
> <mailto:pete at nomadlogic.org>> wrote:
>
>
>
>     On 8/11/20 5:49 AM, Odhiambo Washington wrote:
>     > Hi infoomatic,
>     >
>     > Looks like I have to top-post so as to not mess the thread:
>     >
>     > The reason I need a VM is because I need to totally independent
>     host,
>     > with an independent name, with access to all ports of its own.
>     > It looks like I need another public IP for that.
>
>     It depends on your use case.  I have a single IPv4 address
>     allocated to
>     one of my systems and have setup various CNAME entries in DNS that
>     all
>     resolve to the same IP.  I think that's a pretty common design
>     pattern
>     for people who colo their own servers and host multiple services
>     on them.
>
>     the tricky part will be if you want to host multiple instances of the
>     same service though (multiple webservers for example).  in that case
>     you'll most likely need multiple IPv4 address assigned to your system.
>
>
> That's exactly where I am.
> Suppose I obtained another IP for the VM, how do I make the VM the 
> only host listening on that IP then?

this should be pretty straight forward - the first step would be to 
setup the additional public IP's as virtual addresses on your NIC 
similar to this:
https://www.freebsd.org/doc/handbook/configtuning-virtual-hosts.html

then setting up your firewall (pf or ipfw) to forward requests coming in 
on one of those public IP's to the specific bhyve VM which is listening 
on a private IP.  this would be identical to hosting multiple services 
on a single IP.


here's an example pf config that does the forwarding of SMTP on port 25 
to a VM using a private IP to give you an idea of what the syntax would 
look like:
rdr pass on $ext_if inet proto tcp from any to 1.2.3.4 port = 25 -> 
10.1.0.10 port 25


hope this helps,
-pete

-- 

Pete Wright
pete at nomadlogic.org
@nomadlogicLA