[INUG-Users] Objectserver only able to listen to ONE SINGLE interface`??

[Gerhard Holzer]

Thank you all,

the first server is now listening on both interfaces and I'm sure connecting
to teach of hem would work from
different clients on different networks.

kind regards

gerhard


2007/8/2, Alex Greenbank <agreenbank at uk.ibm.com>:
>
>
> Hello,
>
> users-bounces at netcoolusers.org wrote on 01/08/2007 20:37:52:
> >
> > I'm really wondering.
> > Nearly any UNIX process listening to a port is listening to ALL
> > interfaces (IP addresses) if not restricted to one (some).
> >
> > No matter if it's inetd, syslogd or any httpd.
> >
> > Omnibus objectserver is only able to listen to one single interface.
>
> No, it can listen to multiple.
>
> > Anybody ever found any trick to makeit available on more than one
> interface?
> > Any piece of software to achieve that?
>
> Take a look at the interfaces file. There are two types of lines in the
> file
> for each entry:-
>
> "master" lines are used by the servers (nco_objserv, nco_gate, nco_pad,
> nco_proxyserv) to work out which interfaces and ports to listen on.
>
> "query" lines are used by any client to connect to that server. Each query
> line is tried, in order, until a connection is made.
>
> So while putting an address of 0.0.0.0 will make the ObjectServer listen
> on all available interfaces. A "query" line with an IP address of 0.0.0.0
> isn't a good idea as none of the clients can connect via that address.
>
> Taking the simplest entry in omni.dat:-
>
> [EXAMPLE]
> {
>         Primary: devtest4 1234
> }
>
> becomes this in the interfaces.solaris2 file:-
>
> # EXAMPLE => devtest4 1234
> EXAMPLE
>         master tcp ether devtest4 1234
>         query tcp ether devtest4 1234
>
> What if this machine actually had two interfaces (10.1.1.1 and 192.168.1.4)
> and you wanted to make it listen on both:-
>
> [EXAMPLE]
> {
>         Primary: 10.1.1.1 1234
>         Backup: 192.168.1.4 1234
> }
>
> # EXAMPLE => 10.1.1.1 1234
> EXAMPLE
>         master tcp ether 10.1.1.1 1234
>         query tcp ether 10.1.1.1 1234
>         master tcp ether 192.168.1.4 1234
>         query tcp ether 192.168.1.4 1234
>
> For clients that connected from machines on the 192.168.1.x network you'd
> obviously have an omni.dat/interfaces file on that machine which only
> specified the 192.168.1.4 address.
>
> Note that you can have multiple backup lines if you have more than two
> interfaces:-
>
> [EXAMPLE]
> {
>         Primary: 10.1.1.1 1234
>         Backup: 192.168.1.4 1234
>         Backup: 1.2.3.4 1234
> }
>
> gives:-
>
> # EXAMPLE => 10.1.1.1 1234
> EXAMPLE
>         master tcp ether 10.1.1.1 1234
>         query tcp ether 10.1.1.1 1234
>         master tcp ether 192.168.1.4 1234
>         query tcp ether 192.168.1.4 1234
>         master tcp ether 1.2.3.4 1234
>         query tcp ether 1.2.3.4 1234
>
> This leads on to how failover pairs are created:-
>
> OBJ_PRI
>        master tcp ether machine_a 1234
>        query tcp ether machine_a 1234
>
> OBJ_SEC
>        master tcp ether machine_b 1234
>        query tcp ether machine_b 1234
>
> The above two define how the ports for the ObjectServers to listen on, and
> how to connect to them individually.
>
> You then define a new entry for the failover ObjectServer with just the
> query lines:-
>
> OBJ_PAIR
>         query tcp ether machine_a 1234
>         query tcp ether machine_b 1234
>
> No master lines are required (although it doesn't hurt if they are there)
> because you'll never run an ObjectServer called OBJ_PAIR as it is "virtual".
>
> Hope this helps,
>
> Ta,
>
> -Alex
>
>
> ------------------------------
>
> *
> *
>
> *Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
> *
>
>
>
>
>
>
>
> _______________________________________________
> Sent by the netcoolusers.org "users" mailing list
> Post: users at netcoolusers.org
> Unsubscribe: users-unsubscribe at netcoolusers.org
> Search: http://lists.netcoolusers.org/archives/users/
>
>
-------------- next part --------------
HTML attachment scrubbed and removed