Hi all, I am running a small non-profit college in Zambia, and we've just managed to get an internet connection to the site (£200 per month for a 2Mbit 10:1 contested line. It's enough to make you weep). I've done bits and pieces of networking in the past so I'm not a complete newbie, but I am nowhere near an expert. My question is probably simple, but I will start with the context...
The incoming modem (WiMAX) can serve 10 IP addresses. I have the college (30 IPs), then two residential properties (12 IPs), with runs of 110 metres between each (220 metres from the modem to the final point. We get a lot of heavy rain and lightning storms here, so I decided against wireless bridging, and went for Cat5 buried in ducting (plus it's cheaper, and we're a charity) - because of the length of each individual run, I put hubs at the mid point as a cheap booster, and have daisy-chained two routers.
The network looks like this:
0) ISP WiMAX broadcast
1) Modem (10.1.1.254) ->
1a) Wifi Access Point [TP-Link router in AP mode]->
1b) Hub ->
2) Router Using 10.1.1.X as WAN port [TP-Link] (192.168.0.1) ->
3) Router Using 192.168.0.X as WAN port [TP-Link] (192.168.1.1) ->
3b) Hub ->
3c) Wifi Access Point [D-Link]
This is working well and is nice and simple.
First question - I need a simple and low-resource tool to run on a machine on the final network (192.168.1.1) to give me logs and an alarm if (3), (2), (1) or (www.google.com) don't respond to a ping. At the moment I am using freeping by Tools4Ever but this doesn't produce logs. The main purpose is so that I have evidence on which to base an internet availability calculation (the ISP claims 99%, but it is nowhere near this). The purpose of pinging my own routers and google.com is so I can see at a glance that if my routers and modem are ok, but google.com is not, then it is the ISP that is down. I have checked out a lot of tools but nothing does exactly what I want, and my network connection is so slow I can't just download hundreds to try them. I just need a list of devices, whether they are responding to pings, and also the results logging to a file so I can see which part of the network went down and at what time.
Next question - I have file servers on the end network (192.168.1.1) and I would like to give computers on the (10.1.1.254) and (192.168.0.1) networks access to them. From 192.168.1.X I can see 'down' the network, but 10.1.1.X can't see 'up'. Can anyone give me advice on the routing to achieve this?
Thanks,
The incoming modem (WiMAX) can serve 10 IP addresses. I have the college (30 IPs), then two residential properties (12 IPs), with runs of 110 metres between each (220 metres from the modem to the final point. We get a lot of heavy rain and lightning storms here, so I decided against wireless bridging, and went for Cat5 buried in ducting (plus it's cheaper, and we're a charity) - because of the length of each individual run, I put hubs at the mid point as a cheap booster, and have daisy-chained two routers.
The network looks like this:
0) ISP WiMAX broadcast
1) Modem (10.1.1.254) ->
1a) Wifi Access Point [TP-Link router in AP mode]->
1b) Hub ->
2) Router Using 10.1.1.X as WAN port [TP-Link] (192.168.0.1) ->
3) Router Using 192.168.0.X as WAN port [TP-Link] (192.168.1.1) ->
3b) Hub ->
3c) Wifi Access Point [D-Link]
This is working well and is nice and simple.
First question - I need a simple and low-resource tool to run on a machine on the final network (192.168.1.1) to give me logs and an alarm if (3), (2), (1) or (www.google.com) don't respond to a ping. At the moment I am using freeping by Tools4Ever but this doesn't produce logs. The main purpose is so that I have evidence on which to base an internet availability calculation (the ISP claims 99%, but it is nowhere near this). The purpose of pinging my own routers and google.com is so I can see at a glance that if my routers and modem are ok, but google.com is not, then it is the ISP that is down. I have checked out a lot of tools but nothing does exactly what I want, and my network connection is so slow I can't just download hundreds to try them. I just need a list of devices, whether they are responding to pings, and also the results logging to a file so I can see which part of the network went down and at what time.
Next question - I have file servers on the end network (192.168.1.1) and I would like to give computers on the (10.1.1.254) and (192.168.0.1) networks access to them. From 192.168.1.X I can see 'down' the network, but 10.1.1.X can't see 'up'. Can anyone give me advice on the routing to achieve this?
Thanks,