Yeah, I think it's not a big issue. I think when you connect to a web server on port 80, that's port 80 on the *server* computer side. Who cares which port your client machine connects to it with. You could have ten programs, each making requests on different ports to the same port 80 web server.
Firewall rules (on client) just classify that as an "outgoing connection on port 80". It means "*to* port 80". I could be wrong, but that's my impression. Anton. > Hi, Matt, > > I claim no guruhood re networking, but... > > IIRC, firewall rules can take both origin and destination ports into > account. Could they use a rule that allows any client-side port, as > long as it is attempting to connect to a specified server/port where > the authorized service is available? > > -jn- > > Matt MacDonald wrote: > > > > I'm making a client software for other users. I need to > somehow limit the > > ports that rebol will try to open on their computers so that > their company > > firewalls can be configured to allow access over those ports. > Or am I going > > about it the wrong way? Any networking gurus out there? > > > > -- > ---------------------------------------------------------------------- > Joel Neely joelDOTneelyATfedexDOTcom 901-263-4446 -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
