@Sebastian-Roth

Thank you. I’m going to try to get my hands on a sever and a few routers to try this in a real environment and not a virtual one. I think this is giving me issues.

But i’m still not sure on what address fog multicasts? Is this a fixed address? or based on your current subnet? can i find it anywhere in the config files? I know the trunk version let’s you chose the multicast address but i’m having other troubles with that version + a friend of mine got this version perfectly working in his business environment so i want to atleast try to get this working.

@Quazz

Don’t seem to have that option.

@Quazz

Where could i change the multicast adress? Haven’t seen it anywhere in the options.

Is it possible to change the multicast adress of fog somewhere? to something different then 224.0.0.1 ?

@Yamakazi

Alright it seems it has something to do with multicasting groups not properly reporting to eachother.

When fog starts a multicast session it send to 224.0.0.1 but it stops there and doesn’t get forwarded to other clients in different subnets
*

When in the same subnet, It manges to request to join that specific multicast group get the data en then again leaves the mcast group.
Though it’s doing this directly with the fog server and not trough the general 224.0.0.1 which normally request host to join or leave a group.
*

I know this is maybe not that fog related anymore, but we came this far already

Hosts in a different vlan listen to 224.0.0.1 to report their status. For example
*

@Sebastian-Roth

UDP running
*

This is to different vlan. Is it normal it broadcasts to 224.0.0.1? Because i see in wireshark it doesn’t get further than the first router it encounters on 224.0.0.1 (see pic a few posts back)
*

To the same subnet multicast is working properly.
*

Was also able to clear mysql database but to no avail.

I already tested the setup in the same subnet and that works. I’m just don’t seems to get it to work on different subnets.

How does fog multicast? to which multicast address? Does it make a multicast address and lets clients join it? or is it a set multicast address? Because it’s sending to 224.0.0.1 atm, which seems a bit weird.

From one of the wiki pages of fog it makes you check these files.

“Check the MySQL details in “/opt/fog/service/etc/config.php” are correct.
If not, correct them (they should be the same as in /var/www/fog/commons/config.php) and restart the service”

*

this can’t be right. There is not much in the first config.php file and the 2nd under commons doesn’t even exist.

I Made a new very basic setup with just the fog server a router and a host. I configured the router to allow multicast.

I get the same result, everything is working: dhcp, unicast etc. Just not multicast. So i think fog is causing the problems. I’m just really lost what is wrong. FOGMulticastmanger is active and working, the multicast settings in the webinterface are all correct. Dhcp and the image are working fine. Mysql still remains a mystery to me though. I’ve got no experiecne with it on linux so.

@Quazz

hmmm it keeps giving these syntax errors

i also tried troubleshooting by sending an udp packet as explained in link text

And i the same subnet it is working. When i try it with a client in a different subent i get this

The udp packet seems to stop there.

@Wayne-Workman

I did a fresh install and managed to get multicast working in the same subnet but not in different vlans.
This is what i get when i’m in the database excuting those commands.

The .fogsettings file seems to be empty?
Config file is below