>It's funny too cause just playing with my server before I noticed L4D almost >gets around this problem automatically. If I do a manual connect to my >public IP L4D automatically tried to connect to my public and my local IP >and eventually connects on the local. It's a shame though it doesn't work >for lobbies.
Surely it can't be too hard to change the behaviour of the data L4D sends out to including keys like "external_address" and "internal_address". A small bit of coding to allow clients to check for a server on the local subnet before trying the external? Vote this goes into the next patch :P _______________________________________________________ Shane Arnold - [email protected] "For want of a nail, the horseshoe was lost. For want of a horseshoe, the horse was lost. For want of a horse, the messenger was lost. For want of a messenger, the message was not delivered. For want of an undelivered message the war was lost." Tim Fletcher wrote: > Thank you very much. > > I had a feeling it was something to do with my router but had no idea it was > called nat loopback. That hint in your first e-mail sent me looking and your > link in the second also gave me some very useful info. I now have heaps of > info and lots of things to try. > > Thank you everyone for your help. > > It's funny too cause just playing with my server before I noticed L4D almost > gets around this problem automatically. If I do a manual connect to my > public IP L4D automatically tried to connect to my public and my local IP > and eventually connects on the local. It's a shame though it doesn't work > for lobbies. > > 2009/6/27 Da-Huntha <[email protected]> > > >> Even though I'm sure this doesn't need to be said: make sure your >> router's firmware is up-to-date. >> >> A quick google search brings me to this very interesting patch: >> http://www.waveform.plus.com/netgear.html >> It contains a fix you can try to get the NAT loopback working correctly. >> (This fix only works with certain versions of your router, so you want >> to check your router's version first) >> >> If not, you can google further and see if there's a fix for it: >> http://www.google.com/search?q=DG834GT+nat+loopback >> >> >> On Fri, Jun 26, 2009 at 4:02 PM, Tim Fletcher<[email protected]> wrote: >> >>>> Maximilian L >>>> mh, good question. tried >>>> ms_force_dedicated_server LocalIP:PORT >>>> >>> No didn't know about that. That will will work I think if I am the only >>> person in the lobby but if others are I think I will connect but they >>> >> will >> >>> fail. I would at least be able to start a game by myself and then they >>> >> could >> >>> join later. >>> >>> >>> And the router is a Netgear DG834GT >>> Website is here >>> http://kb.netgear.com/app/products/model/a_id/2328 >>> >>> 2009/6/26 Da-Huntha <[email protected]> >>> >>>> Could you post your Router model and type? >>>> It's probably a router configuration problem involving IP Loopback not >>>> set correctly. >>>> >>>> On Fri, Jun 26, 2009 at 3:04 PM, Tim Fletcher<[email protected]> wrote: >>>> >>>>> Hopefully I can explain this well enough that people can understand my >>>>> question. >>>>> >>>>> I have a L4D server running on a windows server on my local private >>>>> >>> network. >>> >>>>> It is setup with port forwarding from the router and my friends can >>>>> >>> connect >>> >>>>> from the internet through a lobby to my server with no problems. That >>>>> >> is >> >>>>> working fine. Performance is great and pings are pretty good too. >>>>> >>>>> The problem is I can't connect to my server through a lobby. I can be >>>>> >> in >> >>> a >>> >>>>> lobby with my friends and when they start the game they will all >>>>> >> connect >> >>> to >>> >>>>> my server but I can't. I know what the problem is and I can work >>>>> >> around >> >>> it >>> >>>>> but it would be nice to just connect as that way I can be the lobby >>>>> >>> leader >>> >>>>> and set the game up without having to manually set the server up >>>>> >> before >> >>>>> hand. >>>>> >>>>> The real problem is that when I try to connect through the lobby it >>>>> >> trys >> >>> to >>> >>>>> connect to the lobby through my public ip and I assume the router >>>>> >> can't >> >>>>> handle that. I can connect to my server fine if I connect manually >>>>> >> using >> >>> the >>> >>>>> console to it's local ip. >>>>> >>>>> So is there any way I can redirect network traffic from my public ip >>>>> >> to >> >>> my >>> >>>>> servers local ip either on my router (netgear dg834gt) or on my local >>>>> machine or is there anyway to do this in game some how? >>>>> >>>>> Thanks for any help in advance >>>>> _______________________________________________ >>>>> To unsubscribe, edit your list preferences, or view the list archives, >>>>> >>> please visit: >>> >>>>> http://list.valvesoftware.com/mailman/listinfo/hlds >>>>> >>>>> >>>> _______________________________________________ >>>> To unsubscribe, edit your list preferences, or view the list archives, >>>> >>> please visit: >>> >>>> http://list.valvesoftware.com/mailman/listinfo/hlds >>>> >>> _______________________________________________ >>> To unsubscribe, edit your list preferences, or view the list archives, >>> >> please visit: >> >>> http://list.valvesoftware.com/mailman/listinfo/hlds >>> >>> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds >> >> > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds > > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
