Re: [hlds_linux] CS:S question
yes i meant -ip not port..sorry for hte mistype..:) Craig Moore wrote: First, what I think you mean to say is +ip or -ip, whichever it is. As for the FQDN part, you can't bind to an IP that the local machine doesn't have assigned to an interface. You have to tell it the local IP and do the port forwarding at the NAT router. Even if it could accept the FQDN, it wouldn't solve your problem for the forementioned reason and the fact that it doesn't automatically update the DNS record. You say you're using a Dynamic DNS service, but you didn't mention if you have a daemon running on the LAN (perhaps even the router) that updates it every time the IP changes. If you use the LAN IP and it properly forwards the packets, updating the DNS record will be enough for the clients that actually add that to their favorites. There's no way you can force them to use a FQDN. For a few dollars more a month, you can most likely get a static IP from your ISP. Give them a call. They might require you use a "business" plan, which is pretty much just a static IP and a few more e-mail accounts in most cases. Hope this was some help. Regards, Craig Moore On 12/26/05, William Warren <[EMAIL PROTECTED]> wrote: I run Ipcop in front of my HLDS(and now also an SRCDS) server. For the source server can the +port command be an FQDN? I ask to ask as i run these servers form my dsl line and i have to use Dyndns..:) According to my research source doesn't like +port being the LAN ip address. p.s. the 1.6 runs swimmingly behind my firewall but the source server is having issues with refusing or dropping remote RCON requests. -- My "Foundation" verse: Isa 54:17 No weapon that is formed against thee shall prosper; and every tongue that shall rise against thee in judgment thou shalt condemn. This is the heritage of the servants of the LORD, and their righteousness is of me, saith the LORD. -- carpe ductum -- "Grab the tape" CDTT (Certified Duct Tape Technician) Linux user #322099 Machines: 206822 256638 276825 http://counter.li.org/ ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux -- My "Foundation" verse: Isa 54:17 No weapon that is formed against thee shall prosper; and every tongue that shall rise against thee in judgment thou shalt condemn. This is the heritage of the servants of the LORD, and their righteousness is of me, saith the LORD. -- carpe ductum -- "Grab the tape" CDTT (Certified Duct Tape Technician) Linux user #322099 Machines: 206822 256638 276825 http://counter.li.org/ ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] CS:S question
First, what I think you mean to say is +ip or -ip, whichever it is. As for the FQDN part, you can't bind to an IP that the local machine doesn't have assigned to an interface. You have to tell it the local IP and do the port forwarding at the NAT router. Even if it could accept the FQDN, it wouldn't solve your problem for the forementioned reason and the fact that it doesn't automatically update the DNS record. You say you're using a Dynamic DNS service, but you didn't mention if you have a daemon running on the LAN (perhaps even the router) that updates it every time the IP changes. If you use the LAN IP and it properly forwards the packets, updating the DNS record will be enough for the clients that actually add that to their favorites. There's no way you can force them to use a FQDN. For a few dollars more a month, you can most likely get a static IP from your ISP. Give them a call. They might require you use a "business" plan, which is pretty much just a static IP and a few more e-mail accounts in most cases. Hope this was some help. Regards, Craig Moore On 12/26/05, William Warren <[EMAIL PROTECTED]> wrote: > I run Ipcop in front of my HLDS(and now also an SRCDS) server. For the > source server can the +port command be an FQDN? I ask to ask as i run > these servers form my dsl line and i have to use Dyndns..:) According > to my research source doesn't like +port being the LAN ip address. > > p.s. the 1.6 runs swimmingly behind my firewall but the source server is > having issues with refusing or dropping remote RCON requests. > > -- > My "Foundation" verse: > Isa 54:17 No weapon that is formed against thee shall prosper; and > every tongue that shall rise against thee in judgment thou shalt > condemn. This is the heritage of the servants of the LORD, and their > righteousness is of me, saith the LORD. > > -- carpe ductum -- "Grab the tape" > CDTT (Certified Duct Tape Technician) > > Linux user #322099 > Machines: > 206822 > 256638 > 276825 > http://counter.li.org/ > > ___ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] CS:S question [u]
William Warren schrieb: I run Ipcop in front of my HLDS(and now also an SRCDS) server. For the source server can the +port command be an FQDN? I ask to ask as i run these servers form my dsl line and i have to use Dyndns..:) According to my research source doesn't like +port being the LAN ip address. p.s. the 1.6 runs swimmingly behind my firewall but the source server is having issues with refusing or dropping remote RCON requests. Yeah - giving an IP parameter to a -port option is always a bad idea :o. So I guess you meant -ip (its "-" since for some time now but it still accepts "+"). Nevertheless you most likely will not have to enter the port and ip values anyway. You just have to forward the serverport (27015 if you don't set any other by -port) on *udp* (for joining the server from outside) and *tcp* (for the rcon protocol, which now is a connection oriented one). If you have multiple network interfaces on the server machine (not the one running IPCop): on udp a server listens to all interfaces if not bound to a specific ip while on tcp it just listens to one (selectable by -ip). ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
