Re: binding to particular IP on multi-ip machine failed with 2.2.0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This worked in 2.0.9 and we are still using pretty much the same calls
to PWLib. How come this broke ?

Since we don't do anything special for FreeBSD, is this broken on other
Unix versions as well ?


Aivis Olsteins wrote:
> Hi,
> 
> yes, it is FreeBSD 4.10
> 
> regards, Aivis
> 
> Zygmuntowicz Michal wrote:
> > Is it FreeBSD system? I noticed, that 2.2 has problems
> > on FreeBSD with aliased interfaces.
> > 
> > ----- Original Message ----- From: "Aivis Olsteins" 
> > <aivis@xxxxxxxxxxxxxxxx>
> > Sent: Thursday, December 02, 2004 11:45 PM
> > 
> > 
> >> I was just trying to set gnugk 2.2.0 on machine with multiple IP
> >> addresses (for multi-gk setup) to bind to particular IP address.
> >> However, all possible configurations always ended up with gnugk
> >> listening to machine's default Ip address AND localhost address.
> >>
> >> Example:
> >> machine default address: 10.0.0.1
> >> aliases:                 10.0.0.2 and 10.0.0.3
> >>
> >> we want particular gnugk instance to listen to 10.0.0.2
> >>
> >> config is like this:
> >>
> >> [Gatekeeper::Main]
> >> Fourtytwo=42
> >> Name=gnugk
> >> StatusPort=7000
> >> Home=10.0.0.2
> >> NetworkInterfaces=10.0.0.2/32
> >> UseBroadcastListener=0
> >>
> >> it gives following debug at startup:
> >> 2004/12/02 22:21:27.587 2          singleton.cxx(28)    Create 
> >> instance: Toolkit(1)
> >> 2004/12/02 22:21:27.587 5            Toolkit.cxx(592)   Try name 
> >> /tmp/gnugk.ini-2052
> >> 2004/12/02 22:21:27.589 4            Toolkit.cxx(113)  
> >InterfaceTable:> 10.0.0.1 (sis0)
> >> 127.0.0.1 (lo0)
> >>
> >> 2004/12/02 22:21:27.591 2            Toolkit.cxx(83) 
> >> Network=10.0.0.0/255.255.255.0, IP=10.0.0.1
> >> 2004/12/02 22:21:27.591 2            Toolkit.cxx(83) 
> >> Network=10.0.0.1/255.255.255.255, IP=10.0.0.1
> >> 2004/12/02 22:21:27.591 2            Toolkit.cxx(83) 
> >> Network=10.0.0.3/255.255.255.255, IP=10.0.0.1
> >>
> >> .... and so on for all interfaces on machine, then localhost....
> >>
> >> 2004/12/02 22:21:27.591 2            Toolkit.cxx(83) 
> >> Network=127.0.0.1/255.255.255.255, IP=127.0.0.1
> >>
> >> 2004/12/02 22:21:27.592 2            Toolkit.cxx(84)    Default 
> >> IP=10.0.0.1
> >> 2004/12/02 22:21:27.594 2            Toolkit.cxx(83) 
> >> Network=0.0.0.0/0.0.0.0, IP=10.0.0.2
> >> 2004/12/02 22:21:27.594 2            Toolkit.cxx(84)    Default 
> >> IP=10.0.0.2
> >> 2004/12/02 22:21:27.591 2            Toolkit.cxx(83) 
> >> Network=63.208.156.113/255.255.255.255, IP
> >>
> >> so it kind of detects Home address, but also detects all other
> >> addresses on machine and decides to listen to main and localhost:
> >>
> >> 2004/12/02 22:21:27.601 1             RasSrv.cxx(471)   Listening
> >to > 10.0.0.1:1719(U)
> >> 2004/12/02 22:21:27.601 5           yasocket.cxx(670)   RasServer 
> >> total sockets 1
> >> 2004/12/02 22:21:27.602 1             RasSrv.cxx(471)   Listening
> >to > 10.0.0.1:1718(Mcast)
> >> 2004/12/02 22:21:27.602 5           yasocket.cxx(670)   RasServer 
> >> total sockets 2
> >> 2004/12/02 22:21:27.602 1             RasSrv.cxx(471)   Listening
> >to > 10.0.0.1:1720
> >> 2004/12/02 22:21:27.602 5           yasocket.cxx(670)   TCPServer 
> >> total sockets 1
> >> 2004/12/02 22:21:27.602 1             RasSrv.cxx(471)   Listening
> >to > 10.0.0.1:7000
> >> 2004/12/02 22:21:27.602 5           yasocket.cxx(670)   TCPServer 
> >> total sockets 2
> >> 2004/12/02 22:21:27.602 1             RasSrv.cxx(471)   Listening
> >to > 127.0.0.1:1719(U)
> >> 2004/12/02 22:21:27.602 5           yasocket.cxx(670)   RasServer 
> >> total sockets 3
> >> 2004/12/02 22:21:27.602 1             RasSrv.cxx(471)   Listening
> >to > 127.0.0.1:1720
> >> 2004/12/02 22:21:27.602 5           yasocket.cxx(670)   TCPServer 
> >> total sockets 3
> >> 2004/12/02 22:21:27.602 1             RasSrv.cxx(471)   Listening
> >to > 127.0.0.1:7000
> >> 2004/12/02 22:21:27.602 5           yasocket.cxx(670)   TCPServer 
> >> total sockets 4
> >>
> >>
> >> Anyone has idea how to make it listen to "home" only? Needless to
> >say,> that till 2.0.9 it worked as expected
> >>
> >> regards, Aivis
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real
> > users. Discover which products truly live up to the hype. Start
> > reading now. http://productguide.itmanagersjournal.com/
> > 
> > _______________________________________________________
> > 
> > List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
> > Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
> > Homepage: http://www.gnugk.org/
> > 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real
> users. Discover which products truly live up to the hype. Start
> reading now. http://productguide.itmanagersjournal.com/
> 
> _______________________________________________________
> 
> List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
> Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
> Homepage: http://www.gnugk.org/
> 


-- 
Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.willamowius.de/


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

_______________________________________________________

List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux