Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Troy Arnold
On Tue, Feb 15, 2011 at 03:27:01PM -0500, Peter Salzman wrote: > > But as to why the 3-way handshake isn't being fully established ... > that would suck because I have *no* idea how to diagnose that sort of > thing... Hey, Pete- netcat is the perfect tool for determining if the 3 way handshake i

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Peter Salzman
> Hi Bryan, > > Good call, but I'm on Optimum Online Ultra.  It's pricey ($85/mo) but > between the 100Mbps down, 15 Mbps up, static IP, and being able to run > servers, I kind of had to get it, so I fall under 22B. > > I called them and verified they don't drop packets to port 80, and in > fact, I

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Peter Salzman
On Tue, Feb 15, 2011 at 2:54 PM, Cam Ellison wrote: > On 11-02-15 11:31 AM, Peter Salzman wrote: >> On Tue, Feb 15, 2011 at 12:26 PM, Cam Ellison  wrote: >>> On 11-02-15 08:56 AM, Peter Salzman wrote: OK, I commented out all the virtual host stuff and changed ports.conf to: Listen 8

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Peter Salzman
On Tue, Feb 15, 2011 at 2:51 PM, Bryan Richter wrote: > On Tue, Feb 15, 2011 at 01:31:58AM -0500, Peter Salzman wrote: >> Third time is a charm, perhaps.  I'm trying to get Apache to work. >> >> I can access dirac.org successfully from inside my network; I can't >> access it from outside my home n

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Bryan Richter
On Tue, Feb 15, 2011 at 01:31:58AM -0500, Peter Salzman wrote: > Third time is a charm, perhaps.  I'm trying to get Apache to work. > > I can access dirac.org successfully from inside my network; I can't > access it from outside my home network. Apache is running on a Linux box > on satan: 192.168

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Orson Jones
On 02/15/2011 12:38 PM, Peter Salzman wrote: > On Tue, Feb 15, 2011 at 2:26 PM, Orson Jones > wrote: >>> Unfortunately, Apache is listening to 80 -- I think I know that >>> because the webserver is accessible from inside the LAN. But just to >>> make 100% sure, >> >> Rereading your original post

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Cam Ellison
On 11-02-15 11:31 AM, Peter Salzman wrote: > On Tue, Feb 15, 2011 at 12:26 PM, Cam Ellison wrote: >> On 11-02-15 08:56 AM, Peter Salzman wrote: >>> OK, I commented out all the virtual host stuff and changed ports.conf to: >>> >>> Listen 80 >>> >>> � � �# SSL name based virtual hosts are not yet s

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Peter Salzman
On Tue, Feb 15, 2011 at 2:26 PM, Orson Jones wrote: >> Unfortunately, Apache is listening to 80 -- I think I know that >> because the webserver is accessible from inside the LAN.  But just to >> make 100% sure, > > Rereading your original post, I misunderstood the setup. > It sounds like the packe

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Peter Salzman
On Tue, Feb 15, 2011 at 12:26 PM, Cam Ellison wrote: > On 11-02-15 08:56 AM, Peter Salzman wrote: >> >> OK, I commented out all the virtual host stuff and changed ports.conf to: >> >> Listen 80 >> >>      # SSL name based virtual hosts are not yet supported, therefore no >>      Listen 443 >> >>

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Orson Jones
> Unfortunately, Apache is listening to 80 -- I think I know that > because the webserver is accessible from inside the LAN. But just to > make 100% sure, Rereading your original post, I misunderstood the setup. It sounds like the packets are getting in, hitting the server, being responded to by

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Peter Salzman
On Tue, Feb 15, 2011 at 12:40 PM, Orson Jones wrote: > A couple more things worth checking: > > Use netstat to check to see what IP(s) it is actually listening on. > netstat -tapn | grep LISTEN | grep :80 > If the output of that doesn't match what is in the configuration, there may > be something

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Peter Salzman
On Tue, Feb 15, 2011 at 12:32 PM, wrote: >> Original Message >> Subject: [vox-tech] Apache: 2, Me: 0. >> From: Peter Salzman >> Date: Mon, February 14, 2011 10:31 pm >> To: vox-tech >> >> >> Third time is a charm, perhaps.  I'm trying to get Apache to work. >> >> I can access

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Cam Ellison
On 11-02-15 08:56 AM, Peter Salzman wrote: > > OK, I commented out all the virtual host stuff and changed ports.conf to: > > Listen 80 > > # SSL name based virtual hosts are not yet supported, therefore no > Listen 443 > > ServerName dirac.org > > and Apache is still not responding to r

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Orson Jones
A couple more things worth checking: Use netstat to check to see what IP(s) it is actually listening on. netstat -tapn | grep LISTEN | grep :80 If the output of that doesn't match what is in the configuration, there may be something wrong with the config and you should spend more time looking ther

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread timriley
> Original Message > Subject: [vox-tech] Apache: 2, Me: 0. > From: Peter Salzman > Date: Mon, February 14, 2011 10:31 pm > To: vox-tech > > > Third time is a charm, perhaps.  I'm trying to get Apache to work. > > I can access dirac.org successfully from inside my network; I c

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Rod Roark
On 02/15/2011 08:56 AM, Peter Salzman wrote: > OK, I commented out all the virtual host stuff and changed ports.conf to: > > Listen 80 > > # SSL name based virtual hosts are not yet supported, therefore no > Listen 443 > > ServerName dirac.org > > and Apache is still not responding to r

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Peter Salzman
On Tue, Feb 15, 2011 at 11:28 AM, Rod Roark wrote: > On 02/15/2011 08:05 AM, Peter Salzman wrote: >> and in ports.conf: >> >>       Listen 192.168.0.2:80 >> >>       >>             # SSL name based virtual hosts are not yet supported, therefore >> no >>             Listen 443 >>       >> >>    

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Rod Roark
On 02/15/2011 08:28 AM, Rod Roark wrote: > To listen on all ports, change the first Listen directive to > just "Listen 80". Sorry, I mean "To listen on all IPs...". ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinf

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Rod Roark
On 02/15/2011 08:05 AM, Peter Salzman wrote: > and in ports.conf: > > Listen 192.168.0.2:80 > > > # SSL name based virtual hosts are not yet supported, therefore no > Listen 443 > > > ServerName dirac.org So it's only listening on 192.168.0.2. Per

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Peter Salzman
On Tue, Feb 15, 2011 at 9:29 AM, Rod Roark wrote: > > Check the Listen directives.  By default it will listen on all > IP addresses, but if one specifies an IP or localhost then only > those specified will be listened to. > > If that's OK, then see if it works without the NameVirtualHost > and Vir

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Peter Salzman
On Tue, Feb 15, 2011 at 2:42 AM, Nick Schmalenberger wrote: > On Tue, Feb 15, 2011 at 01:31:58AM -0500, Peter Salzman wrote: >> Third time is a charm, perhaps.  I'm trying to get Apache to work. >> >> I can access dirac.org successfully from inside my network; I can't >> access it from outside my

Re: [vox-tech] Apache: 2, Me: 0.

2011-02-15 Thread Rod Roark
Check the Listen directives. By default it will listen on all IP addresses, but if one specifies an IP or localhost then only those specified will be listened to. If that's OK, then see if it works without the NameVirtualHost and VirtualHost stuff. Rod ___