Re[2]: [Openh323gk-developer] Home addresses after reload
H.323 Gatekeeper for VoIP and videconferencing
Brought to you by:
willamowius
From: Thomas <th...@ew...> - 2004-04-29 17:01:11
|
Ah, sorry. I had in my mind to write also, that I'm not using Home option, unfortunately I forgot :( So, I'm not using Home config setting. Regards, Tomi Thursday, April 29, 2004, 1:49:12 PM, Zygmuntowicz wrote: ZM> I assume you are not using Home= config setting? If not, it may look ZM> like a bug and I'll see what is wrong. ZM> ----- Original Message ----- ZM> From: "Thomas" <th...@ew...> ZM> Sent: Wednesday, April 28, 2004 5:03 PM >> I have a child-parent gatekeeper configuration. The child GK box is on >> a dynamic IP DSL connection. When the IP address changes, I issue a >> reload command on child GK. However it somehow doesn't recognize well >> the new IP address. I need to completely restart (stop, start) GK to >> handle this problem. >> This method worked well for long time. Unfortunately I don't know when >> this problem came into picture, so don't know from which version of >> gnugk this problem was introduced. (I have a feeling, that it doesn't >> work well from time I upgraded to 2.2CVS version - but not sure). >> >> Here is a log after a reload on a changed IP (2.2 CVS - today). >> (old IP was: 81.182.173.184, new: 81.182.173.207) >> >> Thanks in advance, >> Thomas >> >> ps: gnugk is sitting on a Debian Woody box, kernel 2.4.26, pwlib-1.6.5, openh323-1.13.3 >> >> 2004/04/28 12:44:57.175 4 Toolkit.cxx(112) InterfaceTable: >> 127.0.0.1 <00-00-00-00-00-00> (lo) >> 192.168.254.100 <00-40-63-D3-8C-E7> (eth0) >> 81.182.173.207 <00-00-00-00-00-00> (ppp0) >> >> 2004/04/28 12:44:57.176 2 Toolkit.cxx(82) >> Network=145.236.238.132/255.255.255.255, IP=81.182.173.207 >> 2004/04/28 12:44:57.176 2 Toolkit.cxx(82) >> Network=192.168.254.0/255.255.255.0, IP=192.168.254.100 >> 2004/04/28 12:44:57.176 2 Toolkit.cxx(83) Default IP=81.182.173.207 >> 2004/04/28 12:44:57.176 2 Toolkit.cxx(155) GK H.323 Proxy enabled >> 2004/04/28 12:44:57.177 2 Toolkit.cxx(168) GK >> Internal Network 0 = 192.168.254.0/255.255.255.128 >> 2004/04/28 12:44:57.177 2 Toolkit.cxx(398) GK Loaded per GW rewrite data: >> 2004/04/28 12:44:57.177 2 Toolkit.cxx(401) GK No per GW data loaded >> 2004/04/28 12:44:57.177 2 ProxyChannel.cxx(76) Q931PortRange: 50000-50024 >> 2004/04/28 12:44:57.177 2 ProxyChannel.cxx(76) H245PortRange: 50025-50049 >> 2004/04/28 12:44:57.178 2 ProxyChannel.cxx(76) T120PortRange: 49999-50000 >> 2004/04/28 12:44:57.178 2 ProxyChannel.cxx(76) RTPPortRange: 50000-50049 >> 2004/04/28 12:44:57.178 2 RasSrv.cxx(677) GK Using Routed Signalling >> 2004/04/28 12:44:57.178 2 RasSrv.cxx(678) GK H.245 Routed Enabled >> 2004/04/28 12:44:57.178 2 RasSrv.cxx(714) GK >> Home = 81.182.173.184,192.168.254.100,127.0.0.1 >> ... >> 2004/04/28 12:44:57.627 3 RasSrv.cxx(201) RAS Send to <maingkip>:1719 >> registrationRequest { >> requestSeqNum = 13 >> protocolIdentifier = 0.0.8.2250.0.2 >> nonStandardData = { >> nonStandardIdentifier = object (NULL) >> data = 17 octets { >> 49 50 3d 38 31 2e 31 38 32 2e 31 37 33 2e 31 38 IP=81.182.173.18 >> 34 4 >> } >> } >> discoveryComplete = TRUE >> callSignalAddress = 1 entries { >> [0]=ipAddress { >> ip = 4 octets { >> 51 b6 ad b8 Q... >> } >> port = 1721 >> } >> } >> rasAddress = 1 entries { >> [0]=ipAddress { >> ip = 4 octets { >> 51 b6 ad b8 Q... >> } >> port = 1719 >> } >> } >> ... >> 2004/04/28 12:44:57.637 4 RasSrv.cxx(217) RAS Write error: Invalid argument |