[CUWiN-Dev] Re: static gateways
Matt Isaacs
matthew.isaacs at gmail.com
Mon Aug 28 17:20:00 CDT 2006
OK. It looks like we got the static gateways working. I've drafted
some instructions on how to set it up. The instructions are available
on the wiki: http://newiki.cuwireless.net/index.php/User:Isaacsm
Comments and suggestions appreciated.
--Matt
On 8/28/06, Matt Isaacs <matthew.isaacs at gmail.com> wrote:
> Setting up NAT fixed it.
>
> On 8/28/06, David Young <dyoung at pobox.com> wrote:
> >
> > On Mon, Aug 28, 2006 at 03:36:46PM -0500, Brandon Bowersox wrote:
> > > On Aug 28, 2006, at 3:11 PM, David Young wrote:
> > >
> > > >On Mon, Aug 28, 2006 at 02:35:55PM -0500, Matt Isaacs wrote:
> > > >>OK. I've setup ifconfig.sip0, mygate, and internet-connected. The
> > > >>situation currently is that the gateway can send traffic out to the
> > > >>internet, and the second node can now ping the the outside
> > > >>interface on the
> > > >>gateway node. The routes also appear to be holding. However,
> > > >>traffic from
> > > >>the second node still is not being routed to the internet. A
> > > >>traceroute
> > > >>shows anything beyond the gatway node (specifically its wireless ip,
> > > >>10.0.x.x) to time out.
> > > >
> > > >Ah. NAT is not active on the interface. You need to add /etc/
> > > >pf.conf,
> > > >too. Use a rule like the one that /etc/dhclient-exit-hooks creates.
> > >
> > > What aspects of this functionality can and should be built into
> > > nodeconfig? We want nodeconfig to be an easy way to do this without
> > > making special files in /permanent.
> >
> > nodeconfig needs knobs both for setting a static IP (already in
> > there?) and for configuring a default route on one interface.
> >
> > Dave
> >
> > --
> > David Young OJC Technologies
> > dyoung at ojctech.com Urbana, IL * (217) 278-3933
> > _______________________________________________
> > CU-Wireless-Dev mailing list
> > CU-Wireless-Dev at lists.cuwireless.net
> > http://lists.chambana.net/cgi-bin/listinfo/cu-wireless-dev
> >
>
>
More information about the CU-Wireless-Dev
mailing list