Can't ping IP through RED interface

Networking
1

Hi,

I have several server running on my XigmaNAS VirtualBox.
My home network look like:
Router 10.0.0.1
XigmaNAS 10.0.0.100

My XigmaNAS hardware
INTEL X79 INTEL (INTEL Xeon E5/Corei7 DMI2 - C600/C200 Cipset)
CPU 16cores 2700MHz
RAM 64gig

I have install IPFire last version 2.27(178) and test an older version 2.25(158).

My virtual setup is simple:
RAM 4096MB
CPU 2cores
Network adapter 1 - NAT Card 82540EM
Network adapter 2 - Bridged Adapter 82540EM

In IPFire, my RED is on adapter 1 and GREEN on adapter 2.
RED
On network adapter 1
DHCP IP 10.0.2.15 Gateway 10.0.2.2 DNS 10.0.0.1
GREEN
On network adapter 2
Static IP 192.168.0.1

From my computer with IP 192.168.0.3 i can access the web gui (https://192.168.0.1:444) without problem.

image
image1023×604 81 KB

From the CLI i can ping on the following IP without problem:
10.0.2.15 RED
10.0.2.2 GATEWAY
192.168.0.1 GREEN
192.168.0.3 Another computer in this subnet
I can’t ping on the following IP (No response):
10.0.0.1 Local DNS
1.1.1.1 Cloudflare DNS
8.8.8.8 Google DNS
8.8.4.4 Google DNS

I got the same result with both version of IPFire 2.27(178) and 2.25(158).

I have no problem with my others virtuals guests with network in NAT or Bridge mode.

2

I change the DNS queries for TLS so i can navigate on internet in the browser of this computer(192.168.0.3) but if I ping from the CLI of IPFire or the cli of this computer i got time out.

image
image1221×685 130 KB

3

Welcome to the IPFire community.

To assist with your issue, it would be helpful to see the contents of both your ARP and Routing Tables. You can find these in the Web User Interface (WUI) under /Status/Network (others). Could you please share them?

Based on your configuration, it appears that your router at 10.0.0.1 might not be forwarding outgoing traffic properly, or XigmaNAS cannot route traffic properly between the IPFire virtual machine and the router.

Is this a correct representation of your network?

                    +---------------------+
                    |    Router           |
                    |    10.0.0.1         |
                    +---------+-----------+
                              |
                              |
                              |
                    +---------+-----------+
                    |    XigmaNAS         |
                    |    10.0.0.100       |
                    +---------+-----------+
                              |
                              | Virtual Network
                              |
                    +---------+-----------+
                    |     IPFire VM       |
                    | RED 10.0.2.15  (NAT)|
                    | GREEN 192.168.0.1   |
                    +---------+-----------+
                              |
                              |
                              |
                    +---------+-----------+
                    |   User's Computer   |
                    |   192.168.0.3       |
                    +---------------------+

Edit: if you bridge also the RED interface (instead of having a NAT), what happens?

2 Likes
4

As @cfusco wrote
you need to check XigmaNAS firewall logs

BR

1 Like
5

Another important information to help are the concrete network definitions:

  • router network 10.0.0.0/x
  • XigmaNAS network(s) 10.0.2.0/y
  • IPFire red 10.0.2.0/y
  • IPFire green 192.168.0.0/z

z is 24, right?

How does the XigmaNAS route to the VMs?
Where is 10.0.2.2, the gateway?

EDIT: Maybe the answers can be guessed from your description. But experience shows, that a nearly complete question is part of the solution.

2 Likes
6

Just for hint about 10.0.2.2
https://www.virtualbox.org/manual/ch06.html#network_nat

1 Like
7

Hi, thank you for your support.
Switching from NAT to Bridge for my RED interface work and i can ping all ip on RED now.
I can let it in Bridge mode, NAT mode seem broken on my NAS, i will check it at a later time.

If I change the DNS queries for UDP i got broken again… did using TLS can cause a problems?
image

8

Yes z is 24

The 10.0.2.2 gateway is the ip of the virtualbox NAT internal gateway.

I found the error in the Virtualbox log.
image

I keep it for a later time.

Thank you