"ethX: received packet with own address as source address" flooding!

I

italian01

Member
Feb 23, 2012
57
0
6
Italy
Hello to all readers.

I already wrote two threads in this forum along my Proxmox "experience". And I still keep trying to test Proxmox Hypervisor inside a VMWare Workstation 8 box, installing a Virtual Machine inside the Proxmox where a Windows 2003 Server could run.

I already overcame two obstacles: 1st, an issue with accelartion HW for "virtualization" which didn't permit to start the VM (http://forum.proxmox.com/threads/8466); 2nd, an issue with installation of SO because (without "full-update") Proxmox VM didn't recognize my physical DVD (http://forum.proxmox.com/threads/8483).

Now, I've got a new challenge!

So, my syslog and dmesg is flooded with follow lines:

HTML: 
....
....
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
__ratelimit: 41 callbacks suppressed
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
__ratelimit: 52 callbacks suppressed
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
eth0: received packet with own address as source address
....
....

Why? And what can I do for stopping this behavior?

Moreover, granted that my enviroment is

HOST: Windows 7 (where VMWare Workstation 8 is running);
​
1st HYPERVISOR: VMWare Workstation 8 (where Proxmos is running);
​
2nd HYPERVISOR: Proxmox (where Window 2003 Server SP2 guest is running);
​
GUEST: Windows 2003 Server SP2.


​
and that their IPs are:


  • HOST: 192.168.5.52/16
  • 2nd HYPERVISOR: 192.168.5.254/16
  • GUEST: 192.168.2.21/16

It happens that



  • GUEST can ping 2nd HYPERVISOR but neither HOST nor any workstation connected to LAN of this HOST.
  • 2nd HYPERVISOR can ping both GUEST and HOST and any workstation connected to LAN of this HOST.
  • HOST can ping 2nd HYPERVISOR but not the GUEST; in truth, this is not the correct definition... because behavior of ping of the HOST is ...a quite strange (discontinuous), as follows:


    HTML: 
    C:\>ping 192.168.2.21 -t
....
....
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Risposta da 192.168.2.21: byte=32 durata<1ms TTL=128
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Risposta da 192.168.2.21: byte=32 durata<1ms TTL=128
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Risposta da 192.168.2.21: byte=32 durata=1ms TTL=128
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
....
....

    * translation of "Richiesta scaduta" is "Request time out"

Again, why this happens? Does exist any relation between this behavior and which one described above?

Before closing of this message, follows some configs of my ethernet enviroment.



  • HOST: Windows 7

    HTML: 
    C:\Users\egidio.melissano.TS>ipconfig /all

Configurazione IP di Windows

   Nome host . . . . . . . . . . . . . . : ZZZZZ
   Suffisso DNS primario . . . . . . . . : yy.xxxxxx.it
   Tipo nodo . . . . . . . . . . . . . . : Ibrido
   Routing IP abilitato. . . . . . . . . : No
   Proxy WINS abilitato . . . . . . . .  : No
   Elenco di ricerca suffissi DNS. . . . : yy.xxxxxx.it
                                           xxxxxx.it


Scheda Ethernet Connessione alla rete locale (LAN):

   Suffisso DNS specifico per connessione: yy.xxxxxx.it
   Descrizione . . . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Indirizzo fisico. . . . . . . . . . . : 00-19-99-9B-59-23
   DHCP abilitato. . . . . . . . . . . . : Sì
   Configurazione automatica abilitata   : Sì
   Indirizzo IPv6 locale rispetto al collegamento . : fe80::19d1:4566:b70d:9ee9(Preferenziale)
   Indirizzo IPv4. . . . . . . . . . . . : 192.168.5.52(Preferenziale)
   Subnet mask . . . . . . . . . . . . . : 255.255.0.0
   Lease ottenuto. . . . . . . . . . . . : mercoledì 29 febbraio 2012 11:10:00
   Scadenza lease . . . . . . . . . . .  : lunedì 27 agosto 2012 11:09:57
   Gateway predefinito . . . . . . . . . : 192.168.0.1
   Server DHCP . . . . . . . . . . . . . : 192.168.1.21
   IAID DHCPv6 . . . . . . . . . . . : 234887577
   DUID Client DHCPv6. . . . . . . . : 00-01-00-01-15-6D-7A-91-00-19-99-9B-59-23

   Server DNS . . . . . . . . . . . . .  : 10.251.4.51
                                           10.251.8.51
                                           192.168.1.21
                                           192.168.1.22
                                           192.168.1.23
                                           192.168.1.24
                                           10.251.4.52
                                           10.251.8.52
   Server WINS primario . . . . . . . .  : 192.168.1.21
   Server WINS secondario . . . . . . .  : 192.168.1.22
                                           192.168.1.23
                                           192.168.1.24
   NetBIOS su TCP/IP . . . . . . . . . . : Attivato
  • 1st HYPERVISOR: VMWare Workstation 8

    1 Network Adapter: Bridged (connected directly to the physical network)
    Incoming Transfer: bandwidth UNLIMITED
    Outgoing Transfer: bandwidth UNLIMITED
    MAC Address: 00:0C:29:A7:FB:03



  • 2nd HYPERVISOR: Proxmox

    HTML: 
    root@proxmox:~# cat /etc/network/interfaces

auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 192.168.5.254
        netmask 255.255.0.0
        gateway 192.168.0.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0
    HTML: 
    root@proxmox:~# ifconfig -a

eth0      Link encap:Ethernet  HWaddr 00:0c:29:a7:fb:03
          inet6 addr: fe80::20c:29ff:fea7:fb03/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:885534 errors:0 dropped:0 overruns:0 frame:0
          TX packets:106020 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:432464290 (412.4 MiB)  TX bytes:33091547 (31.5 MiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:171107 errors:0 dropped:0 overruns:0 frame:0
          TX packets:171107 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:27838753 (26.5 MiB)  TX bytes:27838753 (26.5 MiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet6 addr: fe80::1/128 Scope:Link
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vmbr0     Link encap:Ethernet  HWaddr 00:0c:29:a7:fb:03
          inet addr:192.168.5.254  Bcast:192.168.255.255  Mask:255.255.0.0
          inet6 addr: fe80::20c:29ff:fea7:fb03/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:316883 errors:0 dropped:0 overruns:0 frame:0
          TX packets:98817 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:33523334 (31.9 MiB)  TX bytes:32687945 (31.1 MiB)

    HTML: 
    root@proxmox:~# route

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.0.0     U     0      0        0 vmbr0
default         192.168.0.1     0.0.0.0         UG    0      0        0 vmbr0

Thank's for your attention.

Regards.
 
Meanwhile, I've gathered more infos... and I'm going to share them here.

First of all, I forgot some network details in the last post and I put them here now. For instance, my bridge configuration:

HTML: 
root@proxmox:~# brctl show

bridge name     bridge id               STP enabled     interfaces
vmbr0           8000.000c29a7fb03       no              eth0

and my guest network configuration:

HTML: 
C:\>ifconfig /all

Windows IP Configuration

    Host Name........................: rdp
    Primary Dns Suffix:..............:
    Node Type........................: Unknown
    IP Routing Enabled...............: No
    WINS Proxy Enabled...............: No
    
Ethernet adapter Local Area Connection 2:

    Connection-specific DNS Suffix...:
    Desscription.....................: Red Hat VirtIO Ethernet Adapter
    Physical Address.................: 56-73-86-D5-82-68
    DHCP Enabled.....................: No
    IP Address.......................: 192.168.2.21
    Subnet Mask......................: 255.255.0.0
    Default Gateway..................: 192.168.0.1

During my research, I read this doc (http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge) where is stated that "multi-briged enviroment" requires stp protocol switched on. So, I setted it! And consequence has been as follows:


  • switched on guest VM, Proxmox Hypervisor ifconfig says:

    HTML: 
    root@proxmox:~# ifconfig -a

eth0      Link encap:Ethernet  HWaddr 00:0c:29:a7:fb:03
          inet6 addr: fe80::20c:29ff:fea7:fb03/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2932081 errors:0 dropped:0 overruns:0 frame:0
          TX packets:757602 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:592756804 (565.2 MiB)  TX bytes:209374092 (199.6 MiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1189248 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1189248 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:196843745 (187.7 MiB)  TX bytes:196843745 (187.7 MiB)

tap100i0  Link encap:Ethernet  HWaddr aa:ac:b4:7c:92:f5
          inet6 addr: fe80::a8ac:b4ff:fe7c:92f5/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:25545 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1371740 errors:0 dropped:0 overruns:501 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:2598781 (2.4 MiB)  TX bytes:147053124 (140.2 MiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet6 addr: fe80::1/128 Scope:Link
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vmbr0     Link encap:Ethernet  HWaddr 00:0c:29:a7:fb:03
          inet addr:192.168.5.254  Bcast:192.168.255.255  Mask:255.255.0.0
          inet6 addr: fe80::20c:29ff:fea7:fb03/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1837634 errors:0 dropped:0 overruns:0 frame:0
          TX packets:664914 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:214874080 (204.9 MiB)  TX bytes:203201381 (193.7 MiB)

    where "tap100i0" is the dynamic ethernet interface of guest;

  • the brctl says:

    HTML: 
    root@proxmox:~# brctl show

bridge name     bridge id               STP enabled     interfaces
vmbr0           8000.000c29a7fb03       yes             eth0
                                                        tap100i0

  • trying to ping gateway from guest VM, outpus is:

    HTML: 
    C:\>ping -r 192.168.0.1

Request time out.
Request time out.
...
...
Request time out.
Request time out.
Request time out.
Request time out.
Request time out.
Request time out.
Request time out.
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=6ms TTL=225
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=7ms TTL=225
Reply from 192.168.0.1: bytes=32 time<1ms TTL=225
Reply from 192.168.0.1: bytes=32 time<1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=2ms TTL=225
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Reply from 192.168.0.1: bytes=32 time=1ms TTL=225
Request time out.
Request time out.
Request time out.
Request time out.
Request time out.
Request time out.
...
...

    Hence, unstable.

  • and when ping states switch from "Request time out" to "Reply from..." and vice versa, the only difference I found is into brctl showstp. That is

    Output when brctl states "Request time out":

    HTML: 
    root@proxmox:~# brctl showstp vmbr0 

vmbr0
 bridge id              8000.000c29a7fb03
 designated root        8000.000c29a7fb03
 root port                 0                    path cost                  0
 max age                  19.99                 bridge max age            19.99
 hello time                1.99                 bridge hello time          1.99
 forward delay             0.00                 bridge forward delay       0.00
 ageing time             299.95
 hello timer               0.33                 tcn timer                  0.00
 topology change timer     0.00                 gc timer                   0.33
 flags


eth0 (1)
 port id                8001                    state                forwarding
 designated root        8000.000c29a7fb03       path cost                  4
 designated bridge      8000.000c29a7fb03       message age timer          0.00
 designated port        8001                    forward delay timer        0.00
 designated cost           0                    hold timer                 0.00
 flags

tap100i0 (2)
 port id                8002                    state                forwarding
 designated root        8000.000c29a7fb03       path cost                100
 designated bridge      8000.000c29a7fb03       message age timer          0.00
 designated port        8002                    forward delay timer        0.00
 designated cost           0                    hold timer                 0.00
 flags

    Output when brctl states "Reply from...":

    HTML: 
    root@proxmox:~# brctl showstp vmbr0 

vmbr0
 bridge id              8000.000c29a7fb03
 designated root        8000.000c29a7fb03
 root port                 0                    path cost                  0
 max age                  19.99                 bridge max age            19.99
 hello time                1.99                 bridge hello time          1.99
 forward delay             0.00                 bridge forward delay       0.00
 ageing time             299.95
 hello timer               1.31                 tcn timer                  0.00
 topology change timer    15.32                 gc timer                   0.31
 flags                  TOPOLOGY_CHANGE TOPOLOGY_CHANGE_DETECTED


eth0 (1)
 port id                8001                    state                forwarding
 designated root        8000.000c29a7fb03       path cost                  4
 designated bridge      8000.000c29a7fb03       message age timer          0.00
 designated port        8001                    forward delay timer        0.00
 designated cost           0                    hold timer                 0.31
 flags

tap100i0 (2)
 port id                8002                    state                forwarding
 designated root        8000.000c29a7fb03       path cost                100
 designated bridge      8000.000c29a7fb03       message age timer          0.00
 designated port        8002                    forward delay timer        0.00
 designated cost           0                    hold timer                 0.31
 flags

Any suggestion?

Before closing, I have to specify that eth0 is already briged by VMWare with physical ethernet interface of host.

Thank's for your attention.

Regards.
 
Hello to all readers,

maybe I've found something....

During my researches, I noticed strange behavior of bridging that is less unpredictable than what I described before.

Granted that topology of my enviroment is as follows:


HTML: 
+--- Host (WIN 7) -------------------------------------------------+
|                                                                  |
|   +--- 1st Hypervisor (VMWARE WORKST. 8) --------------------+   |
|   |                                                          |   |
|   |    +--- 2nd Hypervisor (PROXMOX) --------------------+   |   |
|   |    |                                                 |   |   |
|   |    |     +--- guest (WIN 2k3 SRV sp2) ---+           |   |   |
|   |    |     |                               |           |   |   |
|   |    |     |  +-------------------------+  |           |   |   |
|   |    |     |  | Virtio Ethernet         |  |           |   |   |
|   |    |     |  |.........................|  |           |   |   |
|   |    |     |  | MAC = 56:73:86:d5:82:68 |  |           |   |   |
|   |    |     |  | IP  = 192.168.2.21/16   |  |           |   |   |
|   |    |     +--+-------------------------+--+           |   |   |
|   |    |        | tap100i0                |              |   |   |
|   |    |        |.........................|              |   |   |
|   |    |        | MAC = ea:e3:1b:8e:7a:25 |              |   |   |
|   |    |        | IP  = null              |              |   |   |
|   |    |        +----------------------#--+              |   |   |
|   |    |                               |                 |   |   |
|   |    |                               |                 |   |   |
|   |    |                 #############################   |   |   |
|   |    |                 # vmbr0                     #   |   |   |
|   |    |                 #...........................#   |   |   |
|   |    |                 # MAC = 00:0c:29:a7:fb:03   #   |   |   |
|   |    |                 # IP  = 192.168.5.254/16    #   |   |   |
|   |    |                 #############################   |   |   |
|   |    |                               |                 |   |   |
|   |    |                               |                 |   |   |
|   |    |        +----------------------#--+              |   |   |
|   |    |        | eth0                    |              |   |   |
|   |    |        |.........................|              |   |   |
|   |    |        | MAC = 00:0c:29:a7:fb:03 |              |   |   |
|   |    |        | IP  = null              |              |   |   |
|   |    +--------+---------------(bridged)-+--------------+   |   |
|   |             | VMnet0                  |                  |   |
|   |             |.........................|                  |   |
|   |             | MAC = 00:0c:29:a7:fb:03 |                  |   |
|   |             | IP  = null              |                  |   |
|   +-------------+---------------(bridged)-+------------------+   |
|                 | LAN                     |                      |
|                 |.........................|                      |
|                 | MAC = 00-19-99-9B-59-23 |                      |
|                 | IP  = 192.168.2.52/16   |                      |
+-----------------+------------#------------+----------------------|
                               |
                               |
         0=================== LAN =======================0

I noticed that ping toward my guest works fine just until MACs TABLE of vmbr0 hasn't any entries for guest (VirtIO) ethernet interface MAC. In fact, if my vmbr0 STP is auto-configured as follow:

HTML: 
vmbr0
 bridge id              8000.000c29a7fb03
 designated root        8000.000c29a7fb03
 root port                 0                    path cost                  0

eth0 (1)
 port id                8001                    state                forwarding


tap100i0 (2)
 port id                8002                    state                forwarding

then, we have to keep in mind that STP recalculates its MACs TABLE every 3 minutes (by default). Therefore, its first step is deleting all TABLE MACs entries. There, from this moment on, any host connected to LAN can run a ping toward guest! But, ping ceases to work as soon as one entry about guest MAC is inserted!

I suppose it's because of STP inserts one wrong entry in MACs TABLE and, that is, a wrong port for forwarding ethernet traffics addressed to guest. In fact, if I search this entry I can found:


HTML: 
root@proxmox:~# brctl showmacs vmbr0 | grep 56:73:86

port no mac addr                is local?       ageing timer
  1     56:73:86:d5:82:68       no                20.51

So, all my ethernet traffic addressed to guest is forwarded to port 1. But, port 1 is eth0, andnot tap100i0 where resides my guest!!!

Question: how I can correct this error???????

Thank's for your attention.

Regards.
 
Rereading my last post, I noticed that I was wrong about topology of my enviroment. Follows correct:



HTML: 
+--- HARDWARE BOX -------------------------------------------------+
|                                                                  |
|    HOST (WIN 7)                                                  |
|    ^^^^^^^^^^^^                                                  |
|                                                                  |
|   +--- 1st Hypervisor (VMWARE WORKST. 8) --------------------+   |
|   |                                                          |   |
|   |    Middle GUEST (PROXMOX)                                |   |
|   |    ^^^^^^^^^^^^^^^^^^^^^^                                |   |
|   |                                                          |   |
|   |         +--- 2nd Hypervisor (KVM) ------+                |   |
|   |         |                               |                |   |
|   |         |    GUEST (WIN 2k3 SRV sp2)    |                |   |
|   |         |    ^^^^^^^^^^^^^^^^^^^^^^^    |                |   |
|   |         |                               |                |   |
|   |         |  +-------------------------+  |                |   |
|   |         |  | Virtio Ethernet         |  |                |   |
|   |         |  |.........................|  |                |   |
|   |         |  | MAC = 56:73:86:d5:82:68 |  |                |   |
|   |         |  | IP  = 192.168.2.21/16   |  |                |   |
|   |         +--+-------------------------+--+                |   |
|   |            | tap100i0                |                   |   |
|   |            |.........................|                   |   |
|   |            | MAC = ea:e3:1b:8e:7a:25 |                   |   |
|   |            | IP  = null              |                   |   |
|   |            +----------------------#--+                   |   |
|   |                                   |                      |   |
|   |                                   |                      |   |
|   |                     #############################        |   |
|   |                     # vmbr0                     #        |   |
|   |                     #...........................#        |   |
|   |                     # MAC = 00:0c:29:a7:fb:03   #        |   |
|   |                     # IP  = 192.168.5.254/16    #        |   |
|   |                     #############################        |   |
|   |                                   |                      |   |
|   |                                   |                      |   |
|   |            +----------------------#--+                   |   |
|   |            | eth0                    |                   |   |
|   |            |.........................|                   |   |
|   |            | MAC = 00:0c:29:a7:fb:03 |                   |   |
|   |            | IP  = null              |                   |   |
|   +------------+-------------------------+-------------------+   |
|                | VMnet0                  |                       |
|                |.........................|                       |
|                | MAC = 00:0c:29:a7:fb:03 |                       |
|                | IP  = null              |                       |
|                +----------------------#--+                       |
|                                       |                          |
|                                       |                          |
|                        #############################             |
|                        # Windows Bridge            #             |
|                        #############################             |
|                                       |                          |
|                                       |                          |
|                +----------------------#--+                       |
|                | LAN                     |                       |
|                |.........................|                       |
|                | MAC = 00-19-99-9B-59-23 |                       |
|                | IP  = 192.168.2.52/16   |                       |
+----------------+------------#------------+-----------------------+
                              |
                              |
        0=================== LAN =======================0

and I would like to add here a "bridging view" of this topology:

HTML: 
     ### Win$ Bridge #######      ### vmbr0 ###############       +- GUEST ---+ 
     #                     #      #                       #       |           |
     #    LAN      VMnet0  #      #    eth0     tap100i0  #       |   VirtIO  |
     #### 
[*] #### 
[*] #####      #### 
[*] #### 
[*] #######       +-- 
[*] ----+
           |        |                   |        |                     |
           |        +-------------------+        +---------------------+
           |
           |
0======== LAN =======================0

Here, it's plain one bit difference of Ethernet Interface Virtualization between VMWare and ProxMox/KVM:

  • first one keep MAC address on both eth-interf of guest OS and its virtual interface (VMnet0/eth0);
  • second one give different MAC address on its virtual interface (tapXXX) and on eth-interf of guest OS (VirtIO).
Could it be concern with my issue?

Thank's for your attention.

Regards.
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back