[MLB-WIRELESS] Routing Confusion!

Sat Jan 21 13:21:06 EST 2006

Change you node to building status , update , then it should give you an
option to request a range 

Peter

-----Original Message-----
From: Asela Fernando [mailto:ace_101_ at hotmail.com]
Sent: Saturday, 21 January 2006 12:41 PM
To: d_ashburner at hotmail.com; melbwireless at wireless.org.au
Subject: Re: [MLB-WIRELESS] Routing Confusion!

Thanks this did the trick! I managed to reverse the firewall and forward
a port to my webserver.

Now I just need to get the senao, various pigtails and boxes and apply
for an address allocation. Where do I apply for one?

Thanks,
Asela Fernando

  _____  

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

  _____  

Message protected by MailGuard: e-mail anti-virus, anti-spam and content
filtering.
http://www.mailguard.com.au/mg <http://www.mailguard.com.au/mg> 