{ Patch } SmartFoxServer PRO 1.5.8c ready

Post by **Lapo** » 03 Oct 2007, 16:02

If you first start the webserver and then SFS you shouldn't get any conflicts.
SFS will bind only on ports that are not bound yet.
So if you have two cards (eth0, eth1) and eth0 is already bound on port 80, SFS will bind on eth1

FunTime · Post by **FunTime** » 03 Oct 2007, 20:24

So it will only bind to and interface that is free, but not multiple IP on the same interface?

I haven't looked yet, I do know however that if I have more then one IP on the same interface, it will not bind to IP's on that interface if any of them have the port I want SFS to use...

Like I have (for example) on eth0:
10.0.0.1
10.0.0.2
10.0.0.3

and my web server only binds only to 10.0.0.1 SFS will not bind to the same port 10.0.0.2 or 10.0.0.3.

But your saying that if I had (for example) on eth2:
10.1.0.1
10.1.0.2
10.1.0.3

that it would bind to them as long as nothing else was?

FunTime · Post by **FunTime** » 03 Oct 2007, 20:25

I know for a fact my first example doesn't work, I'll try the second one in a bit. (Just got back from shopping)

FunTime · Post by **FunTime** » 08 Oct 2007, 19:33

Sorry for the long delay, but I finally got around to more testing, and it seems to me if anything is bound on the same port as SFS, no matter how many other IPs or interfaces you have, SFS will not load, even with the ability to bind to the other address/interfaces that do have that port free, IMHO this is really kind of a step backwards from the way it worked before.

I still beleave a more detailed connection block would work better, instead of binding to all, let you set what address and ports you want it to bind to is way better, and more flexable as well.