| Question : Is NexGenPPP compatible with any TCP/IP stack? |
In theory yes. NexGenPPP could be attached as a driver to any TCP/IP stack by adding some glue code.
It is however not advised to attach NexGenPPP to another TCP/IP stack than the NexGenIP® one,
since the integration in that case cannot be tightly coupled. The reason is that NexGenPPP shares some internal buffers with NexGenIP and negociates some options that are used by the IPCP layer.
|
| Question : Why is NexGenPPPoE considered a separate product? |
NexGenPPPoE is considered a separate product because it needs both NexGenIP and NexGenPPP (to use the Ethernet interface and the Point-to-Point Protocol, respectively).
From a NexGenPPP point of view, NexGenPPPoE can be seen as a link-level driver.
|
| Question : Is it possible to support other than a serial-line driver? |
Yes, but to do that you might need to replace the AHDLC framing module provided with NexGenPPP and used by the serial line driver.
NexGenPPP relies on an abstraction layer that isolates the framing dependencies and consequently, different framing techniques, such as HDLC (for PPPoE), can be used.
|
| Question : How is NexGenPPP(oE) delivered? |
NexGenPPP and NexGenPPPoE are delivered either as binary libraries or as well-commented source code.
The documentation includes a Programming Manual and if the cource code is ordered, a Specification/Implementation Guide is delivered on request.
|
|
