2013-03-11 - Re: [GRASE-Hotspot] two networks on the internal network adaptor?

Header Data

From: Tim White <ti***8@gmail.com>
Message Hash: 38e72bbea92ccf1f434714fd1f1fbfdee2f7b7b2bd792a57c6b6646200e4d592
Message ID: <513E916D.2030501@gmail.com>
Reply To: <1362847497.84900.YahooMailNeo@web140603.mail.bf1.yahoo.com>
UTC Datetime: 2013-03-11 19:22:37 UTC
Raw Date: Tue, 12 Mar 2013 12:22:37 +1000

Raw message 

On 10/03/13 02:44, Psteve wrote:
> Hello All
> I'm sure this is a really simple thing to do but I just can't figure 
> out how to do it.  I've been running grase for some time now really 
> sucessfully at the company I work for (an emergency service).  So 
> sucessful that I've had a request to put it in on another site.  The 
> two sites are linked together.  Let's say siteA is 10.1.0.X and siteB 
> is 10.1.1.X. The routers internally are 10.1.0.254 and 10.1.1.254.  
> Network traffic passes between them just fine, although computers on 
> site B can't ping the grase server, although they can ping other PCs 
> on siteA.
> I suspect this is something to do with the internal routing table in 
> ubuntu but I've added a route into the grase server for 10.1.1.0 with 
> a gateway of 10.1.0.254 and it still doesn't seem to want to play.
> Has anyone achieved this?

Maybe some more details as to how it is setup.

In a normal Grase setup, Grase handles the DHCP for the network. It 
sounds to me as if you have the Grase server (say 10.1.0.1) at Site A, 
and it's the default gateway for the Site A network, and handles DHCP 
for the Site A network? Then you have a router at Site A that is somehow 
connected to Site B (assuming a PTP like?). Site B doesn't have an 
"internet" connection, just the connection to Router A at Site A.

What I don't get about this setup, which probably means I misunderstood 
your setup, is how do the Site A client computers know how to connect to 
the Site B client computers. Unless they all have static routes in them 
pointing them to the 10.1.0.254 router for 10.1.1.0, they'll be trying 
to use 10.1.0.1 as the route for all unknown networks. Adding static 
routes to lots of computers is silly and annoying.


Maybe a digram of how it's all connected, and what routes are in place 
(including default routes) and what the links are, would help. It also 
sounds like you probably need Grase setup in Layer 3 routing, not Layer 
2, and so it wouldn't be handling DHCP, just captive portal.

Tim

Thread