InJoy PPPoE provides full support for the PPPoE protocol and allows OS/2
systems to access the ISPs that are implementing this new protocol.
High performance is maintained and the PPPoE Plugin integrates well with the
existing features of the InJoy products. PPPoE offers ease of use and
because it uses standard protocols, it requires virtually no more knowledge
to setup than required for standard dial-up.
The setup of PPPoE is done through graphically managed profiles that integrate
all configuration and application details.
Installation |
Installed seamlessly as part of the InJoy Firewall software |
Integration |
Plugs into the InJoy Firewall as a loadable module,
maintaining the Firewall's superior speed and efficiency |
Configuration |
Multiple configuration profiles and an easy to use PM GUI for
setting the individual parameters. For the experts, all configuration
attributes are also directly editable in an ASCII file. |
Performance |
Allows sustained, secure utilitization of all your
network bandwidth. |
Connection |
Connect at firewall startup
Connect at demand
Connect manually
Idle disconnect
Session timeout disconnect
Connection loss detection
Auto re-connects |
Diagnostics |
Message log
Screen output |
Connection Sharing |
The gateway (NAT) capability in the InJoy Firewall also works great with PPPoE connections. |
Security |
All the filtering and firewall capabilities of the InJoy Firewall are available. |
VPN Support |
Coexists with the InJoy Firewall IPSec support |
One of the reasons for ISPs to implement and use PPPoE has been
to conform with a recent government rulings, requiring major ISPs
to resell residential xDSL services to other ISPs.
Among the first ISPs to support PPPoE has been
Telecom Italia Network (Tin)
Bell Nexxia,
Sympatico,
Pacific Bell,
Mindspring,
Bell Atlantic,
Earthlink
and German T-Online.
Once you are "connected" using the client, your connection will look the
same as your current connection. When you are finished, or when you've
been idle for a period of time, the client will typically be disconnected
and you will need to reconnect to use the Internet again.
Injoy PPPoE can monitor your link, and automatically reconnect.
It is your choice whether this is immediately, or on demand. In NAT
environments, this interruption will be transparent.
PPPoE generally introduces a small penalty on network bandwidth due
to the added protocol layer handling and the extra data needed for the
PPPoE signaling. This penalty is presumably no more than 5-10%, depending
on both software and usage.
A general implication of PPPoE is the transmission of large packets.
Typically packets on your network will have a maximum size of 1500 bytes,
which is the default MTU (Maximum Transmission Unit) on Ethernet.
Packets of 1500 bytes are larger than the maximum allowable PPPoE packet
size, and therefore, all machines which send data through
the PPPoE connection must have their MTU set to a smaller value (e.g. 1400).
The fragmentation technique is supposed to solve this problem, but
fragmentation introduces an extra performance hit and some applications
require their data not to be fragmented. Refer to the documentation for
more hints about the MTU.
Additional information about the PPPoE protocol is also availabe in RFC 2516,
available here.