I think Chips has the right idea. If your FL client worked flawlessly for several months and suddenly it didn't, then something changed. It could be your ISP, college ISP's are notorious for sniffing for excessive traffic on ports looking for the boad, ole P2Per and then blocking that port. But this is rare.
Chances are you changed something in you 'puter. What I have heard of at least 90% of the time in these cases is someone installed another game and it's install was not very efficient. Instead of checking and not touching a later version of DirectX, it installs it's own version of DirectX regardless. To make a long story short the recommended cure was just reinstall DirectX to get the latest version because for the most part it's backward compatible.
Was anything changed in your gateway/modem? FL client uses close to a dozen OUTGOING ports only (no INCOMING ports). Ordinarily most firewalls (especially hardware firewalls) are concerned about INCOMING ports only but some software firewalls, like ZoneAlarm, firewall both directions. Do you have ZA?
I assume the direct connection you mention to your gateway/modem is actually your ISP requiring you to use only your 'puter and it's unique MAC address with their gateway/modem. It's a neat trick by ISP's to ensure you have only one 'puter per Internet connection but there is a simple workaround. Today's gateways have the ability to be reconfigured to project out the WAN (Internet) side any MAC address. So if you get a gateway, put your 'puter's MAC address in it, then you can try a little test. Through the gateway, connect another 'puter with FL client and see if that works correctly. If it does that would rule out issues with your network, gateways, ISP and back to the FL global list server.
Hope any of this helps.
_____________
Earendil
SysAdmin of Boston Freelancer server
Server community website & forum:
EarendilsPlace.net (
server rules)