FireboxV Hetzner HyperV Interface0

JSCJSC
in Firebox - Firebox Cloud & FireboxV

Hello,

I have set up a VM with FireboxV on a Windows server (dedicated, hosted by Hetzner). I have ordered an additional IPv4 add-on from Hetzner so that both the HyperV and the FireboxV can receive a public IP address.
So far I have made the configuration on the HyperV side (static MAC address). Unfortunately, the Firebox does not obtain the IP for the Interface0 via DHCP and even if I enter the IP statically, the interface is displayed as UP, but I cannot ping the Firebox from outside and cannot access the web interface from outside. I can reach the web interface via Interface1 without any problems and the interface works.

Does anyone have an idea what I have done wrong / what I can optimize?

Comments

  • james.carsonjames.carson Moderator, WatchGuard Representative

    Hi @JSC

    If the firewall is detecting the interface, that is likely the extent of what can be done on the firebox itself.

    If you run a TCPDUMP on the new interface, do you see any traffic at all? If you see the firewall ARPing for the default gateway, the interface is likely not connected to the firewall in a way that will get it anywhere in your hypervisor.

    If you haven't done so, I'd suggest opening a support case so that our team can get more information and logs from your device to help. You can open a case using the support center link at the top right of this page.

    -James Carson
    WatchGuard Customer Support

  • JSCJSC

    Hello @james.carson
    Thank you for your answer.
    When running the TCPDUMP I only get the following output (The first blacked out IP is the gateway and the second is the public IP for the Firebox):

    I will probably open a support case. Do you happen to know where I can find the serial number of the firewall or why I can't select anything in the field🙈?

  • james.carsonjames.carson Moderator, WatchGuard Representative

    Hi @JSC
    That's the firewall ARPing on the interface for the default gateway (most likely) -- it's most likely the hypervisor's setup for that interface causing the problem.

    If you go to the dashboard -> Front panel (the page you see after you log in) your firebox's serial number will be on the far right side under the system area. You can also see your serial number in System -> Feature Key.

    -James Carson
    WatchGuard Customer Support

Sign In to comment.