Re: Re[4]: Still trying to get my site up!
On Jun 28, 2005, at 11:58 PM, Ted Mittelstaedt wrote: But with port 25 your ISP really has it backwards. The block is supposed to be for OUTBOUND traffic for a DESTINATION of port 25. This prevents your ISP from hosting spammers and viruses. Blocks on INBOUND traffic with a destination of port 25 are useless. I don't see how this is any more useless than INBOUND port 80 blocking. It prevents the cable subscriber from setting up a pr0n or warez FTP site (or a legit ftp site for that matter). Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[4]: Still trying to get my site up!
On Monday, June 27, 2005 11:45:52 PM Ted Mittelstaedt [EMAIL PROTECTED] wrote: $ $ My new problem is how do I do an FTP into the site. $ $Well, you first have to FTP into www2.beerstud.us as the FTP protocol $does not have any way to create a redirect the way that dydns is doing $for you with their web server. $ $Second, if your ISP is so stupid as to block incoming port 80 yet allow $people to run web servers on any other port number, then it is quite likely $that they are stupid enough to block incoming port 21 (the FTP port) yet $allow incoming FTP on any other port. $ $In which case you just run your ftp daemon and your command line ftp $client program with the -P option and choose some convenient port number. $ $I just tried using $WS~Pro from a WixXP machine, but that failed. $ $Don't know about that one however the WS_FTP that is the freeware one $has a Advanced tab on the site config that allows you to specify the $remote port. $ $Ted ** Reply Separator ** Tuesday, June 28, 2005 6:46:28 AM Actually, anonymous FTP does work. I was not specific enough before. My next endeavor will be to set up FTP correctly. Do you have any recommendations for an FTP client that is reliable and simple to configure? By the way, the blocking of port 80 as well as port 25 is becoming a rather common occurrence. I am surprised that you are not more familiar with this practice. -- Gerard E. Seibert [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[4]: Still trying to get my site up!
On Monday, June 27, 2005 11:39:32 PM Ted Mittelstaedt [EMAIL PROTECTED] wrote: $ $ On Sunday, June 26, 2005 11:22:19 PM Ted Mittelstaedt $[EMAIL PROTECTED] wrote: $ $ $$Thanks to several individuals, I have almost gotten my Apache2 server $$working. Almost, but not quite. $$ $$My ISP blocks port 80; therefore I am using a redirect from $$DynDNS.org to $$redirect to an alias using port 9545. $$ $$ $$No, you are not. You cannot redirect to a specific port using $$the DNS system. $$ $$Currently dydns.org has beerstud.us pointing to IP address $63.208.196.110 $$If that is your IP address then hosts on the Internet that query $$www.beerstud.us will go to port 80 on that IP address. If that isn't $$your IP number then it must be an IP address of a webhost that will $$issue a HTTP redirect when it gets a query to port 80 on your $beerstud.us $$URL. $$ $$The 'beerstud.us' redirects to 'www2.beerstud.us:9545' $$ $$From my FreeBSD box, if I type: lynx http://beerstud.us, I see the $$following message: Using http://www2.beerstud.us:9545/. The $$connection is $$made and the index.htm file is displayed. $$ $$However, I am unable to reach this site from any other computer. $$Eventually, the request will time out and I receive an error message $$telling me that the site is not available. $$ $$I am not sure what I am doing wrong at this point. $$ $$You need to contact the support department of your ISP. I don't $$understand why you think that your ISP is just blocking port 80 and $$not any other port. There are firewalls out there nowadays smart $$enough to see an incoming HTTP request and block it no matter what $$port it's coming in on. If your ISP is blocking port 80 that probably $$means you haven't paid for an enhanced account that will allow you $$to run a server. If that is the case and your ISP is making money off $$allowing ports to be open for customers, then I would think that they $$probably have one of those firewalls setup that blocks incoming $$HTTP get requests no matter what port they come in on. $$ $$Ted $ $ $** Reply Separator ** $Monday, June 27, 2005 7:00:20 AM $ $I contacted DynDNS, and they stated that any requests for 'beerstud.us' $were being redirected to 'www2.beerstud.us:9545'. $ $Your DNS requests for beerstud.us are NOT, I repeat NOT being redirected to $www2.beerstud.us:9545. They are being pointed to 63.208.196.110 $There is a webserver at that IP address which is issuing a HTTP $redirect to 216.45.217.148, port 9545. The client webbrowser then $makes a second DNS request for www2.beerstud.us. $ $However, the good news is that the site has suddenly come online. I $have no idea why though. $ $Because the admin of the webserver at 63.208.196.110 fixed his $configuration file, that is why. $ $From the looks of it that webserver is owned by dydns, so when you $contacted them it must have lit a fire under the admin of that $server. $ $Your ISP sounds like they are pretty stupid, frankly. $ $ $Ted ** Reply Separator ** Tuesday, June 28, 2005 6:49:34 AM The bottom line is that it works. In the final analysis, that is all that matters. Thanks for your input though. -- Gerard E. Seibert [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Re[4]: Still trying to get my site up!
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gerard Seibert Sent: Tuesday, June 28, 2005 3:54 AM To: Ted Mittelstaedt Cc: freebsd-questions Subject: Re[4]: Still trying to get my site up! The bottom line is that it works. In the final analysis, that is all that matters. No, in the final analysis, what matters is that you understand what your doing - if you don't then you can cause problems for other people on the Internet. Not to mention misleading others and thus causing more of a support burden for the folks who know what they are doing. Being a clueless admin is not something to be proud of, we already have way too many of them. You have already shown yourself a bit smarter than the average because you asked for help instead of just trying bandaid after bandaid until stumbling over some kludge that kind of worked. Don't fuck that up by copping an attitude that ignorance is bliss. Thanks for your input though. input implies something that you have a choice of accepting or not, I really don't care for such politically correct terminology. help is a far better word, here. What you got was help that you really needed to have before you started screwing around with something that is over your head. If you don't want to be labeled a horses-ass, you don't have a choice on whether to learn from instruction, or not. I hope you don't want to be a horses-ass. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Re[4]: Still trying to get my site up!
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gerard Seibert Sent: Tuesday, June 28, 2005 3:49 AM To: Ted Mittelstaedt Cc: FreeBSD Question Subject: Re[4]: Still trying to get my site up! Actually, anonymous FTP does work. I was not specific enough before. My next endeavor will be to set up FTP correctly. Do you have any recommendations for an FTP client that is reliable and simple to configure? What operating system do you want to run the client on? By the way, the blocking of port 80 as well as port 25 is becoming a rather common occurrence. I am surprised that you are not more familiar with this practice. Port 80 blocks have always been popular on cable in order to deter porno sites from using cheap cable connections. It used to be a common practice for porno sites to setup on cable then spam the world with a throwaway URL, collect their credit card payments for their porno which they generally stole from other porno sites, then move on when they got booted. However they are not common on DSL for reasons I explained elsewhere. But with port 25 your ISP really has it backwards. The block is supposed to be for OUTBOUND traffic for a DESTINATION of port 25. This prevents your ISP from hosting spammers and viruses. Blocks on INBOUND traffic with a destination of port 25 are useless. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
