[CUWiN-Dev] CUWiN routers tunnel "home" through NATs

[dan blah]

seems the release notice wasnt forwarded to any of the lists.
On 9/20/06, Bill Comisky <bcomisky at pobox.com> wrote:
> On Wed, 20 Sep 2006, David Young wrote:
>
> > On Wed, Sep 20, 2006 at 02:19:05PM -0500, Bill Comisky wrote:
> >> On Tue, 19 Sep 2006, David Young wrote:
> >>
> >>> On Tue, Sep 19, 2006 at 05:32:46PM -0400, John Atkinson wrote:
> >>>> Is this slated specifically for the Urbana network?
> >>>
> >>> All CUWiN routers will tunnel home.  I realize that may not be desirable
> >>> on some networks.  If it is not desirable for your network, you can
> >>> set utd=NO at the end of src/boot-image/extras/etc/rc.conf.d/utd before
> >>> you build.
> >>>
> >>
> >> Ahh...  I thought this was just on trunk and not in 0.7.0 but I notice now
> >> that the 0.7.0 branch was copied over from trunk again around r4206.  I
> >> was testing out quagga 0.99.5 vs. the 0.7.0 release branch and getting
> >> some zebra log messages I couldn't make sense of, but these must be
> >> related to the phoning home.  Sure enough utd is running:
> >>
> >> # ps auxw | grep utd
> >> root    1997  0.0  2.6  64  836 ?      Ss    7:41AM 0:00.66 /usr/sbin/utd
> >> 10.0.233.56 0.0.0.0 64.198.255.12 192.168.49.1
> >>
> >> I kept seeing routing entries like the one below appear and dissappear in
> >> the routing table (with gre# index incremented) for the 192.168.49.x
> >> subnet, which of course doesn't exist on my LAN.
> >>
> >> 192.168.49.1       192.168.49.249     UH          -   gre16
> >>
> >> BTW, the messages I was getting from zebra (with kernel and events
> >> debugging on) are below.  Was the tunneling stuff ready to go as of r4206?
> >> Or maybe it should be disabled by default on the 0.7.0 release?
> >
> > The tunneling is working quite well.  I think 0.7.0 was already released
> > with it.
>
> gotcha, hadn't seen the announcement.
>
> > Creating/destroying tunnels does make Zebra awfully noisy, but I don't
> > think there is any harm in it.
>
> cool, I thought it was trying to tunnel and failing based on seeing the
> "if_ioctl(SIOCGIFFLAGS) failed: Device not configured" and "Can't lookup
> mtu by ioctl(SIOCGIFMTU)" messages.
>
> bill
>
> --
> Bill Comisky
> bcomisky at pobox.com
> _______________________________________________
> CU-Wireless-Dev mailing list
> CU-Wireless-Dev at lists.cuwireless.net
> http://lists.chambana.net/cgi-bin/listinfo/cu-wireless-dev
>


-- 
Daniel