[PLUG] Dialup Server on network with Linksys DSL/Cablemodem router

[Greg Long]

Thanks, I'm in the process of going through it right now, it looks like
it should work OK to get to the router.  That is the main goal.  That
way if Charter goes out for a little while and doesn't come back up, I
can hit the router "internally" and do a DHCP release/renew.  I imagine
that unless I set the box as a gateway, it will not let me access the
internet since the router is not going to hand out another IP - it's a
basic router, not bad for the price and what you get, but basic.

I'll report back on how this goes.

I will need to limit logons for only members of a certain group, but I
imagine that's documented.  That way only myself, and a couple other
guys can zap in to reset things should the need arise.  This is hardly a
professional application of all this, but we just want to make the most
reliable setup out of what we have.

Greg


-----Original Message-----
From: plug-admin at lists.pdxlinux.org
[mailto:plug-admin at lists.pdxlinux.org] On Behalf Of Anthony Schlemmer
Sent: Thursday, May 09, 2002 8:08 PM
To: plug at lists.pdxlinux.org
Subject: Re: [PLUG] Dialup Server on network with Linksys DSL/Cablemodem
router


I think the original poster was planning on setting up a dialup PPP 
server which sits inside the private network. When a client dials in, 
it is assigned a valid, private, IP address through PPP and is then 
part of the internal 192.168.x.x network. Once the client has an IP 
address that is part of the private network it can access the router at 
192.168.1.1. 

There are no routing issues with private IP addresses and a second 
public IP address isn't needed since the client system will be routing 
packets directly to the PPP dialup server. 

Tony

On Thursday 09 May 2002 18:22 pm, Robert McIntosh wrote:
> I've considered attempting this with my Linksys BEFSR41 Cable/DSL 
> Router as well.  I haven't spent the time to do it, for a few reasons
> - I have one dynamic IP address that AT&T's cable internet service 
> seems to think needs to be changed every week, because "assigning 
> static IP addresses has become increasingly cumbersome."
>
> Here are a few problems to consider while attempting this.
>
> 1)	En route, other routers will NOT pass private-use IP addresses
> (i.e, 192.168.x.y).  They will immediately be dropped, unless you drag

> a LONG cable along with you connected directly to your router.
> You really need a minimum of two static public IP addresses to do
> this with standard ppp - one for the client and one for the host. 
> PPTP might be something to look into, but I'm unsure if the Linksys
> router supports this, nor have I had the time to muddle through PPTP.
>  I'm sure Cisco's support it ($$).
>
> > My questions, before I begin are: will this allow me to interface 
> > with the router, and other on the LAN?
>
> You need to be explicit with packet forwarding in the Linksys router 
> to meet your particular network., otherwise you'll just be interfacing

> with the router.
>
> > It's imperative that the dialup server allows me to do this by 
> > connecting to the router internally on 192.168.1.1.
>
> You won't be able to do this.  You will only be able to refresh the 
> DHCP client (your router) locally, not remotely.  It sounds like 
> you've got cable-modem access that delivers your router a dynamic IP 
> address periodically.  This is not desirable for a ppp host.
>
> > I guess my main question is:  Since there is only one modem/phone 
> > line, should I configure it to just hand out a static IP?
>
> Absolutely!  It'd be a waste of memory to run DHCP for a single 
> client.
>
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org 
> http://lists.pdxlinux.org/mailman/listinfo/plug

-- 
Anthony Schlemmer
aschlemm at attbi.com
>>>>This machine was last rebooted:   3 days 20:30 hours ago<<


_______________________________________________
PLUG mailing list
PLUG at lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug