[Server-devel] Bridging XS to another network

David Leeming david at leeming-consulting.com
Sat Oct 30 16:28:23 EDT 2010


Martyn,

 

In regard to the below, I am trying to set up the XS behind a Linksys
WRT54G2 router. 

 

I think my issue is because eth1 (lanbond0) is set up as network
172.18.96.1/255.255.224.0 (for the XOs) but the server listens on 172.18.0.1
(or

 

I have tried to use the route command to add the router LAN IP as the
default gateway but it doesn't work or I did it wrong

 

Could you please tell me what I should use for the LAN settings on the
router? 

 

The WRT54 settings I am using here at home are

..         WAN - static IP, 192.168.1.88 / 255.255.255.0 (external network is
192.168.1.0/24)

..         LAN - static IP, 172.18.0.88 / 255.255.255.0 (could it be the
netmask? The WRT only allows up that setting , i.e. 255.255.224.0 is not
possible)

..         Port forwarding, I tried everything, including UPnP forwarding and
DMZ Host with 172.18.0.1 as the IP

 

At the moment I can't ping from the XS to the Linksys WAN IP (on the
external network). However, I can ping the LAN side (172.18.0.88). 

 

Moreover, from a PC connected to the same LAN side of the router, I ACN
indeed ping all the way through the router to the external network and
beyond. I can also ping the server and if I enter 172.18.0.1 in the browser
I get Moodle. So in summary, the PC can send traffic through the router but
the server can't. Beats me but I am sure it is the network settings
somewhere.

 

I tried this using with the router LAN network set to 172.18.96.0/24 but it
didn't work either - I can't ping through the router even with a PC
(destination reachable). Note that the PC is given a mask of 255.255.224.0
by the XS DHCP (and DNS server 172.18.0.1) and it's not possible to use that
in the router settings.

 

Is this going to be possible? Do I need a better router ? I am going to the
remote site today for 7 days, and need to crack this one quickly

 

 

David Leeming

Solomon Islands Rural Link 



 

From: server-devel-bounces at lists.laptop.org
[mailto:server-devel-bounces at lists.laptop.org] On Behalf Of David Leeming
Sent: Saturday, 30 October 2010 4:11 p.m.
To: 'XS Devel'
Cc: 'Mark Flynn'; 'Phill Hardstaff'
Subject: [Server-devel] Bridging XS to another network

 

Hello all again,

 

A networking challenge this time.

 

I have an XS at a school where there also exists a wide area private network
connecting schools using Wi-Fi. We want those connected schools to be able
to access the XS, for various reasons.

 

That network (let's call it network 2) is 192.168.1.0/24 and it is connected
with the Internet via a router  running NAT and DHCP.

 

The XS local network seems to be quite complicated, I don't fully understand
it, but what I need to know is the correct slash designation for the httpd
and dns servers at 172.18.0.1 so that I can bridge it to network 2.

 

I am trying to use a Linksys WRT54G2 in DMZ Host mode with the IP address
172.18.0.1 bridged to the external Wan IP address of the WRT (set to
192.168.1.88)

 

The WRT LAN IP setting only allows netmask values of up to 255.255.255.0 and
I am worried if there is a mismatch then it could be why I can't get it to
work. 

 

I also suspect I may have to add something to the apache or routing config
on the XS, so as to "listen" on the WRT external IP address 

 

At the moment I set the Linksys to 

WAN - fixed IP 192.168.1.88 / 255.255.255.0

LAN IP address - 172.18.0.88 / 255.255.255.0  (could the net mask be the
issue?)

Application: DMZ Host, value 172.18.0.1 

Required changes to  xs apache settings   ??????    

 

Trying to connect on the network 2 side using a browser if I enter
192.168.1.88 or 172.18.0.1 it just times out.

 

If anyone reading this recognises what I am trying to do, I'd very much
appreciate your advice.

 

 

David Leeming

Solomon Islands Rural Link 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/server-devel/attachments/20101031/0fb8be53/attachment.htm 


More information about the Server-devel mailing list