Re: PPP Lan Bridge

From: Brian Somers (brian_at_Awfulhak.org)
Date: 03/24/05

  • Next message: c0ldbyte: "Re: Resolving MAC address" 
    Date: Thu, 24 Mar 2005 11:18:22 +0000
To: "Chris Tusa at Linisys, LLC" <linisys@gmail.com>

    I would have thought that

    server:
        add 192.168.1.234/30 HISADDR

    in ppp.linkup should work...

    On Wed, 23 Mar 2005 13:00:03 -0600, "Chris Tusa at Linisys, LLC" <linisys@gmail.com> wrote:
    > 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
    > 

    -- 
Brian Somers                                          <brian@Awfulhak.org>
Don't _EVER_ lose your sense of humour !               <brian@FreeBSD.org>
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
  • Next message: c0ldbyte: "Re: Resolving MAC address"
    • Quantcast