mbo
13-05-11, 14:57
Hi,
for some time I was loosing my internet connection so I couldn't get anywhere but then all was working again. I tought my modem (bridged router) was on it's way out. However on the third occasion I had more closer look and noticed that my connection is alive but outgoing trafic is maxed. Using Wireshark I've found that the flood is comming from my VuDuo box... On packet inspection I've found it has Mgcamd in it. Well, I stopped the softcam and the internet start working perfectly. Right, time to see what is in the config file which I think I got from the net some time ago.
At the L entry (log options) I had some 176.x.x.x /var/etc at option 3 or 4 (don't remember now) and this address was in the config file already, not put by me. I disabled the loging and all is working fine. I don't know if the floding was because the cam tried to write logs to some unknown location or in fact there is a problem with mgcamd logging.
Anyway, it is worth to check what you got in your config file...
Cheers
for some time I was loosing my internet connection so I couldn't get anywhere but then all was working again. I tought my modem (bridged router) was on it's way out. However on the third occasion I had more closer look and noticed that my connection is alive but outgoing trafic is maxed. Using Wireshark I've found that the flood is comming from my VuDuo box... On packet inspection I've found it has Mgcamd in it. Well, I stopped the softcam and the internet start working perfectly. Right, time to see what is in the config file which I think I got from the net some time ago.
At the L entry (log options) I had some 176.x.x.x /var/etc at option 3 or 4 (don't remember now) and this address was in the config file already, not put by me. I disabled the loging and all is working fine. I don't know if the floding was because the cam tried to write logs to some unknown location or in fact there is a problem with mgcamd logging.
Anyway, it is worth to check what you got in your config file...
Cheers