<html><div style='background-color:'><DIV class=RTE>
<P>Thanks this did the trick! I managed to reverse the firewall and forward a port to my webserver.</P>
<P>Now I just need to get the senao, various pigtails and boxes and apply for an address allocation. Where do I apply for one?</P>
<P>Thanks,<BR>Asela Fernando<BR></P></DIV>
<DIV></DIV>
<DIV></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #a0c6e5 2px solid; MARGIN-RIGHT: 0px"><FONT style="FONT-SIZE: 11px; FONT-FAMILY: tahoma,sans-serif">
<HR color=#a0c6e5 SIZE=1>
<DIV></DIV>From: <I>"David Ashburner" <d_ashburner@hotmail.com></I><BR>To: <I>melbwireless@wireless.org.au</I><BR>Subject: <I>Re: [MLB-WIRELESS] Routing Confusion!</I><BR>Date: <I>Fri, 20 Jan 2006 22:09:16 +0000</I><BR>MIME-Version: <I>1.0</I><BR>X-Originating-IP: <I>[144.133.95.52]</I><BR>X-Originating-Email: <I>[d_ashburner@hotmail.com]</I><BR>X-Sender: <I>d_ashburner@hotmail.com</I><BR>Received: <I>from www.wireless.org.au ([202.161.127.82]) by bay0-mc8-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 20 Jan 2006 14:11:54 -0800</I><BR>Received: <I>from www.wireless.org.au (www [127.0.0.1])by www.wireless.org.au (8.13.1/8.13.1) with ESMTP id k0KM9PAF030161;Sat, 21 Jan 2006 09:09:38 +1100</I><BR>Received: <I>from hotmail.com
(bay101-f38.bay101.hotmail.com [64.4.56.48])by www.wireless.org.au (8.13.1/8.13.1) with ESMTP id k0KM9Jln030153for <melbwireless@wireless.org.au>; Sat, 21 Jan 2006 09:09:19 +1100</I><BR>Received: <I>from mail pickup service by hotmail.com with Microsoft SMTPSVC;Fri, 20 Jan 2006 14:09:17 -0800</I><BR>Received: <I>from 64.4.56.200 by by101fd.bay101.hotmail.msn.com with HTTP;Fri, 20 Jan 2006 22:09:16 GMT</I><BR>><BR>>Hi Asela,<BR>><BR>> >From: "Asela Fernando"<BR>> ><BR>> >I've installed OpenWRT WhiteRussian RC4 on the R100, disabled the firewall,<BR>> >broke the bridge between the radio and the LAN ports and configured the WAN<BR>> >port.<BR>>Have you got IP forwarding configured?<BR>>cat /proc/net/ipv4/ip_forward should be 1<BR>>It may be that the init.d script that sets forwarding up is sopmeting you<BR>>moved
/ disabled.<BR>>but more likely it's because other machines do not know that the R100 is a<BR>>gateway between the two network segments.<BR>><BR>> >Until I hit this wall:<BR>> >A Computer connected to the R100 (via lan or radio), cannot communicate at<BR>> >all with a computer connected to the Wl500G, and vice versa.<BR>> >A Computer connected to the radio, cannot communicate with a computer on<BR>> >the<BR>> >lan ports of the R100 and vice versa.<BR>> >This would be because each interface has different subnets.<BR>> >Now I just need to figure out how to route between them.<BR>> ><BR>>The problem is more likely not the router between the networks but the other<BR>>machines oneither segment not knowing that the router is there.<BR>><BR>>ON your private LAN the PC , Webserver etc. probably all use the
WL500G as<BR>>the default route. They send packets to the 10.10.130.0 network to that<BR>>machine for forwarding and it drops them ( or sends them down the cable<BR>>connection) because it ddoes not know where the 10.10.x.x network is.<BR>><BR>>On your MW LAN ( the 10.10.130.0) the machines you connect will probably<BR>>have the R100 as the default route ( that's OK) so your ping etc. gets<BR>>routed to the destination machine but the response back gets lost.<BR>><BR>> >So I just need some step by step instructions to setup routes between the<BR>> >interfaces on the R100, and to get a firewall up to protect the WAN port of<BR>> >the R100 which links my home network to MW, setup DHCP to hand out IPs to<BR>> >clients connecting via the Senao and DNS and give access to port 80 on my<BR>> >webserver to
people on MW.<BR>><BR>>Routing first.<BR>>Easiest thing to try is to set up a route entry on the WL500G so when it<BR>>gets packets for 10.10.130.0 it knows where to send them.<BR>>first add the gateway machine to the table<BR>>route add -host 192.168.1.4 vlan1 <- or whatever the interface used for<BR>>192.168.1.0 is<BR>>then add the network<BR>>route add -net 10.10.130.0 netmask 255.255.255.0 gw 192.168.1.4<BR>>then try to ping the 10.10.130.18 from the WL500G - that shoud now work<BR>>Other machines on your 192.168.1.0 network should also be able to<BR>>communicate to the 10.,10.130.0 network. and vice versa.<BR>><BR>>Then the firewall.<BR>>Your set -up is exactly the same as mine ( well, I use 2 WRT54 ) . You<BR>>could try the MW Router project hotspot package on the R100. It will set
up<BR>>yout iptables the way you need them and put in place the firewall between<BR>>your MW (public) segment and your provate segment.<BR>><BR>>http://www.melbournewireless.org.au/wiki/?MWRPHotspot<BR>><BR>>I can walk you through installation and configuration, when you are ready to<BR>>try it.<BR>><BR>>but not today - I'm off to the beach :)<BR>>cheers, dna<BR>><BR>><BR>>_______________________________________________<BR>>Melbwireless mailing list<BR>>Melbwireless@wireless.org.au<BR>>http://wireless.org.au/mailman/listinfo/melbwireless<BR></FONT></BLOCKQUOTE></div></html>