Linux PPPo. E Server | Sabin Shrestha's Personal Site. Feb, 2. 00. 8 1. Introduction. PPPo. E stands for Point to Point Protocol over Ethernet. It is an OSI Layer Two protocol which uses the PPP (Point to Point) protocol to connect a client system to a server system in a one to one network link. All traffic for a PPPo. E connected client must go thru the PPPo. E server to reach the client. A PPPo. E server can therefore be used to route, NAT, firewall, and perform QOS traffic shaping. Since the newer versions of the PPP daemon support RADIUS attributes client authentication and configuration can be done remotely at the RADIUS server. Linux is an excellent, high performance operating system which can easily support a large number of PPPo. E clients upon modest hardware platforms. This document will probably be of interest to Internet Service Providers, Information Technologists, and other Network Managers. Disclaimer. No liability for the contents of this documents can be accepted. ![]() Use the concepts, examples and other content at your own risk. As this is a new edition of this document, there may be errors and inaccuracies, that may of course be damaging to your system. Proceed with caution, and although this is highly unlikely, the author(s) do not take any responsibility for that. All copyrights are held by their respective owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark. Naming of particular products or brands should not be seen as endorsements. You are strongly recommended to make a backup of your system before major installation and backups at regular intervals.
PPPoE server on OpenWRT (Page 1) — WhiteRussian — OpenWrt — Wireless Freedom. It seems there are only two (free) choices - (rp-pppoe) pppoe-server and pppoed. Hacking; Java & JavaEE5. Software; Linux PPPoE Server. 18. Feb, 2008. All traffic for a PPPoE connected client must go thru the PPPoE server to. Hardware. Linux is a high performance OS. As evidenced by the current trend to deliver Linux firmware on SOHO routers and wireless devices. PPPo. E is a CPU intensive task and running multiple instances of a server daemon will inevitably eat up memory. We have built a number of these PPPo. E server systems over the past couple of years and have observed what appears to be a linear relationship between the number of simultaneously connected clients and system CPU and memory requirements. It is safe to estimate that one connected client will require about 2 Mhz of system CPU on an INTEL Pentium- III processor. It is equally safe to estimate that one connected client will require about 2 Mbytes of system memory. These numbers have been estimated based upon our experience with previous PPPo. E server systems we have built that handled small numbers of connections (terminations). The most simultaneous terminations we have observed on one of our systems is 1. That observation was made on a 2. ![]() Mhz Pentium with 2. Mbytes of memory. That system was also doing per user traffic shaping and NAT. The system felt sluggish at the command line but the users did not complain about performance. Requirements. Your system will require two ethernet NIC (Network Interface Card)s. This is because PPPo. E must operate on an ethernet interface which does not have an IP address assigned to it. The other NIC will have an IP address assigned to it for access to the network. Multiple PPPo. E connections will terminate on the NIC which has no address and they will be forwarded thru the NIC which does have an address assigned. Any Pentium III system with sufficient RAM should easily terminate 1. You should use NICs capable of 1. Mbit or Gigabit performance. Estimating System Capacity. As described in paragraph 2 above, your system will require about 2 Mbytes of memory and 2 Mhz of CPU per active termination. That is in addition to whatever memory and CPU Linux and the other software running on your server require. It is probably safe to assume that a 5. Mhz Pentium with 5. Mbytes of RAM will terminate about 2. When in doubt, play it safe. Both CPU and memory are inexpensive. ![]() Multi- processor systems would be more desirable in this service because of lower system latencies. Also multiple PPPo. E servers are more attractive than a single powerful server because when a server fails the other servers on the network can pick up the load. Redundancy is good. As it turns out there is a bug either in PPP or in the PPPo. E server which will cause problems when the PPP2. As far as I am aware this is an unavoidable problem unless you wish to modify the actual source code for PPP or PPPo. E as appropriate. Therefore you should not expect to terminate more than 2. PPPo. E connections on a home brew PPPo. E server. Hopefully this problem will be fixed by the developers. I have not mentioned the problem to the developers. Multiple servers running in parallel on a LAN backbone are more reliable anyway. That is how I bypassed this particular limitation. Software. Any recent Linux distribution can be used to build a PPPo. E server. Stick with kernel version 2. Earlier versions of the software did not ship with versions of PPP which supported RADIUS and therefore support for RADIUS in PAM was required. Later releases of Linux use the more recent versions of the PPP daemon. Most distributions of Linux will provide the required packages on their installation media. I am using Open Su. SE 1. 0. 1 in my build and all the packages required are on the installation CDs. I like Open Su. SE because kernel mode PPPo. E support is built into the distribution. That means that you don’t need to recompile the kernel to use kernel mode. You can also download and build the packages from their respective sites, if you are particularly adept with your flavor of Linux and wish to build using it. RP- PPPo. EThe Roaring Penguin PPPo. E server software is required. Use version 3. 5 or later. As mentioned elsewhere this version of the server supports kernel mode PPPo. E, when it and the kernel are built for that mode. You can get an RPM for Su. SE 1. 0. 0 here. The authors of RP- PPPo. E claim that the PPPo. E server they have released is not really for production use. We have built and operated RP- PPPo. E based servers for two years now. They have been robust and have performed quite well in an environment with about 2. DSL and wireless customers hitting two servers attached directly to our backbone. Note: Since the time of the above writing we have been operating two 7. MHz PIII systems with 5. MBytes RAM to terminate about 4. PPPd. The version 2. PPP daemon should also be installed on your system. Prior versions may not have support for RADIUS built in to them. This version supports per user configuration via RADIUS attributes. If you understand RADIUS attributes you will have little problem setting up per user configuration. This HOWTO is not going to cover that until it is more mature. We will only set up user login via RADIUS. The radiusclient software provides the configuraton files for the PPP daemon’s RADIUS plugin. On Su. SE 1. 0. 0 it needs to be installed separately. Open. Su. SE 1. 0. Other versions of Linux may install it as part of the PPP daemon installation. The Su. SE 1. 0. 0 RPM can be found here. I am sorry, I do not have a link for the tar. Configuraton. Before configuring your PPPo. E server you need to make sure you are logged on as root. You should turn off your firewall, if you have one running. The PPP daemon plugin’s use the files which are also used by radiusclient. These files are located in the /etc/radiusclient directory. There are two files which must be configured to make your PPPo. E server use a RADIUS server to authenticate users. If you do not want your PPPo. E server to authenticate users via RADIUS you can skip this section and go to section 4. Open the text file you find at /etc/radiusclient/serves in an editor and insert the IP address of your RADIUS server and the secret this client will use when talking to the RADIUS server. That file will now look something like this: #Server Name or Client/Server pair Key#—————- —————#portmaster. My. Radius. Secret. The other file you need to open in your text editor is /etc/radiusclient/radiusclient. In the RADIUS settings section of that file you need to specify your authserver IP address and your acctserver IP addresse. You should also comment out the existing entries which point to localhost. PPPd configuration. PPP is very powerful and complex protocol for building point to point links over just about any medium imaginable. PPPo. E is a “wrapper protocol” around the PPPd software that establishes and tears down PPP connections over ethernet. PPPo. E calls PPPd once it has the necessary information that PPPd requires to maintain a connection. The PPPd configuration files reside in /etc/ppp. There are two files which are of interest to us. They are /etc/ppp/options and /etc/ppp/pap- secrets. We will do the minimum necessary to configure the PPP daemon to support PPPo. E connections. There are many configurable options in the /etc/ppp/options file. A careful reading of the file would be informative to those who have never operated a PPP server. Changes to /etc/ppp/options: You will need to open /etc/ppp/options in your text editor. Most configuration files in *nix use a pound (#) sign at the beginning of a line to indicate the line is a comment. Find the line which reads nologin and change it to read #nologin. Find the line which reads #mru 1. Find the line which reads #mtu 1. Find the line which reads #noreplacedefaultroute and uncomment it. Find the line which reads #proxyarp and uncomment it. This is only necessary if you are going to assign some clients public IP addresses. If all clients will be NATted, you do not need proxyarp enabled. The safe choice is to enable proxyarp because at worst it generates an error message in the logs. Find the line(s) which start with #ms- dns 1. This is where you configure your DNS server for your clients. Clients will be assigned the DNS servers specified here. You should uncomment one of these lines and edit it to assign a DNS server to your clients. Lastly there are two lines which you need to add at the bottom of the /etc/ppp/options file. They are: plugin radius. Mikrotik Pppoe Hack - Free Download Mikrotik Pppoe Hack Software Your mission is to hack into the most secure system in the world and bring it down! With the .. Simple yet challenging addictive puzzle memory game! Come see what the hype is about, for FREE! Welcome to the Memory Core Universe, ..
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
September 2016
Categories |