Messages

1

General Discussion / Is adding public IPs to WAN interface with separate MAC addresses possible?

« on: October 16, 2018, 10:51:24 am »

I have several public IPs from my ISP I want to use for VMs behind OPNsense but they need to be bound to specific MACs.
I tried adding alias IPs but I can't define MACs.

is this possible somehow?
I am trying to avoid adding one physical WAN interface for each public IP but I can do it if its needed as OPNsense is also running in a VM.

Hope that makes sense and someone can clarify my question.

2

17.1 Legacy Series / Re: Any chance of upgrading freebsd 10.3 to 11.0 on Raspberry Pi with opnsense ?

« on: August 24, 2017, 11:28:20 am »

Awesome, I will give it a try.

3

17.1 Legacy Series / Re: Any chance of upgrading freebsd 10.3 to 11.0 on Raspberry Pi with opnsense ?

« on: August 23, 2017, 09:51:03 pm »

Thanks for the clarification Franco.

4

17.1 Legacy Series / Re: Any chance of upgrading freebsd 10.3 to 11.0 on Raspberry Pi with opnsense ?

« on: August 23, 2017, 10:07:06 am »

I'm wondering if someone can point me towards where I can read the current status regarding opnsense support for raspberrys.

I'm interested to know if it runs on a pi 3 and which image could be used for that.

5

General Discussion / Re: How to configure OPNsense on OVH Hosting in a virtual environment

« on: February 28, 2017, 10:05:47 am »

I'm with SoYouStart too! Thanks for the tips, I'll be checking them out. Just wondering as you mention NAT, all my VMs have their own public IPs.

6

General Discussion / Re: How to configure OPNsense on OVH Hosting in a virtual environment

« on: February 18, 2017, 12:40:09 pm »

I haven't made any progress and other issues cropped up so I have postponed this until I find more time.

7

General Discussion / How to configure OPNsense on OVH Hosting in a virtual environment

« on: November 30, 2016, 11:54:08 am »

Hi there,

I am attempting to install OPNsense in a virtual machine using OVH as my host.
OVH has a different setup than the usual hosts namely that the Gateway for VMs is basically the IP of the host with a .254 ending so the Gateway of OPNsense would be outside the WAN network.

All I could find on this topic is:

• a post from 2015 with the exact same problem: https://forum.opnsense.org/index.php?topic=1500.msg4562#msg4562
• a blog post treating the same problem with pfsense 2.0: http://blog.magiksys.net/pfsense-firewall-default-gateway-different-subnet
  
• a similar blog post about pfsense 2.0: http://magiksys.blogspot.de/2012/12/pfsense-bridge-gateway-vmware-ovh-ip.html
  
• the explanations of the host: http://help.ovh.co.uk/BridgeClient
  
• another thread dealing with this problem with pfsense: https://forum.ovh.co.uk/showthread.php?6507-ESXi-pfSense-and-failover-IP
  

I hope someone can help. I am very happy with OVH, its one of the biggest hosts in Europe so I am very surprised that I could not find more info on this topic and all the info I found was from around the years of 2012-2013.

I have attached the config of a windows machine to demonstrate what is needed. Here is some more info to go with that screenshot:
94.xxx.xxx.79 is the host in this case Proxmox but could be VMware or any other hypervisor
51.xxx.xxx.83 is an IP assigned to a VM, in this case Win10 but OPNsense will get a similar one
255.255.255.255 is the netmask which needs to be used as OVH does some weird ARP stuff behind the scenes
94.xxx.xxx.254 is basically the IP of the hypervisor with the ending replaced with 254 to serve as the gateway

To summarize:
Can someone write some sort of tutorial or at least confirm which solutions found in the above links is recommended for OPNsense 16.7?