I didn t, but suppose I should. I think that if I tidy up the code, then a simple diff
will make the changes clear. Most of the work was to get PCAP and sockets to use the same
mechanism to tell the code that there was some data to be processed.
Regards
Rob
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of
hvlems at zonnet.nl Sent: 20 November 2011 11:24 To: hecnet at Update.UU.SE Subject:
Re: [HECnet] Windows Version of Bridge
Did you document the changes? I want to try and port it to VMS.
From: "Rob Jarratt" <robert.jarratt at ntlworld.com>
Sender: owner-hecnet at Update.UU.SE
Date: Sun, 20 Nov 2011 09:21:09 -0000
To: <hecnet at update.uu.se>
ReplyTo: hecnet at Update.UU.SE
Subject: [HECnet] Windows Version of Bridge
I just wanted to let you know that I have ported the bridge code to Windows. It seems to
work well for me. If anyone is interested in a copy, let me know.
I think that it needs just a little bit more work to do the following:
1. Tidy up some bits that I almost certainly left behind while trying to get it
to work.
2. Turn it into a Windows Service so that it starts automatically when Windows
starts.
Another feature which would be nice to add generally is something which periodically
re-resolves the DNS names in the config file to IP addresses, so that people who use
something like DynDNS because they don t have a fixed IP address, can use it more easily
and not fall off the network for too long when their IP address changes. Presumably
calling the SIGHUP handler (read_conf) every so often would do the trick.
It would also be nice to make the code a bit more portable so that it will compile and run
on more platforms without modification, a bit like SIMH.
Regards
Rob