[Server-devel] Bridging XS to another network

David Leeming david at leeming-consulting.com
Mon Nov 1 19:43:10 EDT 2010


Jerry,

The computers wishing to access the server are Windows laptops that get their DNS from the ISP (actually the gateway router points to Google DNS).The 192.168.0.0/24 network is actually a schoolnet linking several village schools with Wi-Fi bridges and access points, and it has Internet gateway (VSAT). We want all those schools to access the XS moodle and my added wiki.

QUESTION: Yes, I can access the gateway router (it is also a Linksys WRT54G2). Would you know how to add the enter pointing schoolserver.patukae.org to 192.168.0.210, where (in the router admin) would I add that entry? It is not obvious to me, sorry...

Other feedback: 

Everything on the XS is default apart from the added wiki. I ran domain_config patukae.org, yes. I have not done anything deviating from default installation that would cause the @@BASEDNSNAME@@ to appear. 

At the moment from the external net I can browse to
http://192.168.0.210/wiki and it works fine
but not
http://192.168.0.210/ or http://192.168.0.210/moodle 

Maybe the above is relevant?

David 

-----Original Message-----
From: Jerry Vonau [mailto:jvonau at shaw.ca] 
Sent: Tuesday, 2 November 2010 9:53 a.m.
To: David Leeming
Cc: 'XS Devel'
Subject: RE: [Server-devel] Bridging XS to another network

On Tue, 2010-11-02 at 09:00 +1100, David Leeming wrote:
> On Mon, 2010-11-01 at 05:43 -0500, Jerry Vonau wrote:
> > On Mon, 2010-11-01 at 20:35 +1100, David Leeming wrote:
> > > Hi Jerry
> > > 
> > > That sorted it out - almost...
> > > 
> > > I added the gateway and the server can now ping through the router.
> > > 
> > > I added port forwarding for HTTP and success .... partially
> > > 
> > 
> > Good that's progress.
> > 
> > > >From the outside I can enter the router WAN IP (which is now 192.168.0.210) and mixed results...
> > > 
> > > http://192.168.0.210 gives the Firefox error "Server not found, Firefox can't find the server at schoolserver.patukae.org" 
> > > (showing that it has found something at least....). Same with http://192.168.0.210/moodle/ 
> > > 
> 
> > > Shoot, the client can't resolve the name, add to /etc/hosts:
>  
> > > 192.168.0.210 schoolserver.patukae.org schoolserver
> 
> > > Jerry
> 
> 

That needs to be on the client PC/XOs that are on the 192.168.0.XXX lan,
those clients can't resolve schoolserver.patukae.org. What dns server
are the 192.168.0.XXX clients pointed too? Need to know where they're
pointed too can you do a "cat /etc/resolv.conf"  


I'm going to say either your isp's servers, or the ADSL modem is caching
the requests. Is this modem configurable? That would open up many more
options. You can add an entry there for schoolserver.patukae.org
pointing to 192.168.0.210, that would fix up the issue cleanly, else
your forced to use the hosts file.


> Tried but no different. I don't think the mediawiki installation has changed anything fundamental with the networking.

No, not likely.

> The server functions normally when XOs and PCs connect wirelessly or wired to the eth1. 

That is because they can resolve schoolserver correctly, while the
clients on 192.168.0.xxx are failing to resolve schoolserver.patukae.org

> I was wondering if the public folders 
> part might be an issue... because the only difference I can think between the wiki and moodle is that Moodle exists at 
> /var/www/moodle/ but the wiki at /var/www/html/wiki/ (i.e. one level down). Please note these observations:
> 
> These results I get when browsing with a PC on the external network
> 
> 1.	http://192.168.0.210/wiki   fully accessible!
> 2.	http://192.168.0.210 gives “Server not found, Firefox can’t find the server at schoolserver.patukae.org” 
> 3.	http://192.168.0.210/moodle gives same as (2) above
> 4.	http://192.168.0.210/gibberish gives a prompt apache error "the URL /gibberish not found". Thus it does find something (i.e. compare with 2 and 3). 
>  
> My /etc/hosts file now
> 127.0.0.1               schoolserver.@@BASEDNSNAME@@ localhost.localdomain localhost
> ::1                     localhost6.localdomain6 localhost6
> 192.168.0.210           schoolserver.patukae.org schoolserver
> 

Stop, right there, don't add 192.168.0.210 to the XS hosts file, that
needs to be on the *clients* only. I'm curious why @@BASEDNSNAME@@ is
present, you have run "domain_config patukae.org" right? I'm going to
say yes as the client that are on 172.18.96.XXX are ok. Is this the
hosts.in file? 

> Route:
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 172.18.16.0     *               255.255.255.0   U     0      0        0 mshbond0
> 172.18.0.0      *               255.255.255.0   U     0      0        0 lanbond0
> 172.18.1.0      *               255.255.255.0   U     0      0        0 lanbond0
> 172.18.14.0     *               255.255.254.0   U     0      0        0 mshbond2
> 172.18.12.0     *               255.255.254.0   U     0      0        0 mshbond1
> 172.18.10.0     *               255.255.254.0   U     0      0        0 mshbond0
> 172.18.64.0     172.18.1.7      255.255.248.0   UG    0      0        0 lanbond0
> 172.18.72.0     172.18.1.8      255.255.248.0   UG    0      0        0 lanbond0
> 172.18.8.0      172.18.1.1      255.255.248.0   UG    0      0        0 lanbond0
> 172.18.16.0     172.18.1.1      255.255.248.0   UG    0      0        0 lanbond0
> 172.18.24.0     172.18.1.2      255.255.248.0   UG    0      0        0 lanbond0
> 172.18.32.0     172.18.1.3      255.255.248.0   UG    0      0        0 lanbond0
> 172.18.40.0     172.18.1.4      255.255.248.0   UG    0      0        0 lanbond0
> 172.18.48.0     172.18.1.5      255.255.248.0   UG    0      0        0 lanbond0
> 172.18.56.0     172.18.1.6      255.255.248.0   UG    0      0        0 lanbond0
> 172.18.96.0     *               255.255.224.0   U     0      0        0 lanbond0
> link-local      *               255.255.0.0     U     0      0        0 mshbond2
> default         172.18.0.88     0.0.0.0         UG    0      0        0 lanbond0

Good, that's fixed..

Jerry





More information about the Server-devel mailing list