Hi Boris, I believe what is being referred to which of the servers' own ips to listen at / bind to, it is not for access control (apart from if you have internal vs external networks). 127.0.0.1 refers to a non network reachable 'localhost' ip. Setting the bind host name to that servers external ip(s?) would allow anyone who is able to 'reach' that ip address connect.
Best Regards, Joe On Fri, Aug 21, 2009 at 1:19 PM, Boris <[email protected]> wrote: > > Thx Anthony. > Is this just a temporary development solution? Shouldn't *any* client > be able to connect to the server? Is there any special reason (except > that it is done like that now) why the server should bind one single > client (- be aware of clients before they connect?) ? Sounds like an > exchange server binding to one single workstation in the company > network ;) > > On Aug 21, 12:40 am, Jochen Bekmann <[email protected]> wrote: > > The following two flags in run-server.sh set which address and port > > the *server binds to*: > > --client_frontend_hostname=127.0.0.1 \ > > --client_frontend_port=9876 \ > > > > If the server binds on 127.0.0.1 you will only be able to connect to > > it from the same machine. Change this address to an address routable on > > your network and your client should be able to connect. > > > > On Fri, Aug 21, 2009 at 3:34 AM, Boris<[email protected]> wrote: > > > > > Hm.. I am sorry if I maybe missed an important point here: > > > > > When running the client on my server machine everything works > > > perfectly, running several clients at once. But when I run the client > > > on another machine, I can not connect with the same user information. > > > Tried everything from u...@localhost to u...@ip, u...@hostname,... > > > Is this simply not possible? Why? > > > From my understanding, the client-server protocol doesn't mind from > > > where it is connected to where... but with this assumption, I don't > > > get the meaning of the "client_frontend_hostname" - why should the > > > server be aware of *one* client host name? . (port is perfect - but > > > there could multiple clients connecting from very different machines?) > > > > > thank you for any information on this topic > > > > > --- > > > Boris > > > > > On Aug 10, 4:48 am, Anthony Baxter <[email protected]> wrote: > > >> You need to use an address that belongs to the host you're running it > > >> on. Unless you're running it on one of our boxes (which would be > > >> suprising!) your machine's name is not primary.initech-corp.com. > > > > >> Anthony > > > > >> On Fri, Aug 7, 2009 at 12:54, [email protected]<[email protected]> > wrote: > > > > >> > I am running into a similar problem. localhost works fine, but the > > >> > FQDN does not. > > > > >> >> You can't use primary.initech-corp.com, as that's not an address > your > > >> >> host supports. The easiest one to use is 127.0.0.1, that will work > on > > > > >> > So what do you mean by "not an address your host supports". I can > ping > > >> > it fine, > > >> > and can access other services on my host by using its FQDN. What > > >> > gives? > > > > >> > -g > > > > >> -- > > >> Anthony Baxter, [email protected] > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
