Dial-up PPPoE + Radius authentication in LINUX

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Dial-up PPPoE + Radius authentication in LINUX
# 1  
Old 08-05-2010
Dial-up PPPoE + Radius authentication in LINUX

Hi All,

I am configured radius authentication server and PPPoE in my Linux systems. It is not work..

Kindly help me how to configure pppoe server to authenticate the clients via radius it is working in UNIX FreeBSD for the same not working in linux.

Can you have any configuration documents kindly share...

Regards,
ThakshinaMoorthy
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Radius authorization on Linux clients

Hello folks, I was guessing if there is a way for configuring Radius authorization on Linux clients. My meaning is to make Radius server manage the authorization/permissions when executing any commnand on my linux servers. Then, there's any way to configure this with Radius? can I also... (1 Reply)
Discussion started by: carpannav
1 Replies

2. IP Networking

authentication of VM's via PPPoE

I have two VM's running on Ubuntu box.Their name and IP addresses are give below. nas 192.168.129.153 home_user 192.168.129.152 I establish a ppp connection between the two machines #nas (server) sudo pppd noauth local lock defaultroute... (0 Replies)
Discussion started by: karthik.sharma
0 Replies

3. UNIX for Dummies Questions & Answers

Why use RADIUS for authentication as there are many ways to do it ?

I guess I probably ask a dumb question but why use RADIUS for authentication as there are many ways to do it, as authentication is basically a user/password check? What is the benifit(s) of using it ? Thanks! (3 Replies)
Discussion started by: qiulang
3 Replies

4. AIX

AIX and radius authentication

We want to use RADIUS to authenticate our AIX server logins. Can anybody tell me how to set on AIX server up to use a Radius server to authenticate or point me to documentation on setting up AIX to use Radius to authenticate user login. Our problem is that we have a few users that access our... (1 Reply)
Discussion started by: daveisme
1 Replies

5. Solaris

Soalris 10 PAM Radius authentication Module

Hello Group, I'm facing Problem with the configuration of "***pam_radius_auth.so.1***" module to be integrated with Freeradius and Funk Steel Belted Radius. Both this radius servers are able to make "Access-Accept" packet. But the SSH or Telnet client is not able to login to the system with the... (0 Replies)
Discussion started by: ImpeccableCode
0 Replies

6. IP Networking

Authentication WAP with RADIUS Server

Network Configuration Figure http://geocities.com/fy_heng/test1.JPG Dear all, I currently performing an testing using the above network configuration (Please click on the above link). On how actually the RADIUS server can authenticate the user who connect to the WAP (wireless access point)... (0 Replies)
Discussion started by: Paris Heng
0 Replies

7. SCO

Dial-Out & Dial-In Connections in OpenServer 5.0.6.

Friends, I am facing a problem in connecting two SCO Openserver 5.0.6 servers through Dial-Up connectivity as is done in the case of two Windows PCs. Please help me out with the following problems: (a) How to configure the modem? (b) How to setup a Dial-In connection? (c) How to... (1 Reply)
Discussion started by: thecobolguy
1 Replies
Login or Register to Ask a Question
PPPOE-SERVER(8) 					      System Manager's Manual						   PPPOE-SERVER(8)

NAME
pppoe-server - user-space PPPoE server SYNOPSIS
pppoe-server [options] DESCRIPTION
pppoe-server is a user-space server for PPPoE (Point-to-Point Protocol over Ethernet) for Linux and other UNIX systems. pppoe-server works in concert with the pppoe client to respond to PPPoE discovery packets and set up PPPoE sessions. OPTIONS
-F The -F option causes pppoe-server not to fork and become a daemon. The default is to fork and become a daemon. -I interface The -I option specifies the Ethernet interface to use. Under Linux, it is typically eth0 or eth1. The interface should be "up" before you start pppoe-server, but should not be configured to have an IP address. You can supply multiple -I options if you want the server to respond on more than one interface. -T timeout This option is passed directly to pppoe; see pppoe(8) for details. If you are using kernel-mode PPPoE, this option has no effect. -C ac_name Specifies which name to report as the access concentrator name. If not supplied, the host name is used. -S name Offer a service named name. Multiple -S options may be specified; each one causes the named service to be advertised in a Service- Name tag in the PADO frame. The first -S option specifies the default service, and is used if the PPPoE client requests a Service- Name of length zero. -m MSS This option is passed directly to pppoe; see pppoe(8) for details. If you are using kernel-mode PPPoE, this option has no effect. -s This option is passed directly to pppoe; see pppoe(8) for details. In addition, it causes pppd to be invoked with the sync option. -L ip Sets the local IP address. This is passed to spawned pppd processes. If not specified, the default is 10.0.0.1. -R ip Sets the starting remote IP address. As sessions are established, IP addresses are assigned starting from ip. pppoe-server auto- matically keeps track of the pool of addresses and passes a valid remote IP address to pppd. If not specified, a starting address of 10.67.15.1 is used. -N num Allows at most num concurrent PPPoE sessions. If not specified, the default is 64. -O fname This option causes pppoe-server to tell pppd to use the option file fname instead of the default /etc/ppp/pppoe-server-options. -p fname Reads the specified file fname which is a text file consisting of one IP address per line. These IP addresses will be assigned to clients. The number of sessions allowed will equal the number of addresses found in the file. The -p option overrides both -R and -N. In addition to containing IP addresses, the pool file can contain lines of the form: a.b.c.d-e which includes all IP addresses from a.b.c.d to a.b.c.e. For example, the line: 1.2.3.4-7 is equivalent to: 1.2.3.4 1.2.3.5 1.2.3.6 1.2.3.7 -r Tells the PPPoE server to randomly permute session numbers. Instead of handing out sessions in order, the session numbers are assigned in an unpredictable order. -u Tells the server to invoke pppd with the unit option. Note that this option only works for pppd version 2.4.0 or newer. -o offset Instead of numbering PPPoE sessions starting at 1, they will be numbered starting at offset+1. This allows you to run multiple servers on a given machine; just make sure that their session numbers do not overlap. -f disc:sess The -f option sets the Ethernet frame types for PPPoE discovery and session frames. The types are specified as hexadecimal numbers separated by a colon. Standard PPPoE uses frame types 8863:8864. You should not use this option unless you are absolutely sure the peer you are dealing with uses non-standard frame types. -k The -k option tells the server to use kernel-mode PPPoE on Linux. This option is available only on Linux kernels 2.4.0 and later, and only if the server was built with kernel-mode support. -h The -h option prints a brief usage message and exits. OPERATION
pppoe-server listens for incoming PPPoE discovery packets. When a session is established, it spawns a pppd process. The following options are passed to pppd: nodetach noaccomp nobsdcom nodeflate nopcomp novj novjccomp default-asyncmap In addition, the local and remote IP address are set based on the -L and -R options. The pty option is supplied along with a pppoe command to initiate the PPPoE session. Finally, additional pppd options can be placed in the file /etc/ppp/pppoe-server-options (which must exist, even if it is just empty!) Note that pppoe-server is meant mainly for testing PPPoE clients. It is not a high-performance server meant for production use. AUTHORS
pppoe-server was written by David F. Skoll <dfs@roaringpenguin.com>. The pppoe home page is http://www.roaringpenguin.com/pppoe/. SEE ALSO
pppd(8), pppoe(8), pppoe-sniff(8), pppoe-relay(8), /usr/share/doc/pppoe/README.Debian.gz 4th Berkeley Distribution 3 July 2000 PPPOE-SERVER(8)