Date: Wed, 23 Mar 2005 13:00:03 -0600 From: "Chris Tusa at Linisys, LLC" <linisys@gmail.com> To: freebsd-net@freebsd.org Cc: brian@awfulhak.org Subject: Re: PPP Lan Bridge Message-ID: <308313860503231100635d6114@mail.gmail.com> In-Reply-To: <3083138605032214175b078a34@mail.gmail.com> References: <3083138605032116273eacd0f7@mail.gmail.com> <20050322122924.71b7c46a@dev.lan.Awfulhak.org> <30831386050322120630eaf58d@mail.gmail.com> <20050322220254.19994f8e@dev.lan.Awfulhak.org> <3083138605032214175b078a34@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
OK, I put the solution in place and had great results. The ONLY issue that I had, is with some routing. In order for the rest of the network to communicate with the hosts at the maintainence shed, I had to set a 'static route'. I did so using DHCP, no problems there. However, I have a problem on the PPP server in its routing table: * I cannot add the static route to 'rc.conf': static_routes="theshed" route_theshed="192.168.1.234 192.168.1.233" because it creates the table entry pointing to the wrong interface - fxp0 instead of tun0 * I tried the same thing in the 'ppp.conf' file. I tried several variations with no success: server: add 192.168.1.234 192.168.1.233 add 192.168.1.234/30 192.168.1.233 * I tried placing a shell script to be run in 'ppp.linkup' on the server server: bg /etc/ppp/setroute.sh and then setroute.sh: #!/bin/sh route delete 192.168.1.234 route add 192.168.1.234 192.168.1.233 STILL FAILS! But once the PPP link is established, if I add the route manually or run the shell script, it works fine thereafter. So the problem is that the routing table gets updated with the WRONG interface. The FreeBSD man page for 'route' is unclear about how to specify the interface on the command line. Any additional advice? On Tue, 22 Mar 2005 16:17:53 -0600, Chris Tusa at Linisys, LLC <linisys@gmail.com> wrote: > Thanks Again, > > Just a quick note on your last reply, don't know whether this will > make an impact: > > > I guess the missing bit is that the timeclock machine needs a special > > routing table with 192.168.1.234/30 on it's crossed-over ethernet > > interface and 192.168.1.233 as the default route, allowing data to > > get back to the rest of the /24 subnet. > > The timeclock itself is a proprietary STANDALONE device, not an actual > machine with an OS. It has its own configuration interface via its LCD > screen and buttons. It only allows me to add the IP, Netmask & > Gateway. So I probably can't perform routing table changes to that > device. > > ( http://www.timeclockplus.com/products/hardware/markIII/mark3.aspx ) > > > > When you get it all working it'll start to make sense (if it doesn't > > already). > > I will try the configuration tommorrow and see what happens. Thanks so much. > > -- > Chris Tusa > linisys@gmail.com > http://people.linisys.com/ctusa > > Buy books from my Half.com inventory: > http://half.ebay.com/shops/shops.jsp?seller_id=1691584 > -- Chris Tusa linisys@gmail.com http://people.linisys.com/ctusa Buy books from my Half.com inventory: http://half.ebay.com/shops/shops.jsp?seller_id=1691584
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?308313860503231100635d6114>