Index: [Article Count Order] [Thread]

Date:  Sun, 24 Jun 2007 15:58:24 -0700
From:  "Ernie Aldama" <ealdama (at mark) inhomepc.net>
Subject:  [coba-e:10226] Re: Unable to access virt sites from outside the local network. {Scanned}
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <000f01c7b6b3$2b5a06f0$a26b304b@etek3>
In-Reply-To:  <024e01c7b6a3$4c15f3a0$3701a8c0@user33b5201c50>
X-Mail-Count: 10226

Arthur,

All good points, and you are correct in this bahavior mentioned.  I'll add
your thoughts to the list of things to test on the standby server.  I went
so far as to take the firewall physically out of the picture.  I did run
across something, via Google, that was related to an Alcatel router and
ADSL, that had to do with ARP caching (using a Netopia 3347WG-ENT) and maybe
there is something there still.  For now, I have the site running, my dad's
business is happy again, which makes me happy... For now.

Your 2p are well noted and appreciated =-)

Thanks,
Ernie

> -----Original Message-----
> From: Arthur Sherman [mailto:arturs (at mark) netvision.net.il] 
> Sent: Sunday, June 24, 2007 2:05 PM
> To: coba-e (at mark) bluequartz.org
> Subject: [coba-e:10225] Re: Unable to access virt sites from 
> outside the local network. {Scanned}
> 
> 
> > > It seems to be rather packet mangling issue, than 
> routing, ot maybe
> > > both are involved.
> > > 
> > > I would check with the provider for his firewall.
> > > 
> > 
> > 
> > Since it's sitting on my network, I control the firewall.
> > Other systems on the network work fine, I can even get to the 
> > admin site of this system, just fine from the outside.  This 
> > only seems to affect access to virtual sites from outside the 
> > network.  I can also SSH into the system, using any of the IP 
> > addresses locally.  I've tried changing IP addresses, and 
> > it's still not working.  This really seems like it's 
> > something in the "box" the more I play with this, centered 
> > around aliased interfaces not routing.  I think I've ruled 
> > out iptables, apache, and I think I've ruled out IP address 
> > configuration unless I'm just missing something obscure.  I 
> > haven't messed with anything there, only used the GUI to set 
> > up the site, and let it create its own alias for the NIC 
> > which is the eth0:0 interface.
> > 
> > I even took this one step further and created a new virtual
> > site, set up my external DNS and that failed too.  I can 
> > properly resolve the FQDN to the proper IP address, can hit 
> > the site locally, but still can't get to it from the outside.
> > 
> > I think I'm down to my last hair here... And my desk is
> > getting a little messy.  If anyone else can think of 
> > something I'm willing to try it as it this point my next move 
> > might be to try moving the site off, reinstalling, and moving 
> > it back.  This all worked at one time, then it just stopped, 
> > and that is the most frustrating since I hadn't been working 
> > on it for a couple of months and it just sat there idle.
> 
> 
> Look at this:
> 
> Request for virtual site comes from outside --> resolving 
> request to your
> DNS --> it says go to the firewall --> firewall further 
> resolves them to IP
> (is their some name caching enabled?) --> this doesn't work
> Is this right?
> Same thing but from inside --> not through the firewall? --> 
> resolving works
> 
> Thus, I assume it is firewall or maybe some additional router 
> which mangles
> packets, or cuts reply, which could both provide the error.
> 
> This is where I see this problem
> 
> Maybe setting the BQ DNS to be SOA for its sites could resolve this.
> 
> My 2p.
> 
> 
> Best,
> 
> --
> Arthur Sherman
> 
> 
> 
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.