Re: two questions in one
steve lasiter wrote: My web server is up and running well and I can test all by going to 192.168.0.2 from any internal workstation, but if I try to go to www.mywebsite.com from any internal workstation, which maps to the 66.190.xxx.xxx IP directed to web server port 80 as it should, my attempt will time out. If I run next door to my buddies and hit it from his PC I get there just fine. I can't understand this since I'm using the www.mywebsite.com name instead of an IP address. It seems the gateway should not be affecting me, right? How do I get around this or solve it? I don't want to have to go next door everytime I need to make sure my site is accessible from the web. Sounds like a DNS lookup problem, check /etc/hosts and /etc/resolv.conf on the different hosts and try to do host lookup on the different hosts. If you get different ip then there you have it. One other quick issue. When FTPing from within my LAN it is horribly slow. It was fast after initial install but something happened without my intervention. I've tried two different servers, proftpd currently and pureftp previously. If I ftp outside my LAN it's lightning fast. Any ideas are appreciated. You are ftp'ing LAN-Internet right? Are you sure that some other user is not sucking up your connection with p2p? On the gateway you can see which states are in the firewall, assuming you have a statefull firewall ruleset. Ntop on the gateway should be a great tool also. Also, ftp and firewalls generally is troublesome, maybe you changed a rule in the firewall just a littlebit? Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: two questions in one
-Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Erik Nørgaard Sent: Tuesday, September 20, 2005 1:11 AM To: steve lasiter Cc: free bsd Subject: Re: two questions in one steve lasiter wrote: My web server is up and running well and I can test all by going to 192.168.0.2 from any internal workstation, but if I try to go to www.mywebsite.com from any internal workstation, which maps to the 66.190.xxx.xxx IP directed to web server port 80 as it should, Thats the problem - you are using NAT, you can't go out and come back in, your packets will expire because they will not be routed back in, and that's by design. You need to set up an internal forward zone in your DNS to direct requests to the internal address .To see what I am talking about, trying pinging your website from the inside using the external address. If your router is set up appropriately, you should get a 'TTL expired' message. Set up an 'A' record for www in mywebsite.com on one of your internal boxes to point to 192.168.0.2, and set up forwarders to your ISP's name servers on this box. Set all your internal hosts to use that machine for DNS requests, and you will be good to go. -Joshua Weaver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: two questions in one
On 9/19/05, steve lasiter [EMAIL PROTECTED] wrote: [...] My web server is up and running well and I can test all by going to 192.168.0.2 from any internal workstation, but if I try to go to www.mywebsite.com from any internal workstation, which maps to the 66.190.xxx.xxx IP directed to web server port 80 as it should, my attempt will time out. If I run next door Your gateway is probably not routing traffic out of your network and back into it. I.E. connections from your private IP numbers to your public IP number will not work. to my buddies and hit it from his PC I get there just fine. I can't understand this since I'm using the www.mywebsite.com name instead of an IP address. It seems the gateway should not be affecting me, right? How do I get around this or solve it? I don't want to have to go next door everytime I need to make sure my site is accessible from the web. Find an anonymizing web proxy service and use it to access your own web site. - Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
two questions in one
First let me say I've come a long way with the help of this community. I now have my local network set up with several servers, workstations, and firewall with most using FreeBSD 5.4. Now here's my current issues. Maybe I can get input even if these are not so very BSD specific. My network consist of a FreeBSD gateway (192.168.0.1) with two new nic cards, fxp0 to the internet(cable modem) and fxp1 to my LAN via cisco switch. My web/mail server is on 192.168.0.2 My static IP is 66.190.xxx.xxx My web server is up and running well and I can test all by going to 192.168.0.2 from any internal workstation, but if I try to go to www.mywebsite.com from any internal workstation, which maps to the 66.190.xxx.xxx IP directed to web server port 80 as it should, my attempt will time out. If I run next door to my buddies and hit it from his PC I get there just fine. I can't understand this since I'm using the www.mywebsite.com name instead of an IP address. It seems the gateway should not be affecting me, right? How do I get around this or solve it? I don't want to have to go next door everytime I need to make sure my site is accessible from the web. One other quick issue. When FTPing from within my LAN it is horribly slow. It was fast after initial install but something happened without my intervention. I've tried two different servers, proftpd currently and pureftp previously. If I ftp outside my LAN it's lightning fast. Any ideas are appreciated. Thanks to all again for the great work, Steve Lasiter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: two questions in one
--- steve lasiter [EMAIL PROTECTED] wrote: snip My web server is up and running well and I can test all by going to 192.168.0.2 from any internal workstation, but if I try to go to www.mywebsite.com from any internal workstation, which maps to the 66.190.xxx.xxx IP directed to web server port 80 as it should, my attempt will time out. How are you redirecting your requests? It is probably due to the fact that a TCP handshake is not being allowed to complete because the server is responding to the client but the client is is expecting a response from the firewall. This is common in your arrangement. Sniff traffic with tcpdump on the various hosts and provide us with more details. If I run next door to my buddies and hit it from his PC I get there just fine. I can't understand this since I'm using the www.mywebsite.com name instead of an IP address. It seems the gateway should not be affecting me, right? How do I get around this or solve it? I don't want to have to go next door everytime I need to make sure my site is accessible from the web. Sign up for a free shell account on an internet-based server. One other quick issue. When FTPing from within my LAN it is horribly slow. It was fast after initial install but something happened without my intervention. I've tried two different servers, proftpd currently and pureftp previously. If I ftp outside my LAN it's lightning fast. Any ideas are appreciated. With the ifconfig utility, check the configuration of the involved network adapters. In particular, look for duplex and half-duplex. -- Peter __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: two questions in one
On 9/20/05, steve lasiter [EMAIL PROTECTED] wrote: My web server is up and running well and I can test all by going to 192.168.0.2 http://192.168.0.2 from any internal workstation, but if I try to go to www.mywebsite.comhttp://www.mywebsite.com from any internal workstation, which maps to the 66.190.xxx.xxx IP directed to web server port 80 as it should, my attempt will time out. If I run next door to my buddies and hit it from his PC I get there just fine. Sounds like your clients aren't set up correctly with DNS to me. Are they pointing to DNS server, is it serving? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
