Multicast when IP is released and renewed
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Alison_Kakoschke
Posted On:   Tuesday, October 8, 2002 02:56 AM

Hi Andreas Just wondering if you could help us on something we have noticed ... Our system has dynamic IPs. We have a monitoring tool that checks when this is the case and then updates the multicast connections in the swiftmq router accordingly (in code through cli). This works fine. However, we have tried a scenario where we are relasing and renewing the IP address. When we relase the IP address, it sets to the local host and when we renew, it is set back to what it was before the release. This all happens very quickly and so is not picked up by our IP monitoring tool. Hence, the multicast connection is not recreated in swiftMQ. We then try sending messages over the multi   More>>

Hi Andreas


Just wondering if you could help us on something we have noticed ...


Our system has dynamic IPs. We have a monitoring tool that checks when this is the case and then updates the multicast connections in the swiftmq router accordingly (in code through cli).


This works fine. However, we have tried a scenario where we are relasing and renewing the IP address. When we relase the IP address, it sets to the local host and when we renew, it is set back to what it was before the release. This all happens very quickly and so is not picked up by our IP monitoring tool. Hence, the multicast connection is not recreated in swiftMQ.


We then try sending messages over the multicast connection. The machine on which the IP was released and renewed can send messages but does not receive them. However, if the multicast connection is recreated (with the same interface address) then everything works fine once again.


My questions are


1. Is this expected behaviour?


2. What can we do (if anything) to solve this problem?


Thanks in advance


Alison Kakoschke

   <<Less

Re: Multicast when IP is released and renewed

Posted By:   Andreas_Mueller  
Posted On:   Tuesday, October 8, 2002 03:11 AM

That's difficult. You must log somewhere (e.g. from a separate process) that the IP has changed and then you can react properly. Without such info I don't see a way to restart the multicast connection.
About | Sitemap | Contact