[TriLUG] Dumb mgetty/pppd question

[Jon Carnes]

Brian,

When I've set this up I used a 192.168.12.0/24 address range for the
folks dialing up. The PPPD server had the "secondary" address
192.168.12.1. My main router routed all 192.168.12.0/24 traffic to the
PPPD server using it's "primary" address.

Other than that the most interesting thing I remember about the setup is
to have Windows clients using PPP connections adjust their MTU size down
to 1400. I think XP clients will auto adjust, but Win98 or Win95 will
not.

Good Luck
 
On Thu, 2004-10-28 at 15:23, Brian Henning wrote:
> Among other things, Jeremy said:
> > 2 - Bridging
> >
> > There are some nifty kernel modules that allow bridging.  This setup
> > would allow you to simply give out an IP address that's already on the
> > local LAN to the remote client, and not have to worry about routing
> > issues.  Then, the dialin server could automatically bridge the packets
> > from the ppp interface to the Ethernet interface.  At least, I think
> > this is possible; I haven't done it.  Hopefully someone else can chime
> > in.
> 
> This fits in with my understanding of the semantics of the term "bridging." 
> And it sounds like exactly what I want to happen.  Can anyone point me 
> toward some docs or howtos or explanations of how to cause this to happen? 
> The implication of Jeremy's post is that simply configuring mgetty/pppd to 
> give the remote host an IP on the same subnet as the rest of the LAN isn't 
> enough, and that's all I've done so far.
> 
> Continued thanks,
> ~Brian 
>