🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.comp.linux.isp
Article #23

PPP inbound Dialup connections HELP!! (long)

#23
From: Phil Howlett
Date: Mon, 14 Jun 1999 00:00
54 lines
3173 bytes
Hi,

I've got a linux box with a Stallion card so that I can provide dial-up
connections to my network. (and out to the internet).

I've compiled the kernel for the Stallion card, and I've tested it with the
Stallion's own testing software. I can dial out on ALL lines.

I'm running a Radius server, and Portslave on my Redhat 5.2 Linux box,
running Kernel 2.2.9

My Portslave IP is setup as 192.168.12.10 and my dialup lines are all
192.168.12.20+ (from 20-28).

I can't get any dial-up connections working.

When a dialup connection occurs, the modems sing, and a connection is
established. The PPP connection doesn't happen. I've checked all the logs,
the Portslave hands the connection over to the Radius Server, the Radius
server authenticates the user, then the portslave starts the ppp connection.

My only concern is when the PPP connection starts, there is an error saying
"Route: no destination". Could I have a problem with my IP Address setup?

When I do an ifconfig from the console as root, the pppx device is not up
and running, but if I do a 'ifconfig -a' it is displayed with all the
correct values (IP, PtP, etc) but just not 'up'.

If I manually do an 'ifconfig ppp0 up' command I can actually ping the
Portslave (192.168.12.10) but not the other end of the connection
(192.168.12.20). I can see the modem Transmit/Receive lights pulse as it
tries to ping.

To cut a longs story short, my main questions are:

1).    Am I going about this the right way? Is Portslave->Radius the best
multi-dialup method? Are there alternatives, that also provide some form of
logging/accounting such as Radius does. (pref. RPM's)

2).    The "Route: no destination error", could that be cause of the ppp
interface not coming 'up' because I am not IP masquerading the machine yet
(the dialup box also has a 'real' IP Address, and it is searching for the
'real' router on the network).

3).    Could RedHat network scripts (in the /etc/sysconf/network-scripts/*)
be interfering somehow with the setup I'm trying to do? I've had trouble in
the past with RedHat not liking "specialized" software. Should I try another
distribution? If so, which one?

I'm really scratching my head hear, could anyone please give me some insight
or an alternative.

Cheers,
Phil H.
Technical Details
Message-ID: <RM793.1636$fR5.9086@ozemail.com.au>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 102983,525c77faec63e055,start
X-Google-Attributes: gid102983,public
X-Google-Thread: fe70d,525c77faec63e055,start
X-Google-Attributes: gidfe70d,public
X-Google-Thread: fc4a0,525c77faec63e055,start
X-Google-Attributes: gidfc4a0,public
From: "Phil Howlett" <pghowlett@ozemail.com.au>
Subject: PPP inbound Dialup connections HELP!! (long)
Date: 1999/06/14
Message-ID: <RM793.1636$fR5.9086@ozemail.com.au>
X-Deja-AN: 489435226
Distribution: world
X-Priority: 3
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
X-Trace: ozemail.com.au 929368241 210.84.72.211 (Mon, 14 Jun 1999 23:50:41 EST)
Organization: OzEmail Ltd, Australia
X-MSMail-Priority: Normal
NNTP-Posting-Date: Mon, 14 Jun 1999 23:50:41 EST
Newsgroups: alt.comp.linux.isp,alt.os.linux.dial-up,aus.computers.linux