[SOLVED] Endian Firewall Community

[jose.cardoso]

Hello all.

I know it's not a eecommended setup and might not make much sense but, I use to have an Endian Firewall Community Edition vm on my Esxi servers, so I can make some trials and new employee education.

I'm now migrating all my internal Esxi servers to PVE, so I can be fully confident to implement it on my customers and, when migrating an HP Microserver where I use to have this testing vms, I've setup some Endian Firewall Commuinity on the PVE.

After the initial setup, made over PVE console, I should continue the setup on the web interface on port 10443.

But, when I try to access this web interface, I can't connect, because the connection is refused.

I've tried SSH access on port 22, and I can't connect either.

I can ping the vm.

I saw a post on the forum where one user changed the NICs to Intel E1000 to solve the problem, but even with this change I can't connect.

Do you know what might be happening?

Thanks in advance.

 

[hd--]

Hello
i assume you configured external access to your endian firewall in advance.
Can your access the Endian firewall VM via. GUI VM -> Console ?

 

[jose.cardoso]

Hello
i assume you configured external access to your endian firewall in advance.
Can your access the Endian firewall VM via. GUI VM -> Console ?

Yes, I do. And I can ping from local network. But I get connection refused onver port 10443 and 22.

 

[rabban]

Hi José,

I've already previously installed Endian in PVE and didn't had any issues accessing it. What I recommend is that you can use VirtIO for the network interface model

Also could you please try accessing to the Endian CLI and do a ping to a computer in your network.

And last, ensure you're using https://192.168.0.15:10443. I know that Endian can reject access if you're not using https.

 

[jose.cardoso]

Ok. I've changed the Endian IP address to 192.168.69.66.


I can ping my computer (192.168.69.69) from the VM.



I can ping from my computer to the Endian VM



Still, I can't connect.



These are my VM settings.



I can't understand where I'm missing...

 

[rabban]

Hi José,

Try doing Endian's network configuration again and enable access from red and green interfaces.

 

[jose.cardoso]

Huummm. OK.


I can ping gateway 192.168.70.254, 1.1.1.1 and google.pt, so DNS is working.



Still, no luck...

 

[jose.cardoso]

Do you think it might be something with the Linux bridge setup?

 

[rabban]

It's possible, however your network setup for the Linux bridge vmbr0 should have as CIDR 192.168.69.0/24 and the gateway of your network 192.168.69.0/24.

What I understand is that eth0 is the network interface for vmbr0, so it should use an IP in that range and you have communication between hosts in that network.

Regarding vmbr1, it should be configured for a different port to provide a different interface for Endian's red interface

 

[jose.cardoso]

It's possible, however your network setup for the Linux bridge vmbr0 should have as CIDR 192.168.69.0/24 and the gateway of your network 192.168.69.0/24.

What I understand is that eth0 is the network interface for vmbr0, so it should use an IP in that range and you have communication between hosts in that network.

Regarding vmbr1, it should be configured for a different port to provide a different interface for Endian's red interface

Right, I think everything is OK with that. I just don't have a CIDR for the external network (I don't thik it's needed), but all the rest is OK.

 

[rabban]

Hi José,

I was able to reproduce your setup and I can't reproduce the issue. The only important thing is that Endian requires 2 network interfaces, and you have enabled them both, eth0 and eth1. It's ok to keep the CIDR configuration blank for vmbr1 if you are not planning to access through red interface yet

The only interesting thing that I noticed is that the Endian's configuration took a while to be applied so the web interface was available. You can also disable the tick for "Firewall" in network interface "net0" but is not necessary as the firewall is disabled by default for VMs in Proxmox.

Also give it a try to command restarthttpd in Endian.

 

[jose.cardoso]

Well, I've just created a new VM, and it's working!

I relly can't understand, why, because I've used exactly the same settings but, anyway, it's working!
Thanks for all the support.

 

[rabban]

Hi,

Glad to know that you solved your issue! Don't forget to update the thread to SOLVED!

 

[jose.cardoso]

Hi,

Glad to know that you solved your issue! Don't forget to update the thread to SOLVED!

Done. Thanks @jjca .