General Questions

[but I'm not sure maybe there is something to be configured in m0n0wall I did not see...]

Dear m0n0wall community,

My problem is quite complex, so I decided to make a schema instead of trying crazy not-understandable explanations

Tests made with the different devices configurations are explained in the frames of the devices + more detailed explanations in the red frame.

The problem seems to be actually related to the Proxmox virtual switch (see other interesting tests results in the red frame) --- but I'm not sure maybe there is something to be configured in m0n0wall I did not see...

In addition to the schema, ntop did not show strange amount of broadcast and ifconfig and its BSD equivalent didn't show error/dropped/overruns on the physical / virtual NIC and virtual switches.

If someone has patience to look at this... I already thank them a lot

The m0n0wall default config is untouched (except of course when described in the schema)

I already consulted 2 networks and linux specialist but only answer I had was "yeah, should work!" ...

Forgot one point, tested with the ISO installation and the VMWare disk.

Fabien,
Excellent diagram! I don't have a lot of ideas as to what could cause your problems, but my guess is a switch config somewhere, either with the physical or virtual switches. Are there any extra cables (physical or virtual) that could be causing a switching loop? A loop seems to describe the symptoms you've been having. Is vmbr0 possibly acting as a router (or "layer 3 switch")?

Thanks very much for your great knowledge.

_____________________
ผลบอล-sbobet-คาสิโนออนไลน์-gclub

Thank you iridris for your reply.

I also think somehow the virtual switches aren't acting ONLY like basic switches... as problem doesn't appear with physical hardware. I made some researches about the Proxmox switches but I did not find concrete info. Otherwise, I also thought about some loop and investigated in this direction, but I did not find anything. Proxmox core server doesn't seem to be able to access vmbr0... but maybe there is something "hidden"

Thanks again anyway for your replies guys, I appreciate a lot. m0n0wall community seems very open, even to people like me who aren't network and BSD experts

Last word: m0n0wall is really great!

What's really tricky when you want to investigate the network virtualization in Proxmox is that:
- As all Linux based system, you think it should use open vswitch
- On the homepage of open vswitch is also said: It is the default switch in ......., Proxmox VE and VirtualBox
- But... some people ask "Anyone tried to install open vswitch ?" on the forum (post from this year ! )
- Nothing concrete in the documentation
- Many questions related to switches aren't answered...

BUT, in the end, it really looks it is a open vswitch related issue because I reproduced the same problem with a virtualbox under ubuntu. Even ubuntu itself needed to have the virtualbox online to have access to internet, and result was the same: it works fine for few minutes only...

Next step: to test with the free VMWare ESX, but it is hell to find some compatible NICs (they don't support) most of the realtek chips oO )

I am also wondering if the default config in interfaces file in proxmox is good for what I want to do:
    bridge_stp off
    bridge_fd 0

but it looks standard config for current linux distros...

I am also wondering if the default config in interfaces file in proxmox is good for what I want to do:
    bridge_stp off
    bridge_fd 0

but it looks standard config for current linux distros...

I'm assuming "bridge_stp" is Spanning Tree? I believe you would want that off - assuming there aren't any network loops. I'll also assume that "bridge_fd" is Full Duplex, but what "0" means is anyones guess. I would imagine that you do want full duplex - so you may want to check documentation to verify the meaning of that command and its setting.

I'm kind of intrigued by this Proxmox... I'll look into it if I have the time.

Hello iridris,

Sorry for the very late answer, I think I missed your reply.

As the symptoms according to your 1st reply could be caused by a network loop, I was wondering if it would make sense to try to change these 2 options...

I will also try this week VMWare, but it is hell to find compatible NIC with the free version.

Currently I am working on other topics, but I will tell you my discoveries (if some...)

m0n0wall seems very happy: as I had to remove the virtualization platform, he runs alone on this with 4GB RAM http://www.ldlc.com/fiche/PB00120170.html Unfortunately, my boss doesn't find this funny too...