Bonjour and virtual servers?

[hambleto]

I have tried both Ubunto and Centos as containers and both of them fail to start/share Bonjour information. Is this possibly related to being virtualized or should I continue down the OS path?
Thank you,
Ben

 

[tlphipps]

I'm not 100% sure, but it may have to do with IPv6 being enabled on the proxmox host. I know that some of the JAVA based tivo server apps out there (galleon, harmonium) have broadcast issues when IPv6 is enabled. They use the Bonjour protocol (or something similar).

I've been wanting to disable IPv6 on my proxmox host to test, but that requires a reboot, and I just haven't found the time to take down all my VMs to test that.

 

[hambleto]

Where would you check to see if ipv6 is enabled on the node itself?

 

[tlphipps]

Proxmox VE has it enabled by default, so if you didn't disable it, it's turned on. You can verify it by doing a ifconfig at the commandline. Just look for a line that gives the inet6 address. If you see that line, IPv6 is enabled.

 

[hambleto]

It looks to be enabled on tap2, l0, eth0, and vmbr.

How hard is it to disable and is it safe to do so? Would it effect the function of the node, containers, or future upgrades?

 

[tlphipps]

I've never done it on debian (base of proxmox VE), so I'm not entirely sure. In redhat/centos you just disable a module or two in your loading sequence. Pretty simple change, but requires a reboot.

I can't comment on any effect it might have on Proxmox VE as I'm unsure and have not actually done it myself yet.

 

[odd]

It looks to be enabled on tap2, l0, eth0, and vmbr.

How hard is it to disable and is it safe to do so? Would it effect the function of the node, containers, or future upgrades?

Well i don´t know, but my guess is that it would not effect anything
unless you use it in you containers, maybe someone else can answer better.

 

[hambleto]

I am thinking the same thing. However since we have 3 nodes linked together, I want to know for sure before I break something. I am hoping the developers might chime in with their recommendations/thoughts.
Thank you again,
Ben

 

[dietmar]

Please tell me how to reproduce the bug first (and what is Bonjour and why do you want to use it (the network is already configured with containers))? What kind of network does you container use?

- Dietmar

 

[hambleto]

Dieter,
Bonjour is another name for Zero Configuration Networking. I have a specific linux application that advertises itself to the network via Bonjour. Networking is working fine in the container, however when Bonjour goes to start it just fails and the messagesbus won't start. This occurs in both Centos and Ubuntu.
Thank you,
Ben

 

[martin]

Dieter,
Bonjour is another name for Zero Configuration Networking. I have a specific linux application that advertises itself to the network via Bonjour. Networking is working fine in the container, however when Bonjour goes to start it just fails and the messagesbus won't start. This occurs in both Centos and Ubuntu.
Thank you,
Ben

pls give detailed setup instructions how we can reproduce this.

 

[dietmar]

Do you use 'bridged' network mode?

 

[hambleto]

Just create a standard centos-5-standard_5-1 container.
Log into it.
start the messages bus: /etc/init.d/messagebus start

It will not start. It will create the pid but that is all. I have tied this on three nodes with the same effect. It does not even generate any info in the dmesg log.
Thank you,
Ben

 

[hambleto]

I am using venet

 

[dietmar]

I am using venet

I guess that protocol uses level2 broadcast features, so it will never work with routed venet - try bridged network instead.

- Dietmar

 

[hambleto]

Do you have a guide on setting that up? Rather than I stumble through blindly?
Thank you,
Ben

 

[dietmar]

You can select the network type when you create the container. Just select 'Bridged Ethernet (veth)'.

The whole network setup needs to be done manually inside the container, like configuring a physical machine.

- Dietmar

 

[hambleto]

Now would I need to have a seperate physical ethernet device enabled on the node (ie eth1) then bridged? Or does the bridge still work on a single ethernet device (ie vmbr0 which I believe goes to eth0)?
Thank you again,
Ben

 

[dietmar]

just use vmbr0

 

[tlphipps]

No additional NIC needed in host. Bridge works just fine with one NIC (eth0).

Sorry for failing to mention this requirement before. But as I said, just setting up a bridge won't solve this issue.