Running Debian VM with more than on network card. On same IP range

espenbo

New Member
Mar 24, 2024
1
0
1
I need several network cards that are on the same IP range to talk to services on other IP ranges. I need it since I will connect to bacnet BBMD in different ip ranges.

I do this on a other site with kepware on a windows server. There I have 100 virtual network cards that I can set different BBMD hosts on. Or I can connect with the IP address of the PLC

From the Debian server running I can ping every site and have connection.
But when I try to make more network cards on the Debian server I can't ping from every network card. And I only get BBMD to work on one card.
Info about bacnet BBMD
More info about bacnet
SimpelCloud.png
I think it's has something to do with the routing table, but I'm not sure.
I made a test server to try to get the right network setup.

Anybody have any tips on what I can do?

Bash:
caesar@testVMdebian:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever

2: ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether aa:67:27:eb:cc:a9 brd ff:ff:ff:ff:ff:ff
    altname enp0s18
    inet 10.240.1.206/24 brd 10.240.1.255 scope global dynamic ens18
       valid_lft 79869sec preferred_lft 79869sec
    inet6 fe80::a867:27ff:feeb:cca9/64 scope link
       valid_lft forever preferred_lft forever

3: ens19: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether fe:24:26:77:48:94 brd ff:ff:ff:ff:ff:ff
    altname enp0s19
    inet 10.240.1.212/24 brd 10.240.1.255 scope global dynamic ens19
       valid_lft 79869sec preferred_lft 79869sec
    inet6 fe80::fc24:26ff:fe77:4894/64 scope link
       valid_lft forever preferred_lft forever

4: ens20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 4e:7e:d5:a3:6d:44 brd ff:ff:ff:ff:ff:ff
    altname enp0s20
    inet 192.168.2.105/24 brd 192.168.2.255 scope global dynamic ens20
       valid_lft 36736sec preferred_lft 36736sec
    inet6 fe80::4c7e:d5ff:fea3:6d44/64 scope link
       valid_lft forever preferred_lft forever
I tride pinging from the two cards on the same ip range.
Bash:
caesar@testVMdebian:~$ ping -c 2 10.240.5.10 && ping -I ens18 -c 2 10.240.5.10 && ping -I ens19 -c 2 10.240.5.10
PING 10.240.5.10 (10.240.5.10) 56(84) bytes of data.
64 bytes from 10.240.5.10: icmp_seq=1 ttl=62 time=82.6 ms
64 bytes from 10.240.5.10: icmp_seq=2 ttl=62 time=53.3 ms

--- 10.240.5.10 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 53.330/67.981/82.632/14.651 ms
PING 10.240.5.10 (10.240.5.10) from 10.240.1.206 ens18: 56(84) bytes of data.
64 bytes from 10.240.5.10: icmp_seq=1 ttl=62 time=60.5 ms
64 bytes from 10.240.5.10: icmp_seq=2 ttl=62 time=63.7 ms

--- 10.240.5.10 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 60.473/62.103/63.733/1.630 ms
PING 10.240.5.10 (10.240.5.10) from 10.240.1.212 ens19: 56(84) bytes of data.

--- 10.240.5.10 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1021ms
pipe 2
caesar@testVMdebian:~$
tshark looking at the packages
Bash:
caesar@testVMdebian:~$ sudo tshark -i ens19 -f "host 10.240.5.10" --color -c 30
Running as user "root" and group "root". This could be dangerous.
Capturing on 'ens19'
    1 0.000000000 fe:24:26:77:48:94 → Broadcast    ARP 42 Who has 10.240.5.10? Tell 10.240.1.212
    2 1.021185048 fe:24:26:77:48:94 → Broadcast    ARP 42 Who has 10.240.5.10? Tell 10.240.1.212
    3 2.045175810 fe:24:26:77:48:94 → Broadcast    ARP 42 Who has 10.240.5.10? Tell 10.240.1.212
Bash:
caesar@testVMdebian:~$ sudo tshark -i ens18 -f "host 10.240.5.10" --color -c 30
Running as user "root" and group "root". This could be dangerous.
Capturing on 'ens18'
    1 0.000000000 10.240.1.206 → 10.240.5.10  ICMP 98 Echo (ping) request  id=0xd1eb, seq=1/256, ttl=64
    2 0.082620835  10.240.5.10 → 10.240.1.206 ICMP 98 Echo (ping) reply    id=0xd1eb, seq=1/256, ttl=62 (request in 1)
    3 1.001739487 10.240.1.206 → 10.240.5.10  ICMP 98 Echo (ping) request  id=0xd1eb, seq=2/512, ttl=64
    4 1.055058252  10.240.5.10 → 10.240.1.206 ICMP 98 Echo (ping) reply    id=0xd1eb, seq=2/512, ttl=62 (request in 3)
    5 1.056409916 10.240.1.206 → 10.240.5.10  ICMP 98 Echo (ping) request  id=0xe5ea, seq=1/256, ttl=64
    6 1.116872579  10.240.5.10 → 10.240.1.206 ICMP 98 Echo (ping) reply    id=0xe5ea, seq=1/256, ttl=62 (request in 5)
    7 2.058043729 10.240.1.206 → 10.240.5.10  ICMP 98 Echo (ping) request  id=0xe5ea, seq=2/512, ttl=64
    8 2.121756731  10.240.5.10 → 10.240.1.206 ICMP 98 Echo (ping) reply    id=0xe5ea, seq=2/512, ttl=62 (request in 7)
    9 2.123445020 fe:24:26:77:48:94 → Broadcast    ARP 42 Who has 10.240.5.10? Tell 10.240.1.212
   10 3.144559986 fe:24:26:77:48:94 → Broadcast    ARP 42 Who has 10.240.5.10? Tell 10.240.1.212
   11 4.168562798 fe:24:26:77:48:94 → Broadcast    ARP 42 Who has 10.240.5.10? Tell 10.240
The router info
Bash:
caesar@testVMdebian:~$ routel 
         target            gateway          source    proto    scope    dev tbl
        default         10.240.1.1                                    ens18 
    10.240.1.0/ 24                    10.240.1.206   kernel     link  ens18 
   192.168.2.0/ 24                   192.168.2.105   kernel     link  ens20 
     10.240.1.0          broadcast    10.240.1.206   kernel     link  ens18 local
     10.240.1.0          broadcast    10.240.1.212   kernel     link  ens19 local
   10.240.1.206              local    10.240.1.206   kernel     host  ens18 local
   10.240.1.212              local    10.240.1.212   kernel     host  ens19 local
   10.240.1.255          broadcast    10.240.1.206   kernel     link  ens18 local
   10.240.1.255          broadcast    10.240.1.212   kernel     link  ens19 local
  100.68.234.98              local   100.68.234.98   kernel     hosttailscale0 local
      127.0.0.0          broadcast       127.0.0.1   kernel     link     lo local
     127.0.0.0/ 8            local       127.0.0.1   kernel     host     lo local
      127.0.0.1              local       127.0.0.1   kernel     host     lo local
127.255.255.255          broadcast       127.0.0.1   kernel     link     lo local
    192.168.2.0          broadcast   192.168.2.105   kernel     link  ens20 local
  192.168.2.105              local   192.168.2.105   kernel     host  ens20 local
  192.168.2.255          broadcast   192.168.2.105   kernel     link  ens20 local
            ::1                                      kernel              lo 
        fe80::/ 64                                   kernel           ens18 
        fe80::/ 64                                   kernel           ens19 
        fe80::/ 64                                   kernel           ens20 
            ::1              local                   kernel              lo local
fe80::4c7e:d5ff:fea3:6d44              local                   kernel           ens20 local
fe80::a867:27ff:feeb:cca9              local                   kernel           ens18 local
fe80::fc24:26ff:fe77:4894              local                   kernel           ens19 local
caesar@testVMdebian:~$
arp info
Bash:
caesar@testVMdebian:~$ sudo arp -n
Address                  HWtype  HWaddress           Flags Mask            Iface
10.240.5.10                      (incomplete)                              ens19
10.240.1.1               ether   68:54:ed:00:58:b8   C                     ens18
192.168.2.1              ether   20:97:27:04:aa:21   C                     ens20
10.240.1.1               ether   68:54:ed:00:58:b8   C                     ens19


caesar@testVMdebian:~$
```
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!