Messages

It looks like it's down for everybody. If it was your firewall you wouldn't see a 404.

https://downforeveryoneorjustme.com/ssl.kaptcha.com?proto=https

Hello,

I got here looking for a solution... but you're stuck in a previous step I think. Did you got your OVH CK?
Because at first I failed creating an API login instead a script:

Code Select Expand

https://api.ovh.com/createToken/?GET=/domain/zone/contoso.com/*&POST=/domain/zone/contoso.com/*&PUT=/domain/zone/contoso.com/*&GET=/domain/zone/contoso.com&DELETE=/domain/zone/contoso.com/record/*
With that my log looks much better, but now I get timeout to every step it tries... I thinks it's time to wait until tomorrow.

Ok, my bad. I typed the wrong gateway, and it was working for minutes. Let's see if now everything stands until tomorrow.
With that fixed, I'm really planning to migrate all pfSense!

https://docs.ovh.com/gb/en/dedicated/network-bridging/

Hello, I'm trying to install an Opnsense in a ESXi at OVH.
In OVH the have a strange setup where your public IP is /32 and your Gateway is in another range. That used to be tricky, but now it's just "normal", there's an option.
Let me say that I been using their servers for years, with ESXi, Windows, Linux and pfSense. So I've been comparing my setup with a working pfSense and looks identical. But I lose connection in minutes and doesn't come back until I make a change to the WAN.
Tracking down the log the only thing that makes sense is:

Code Select Expand

kernel: pflog0: promiscuous mode enabled
kernel: pflog0: promiscuous mode disabled
kernel: arp: 123.123.123.123 moved from xx:xx:xx:xx:xx:xx to yy:yy:yy:yy:yy:yy on em1
pflog0: promiscuous mode enabled
kernel: pflog0: promiscuous mode disabled

Where 123.123.123.123 is my remote gateway and em1 my WAN.
Does it makes sense for any of you?