Re: [Freeciv-Dev] Do you want the application “freeciv-server” to accept incoming network connections?
On 2014 Jan 12, at 3:16 AM, Jacob Nevins 0jacobnk.fc...@chiark.greenend.org.uk wrote: You might have hoped that with the move to 2.4, OS X's firewall would have become *less* fussy, since locally spawned servers should now only listen on the localhost interface http://gna.org/bugs/?18530. Perhaps it has unexpectedly become more fussy as a result of this change in Freeciv -- which behaviour does 2.3 on 10.8 have, if it's easy to test? Sorry i didn't get back to you right away. It turns out i still had a .deb file of 2.3.4, and i re-installed that. The result: the security requester popped up when i loaded a saved game, but it didn't come back when i quit and restarted/reloaded. sent from Mountain Lion Paula: What's that? Blank Reg: It's a book! Paula: Well, what's that? Blank Reg: It's a nonvolatile storage medium. It's very rare, you should have one. Paula: Stuff it! ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
Re: [Freeciv-Dev] Do you want the application “freeciv-server” to accept incoming network connections?
On 2014 Jan 12, at 3:16 AM, Jacob Nevins 0jacobnk.fc...@chiark.greenend.org.uk wrote: You might have hoped that with the move to 2.4, OS X's firewall would have become *less* fussy, since locally spawned servers should now only listen on the localhost interface http://gna.org/bugs/?18530. Perhaps it has unexpectedly become more fussy as a result of this change in Freeciv -- which behaviour does 2.3 on 10.8 have, if it's easy to test? As an addendum, here's some data to chew on - from netstat. Summary: 2.4 initializes an additional IPv6 socket compared to 2.3. Is this expected behavior? With freeciv-2.3.4 Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp6 0 0 localhost.freeciv localhost.51436ESTABLISHED tcp6 0 0 localhost.51436localhost.freeciv ESTABLISHED tcp4 0 0 *.freeciv *.*LISTEN tcp6 0 0 *.freeciv *.*LISTEN With freeciv-2.4.0 Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp6 0 0 localhost.5557 localhost.51623ESTABLISHED tcp6 0 0 localhost.51623localhost.5557 ESTABLISHED tcp6 0 0 localhost.5557 *.*LISTEN tcp4 0 0 localhost.5557 *.*LISTEN tcp6 0 0 localhost.5557 *.*LISTEN sent from Mountain Lion Zik-Zak Announcer: Zik-Zak... We make everything you need and you need everything we make. ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
Re: [Freeciv-Dev] Do you want the application “freeciv-server” to accept incoming network connections?
On 17 January 2014 18:54, David Lowe doctorjl...@earthlink.net wrote: On 2014 Jan 12, at 3:16 AM, Jacob Nevins 0jacobnk.fc...@chiark.greenend.org.uk wrote: You might have hoped that with the move to 2.4, OS X's firewall would have become *less* fussy, since locally spawned servers should now only listen on the localhost interface http://gna.org/bugs/?18530. Perhaps it has unexpectedly become more fussy as a result of this change in Freeciv -- which behaviour does 2.3 on 10.8 have, if it's easy to test? As an addendum, here's some data to chew on - from netstat. Summary: 2.4 initializes an additional IPv6 socket compared to 2.3. Is this expected behavior? With freeciv-2.3.4 Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp6 0 0 localhost.freeciv localhost.51436ESTABLISHED tcp6 0 0 localhost.51436localhost.freeciv ESTABLISHED tcp4 0 0 *.freeciv *.*LISTEN tcp6 0 0 *.freeciv *.*LISTEN With freeciv-2.4.0 Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp6 0 0 localhost.5557 localhost.51623ESTABLISHED tcp6 0 0 localhost.51623localhost.5557 ESTABLISHED tcp6 0 0 localhost.5557 *.*LISTEN tcp4 0 0 localhost.5557 *.*LISTEN tcp6 0 0 localhost.5557 *.*LISTEN I suspect that new socket to be LAN announcement. Their IPv6 support got better between 2.3 and 2.4 (not that I'd call them functional in 2.4) It might be a oversight that server forked by client opens that socket - I don't think single player games need being announced. I'll check that during the weekend. - ML ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
Re: [Freeciv-Dev] Do you want the application “freeciv-server” to accept incoming network connections?
David Lowe writes: Well, i finally moved to OSX 10.8 about the time i built freeciv 2.4. Previously, the OS would ask once [after the first time the binary was run] whether to allow/deny the connection. Whatever answer was chosen would be 'remembered' until the binary was rebuilt. The new version of OSX doesn't 'remember' any more, and keeps asking. Every. Time. What's particularly annoying about this is that it pops up every time i click on the Load Saved Game button. Presumably this is triggered by freeciv initializing a socket or something. My question is, can we avoid re-initializing it repeatedly for solo games? Unfortunately for you, we spawn a fresh server every time we load a game / start a scenario / etc -- we tell it what game to load (etc) via command-line arguments. Of course the listening socket isn't opened until a server is started, and is closed with that server process. For almost all purposes this is simpler and more robust than trying to keep a spawned server hanging around and repurposing it for different uses by the client. I don't think it would be worth trying to switch to doing things that way just for this purpose. You might have hoped that with the move to 2.4, OS X's firewall would have become *less* fussy, since locally spawned servers should now only listen on the localhost interface http://gna.org/bugs/?18530. Perhaps it has unexpectedly become more fussy as a result of this change in Freeciv -- which behaviour does 2.3 on 10.8 have, if it's easy to test? ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
[Freeciv-Dev] Do you want the application “freeciv-server” to accept incoming network connections?
Well, i finally moved to OSX 10.8 about the time i built freeciv 2.4. Previously, the OS would ask once [after the first time the binary was run] whether to allow/deny the connection. Whatever answer was chosen would be 'remembered' until the binary was rebuilt. The new version of OSX doesn't 'remember' any more, and keeps asking. Every. Time. What's particularly annoying about this is that it pops up every time i click on the Load Saved Game button. Presumably this is triggered by freeciv initializing a socket or something. My question is, can we avoid re-initializing it repeatedly for solo games? sent from Mountain Lion Bond. James Bond. ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
