|
HOW TO trace raw PPPoE traffic:
This HOWTO describes how the Ultimate V can be used on Windows as a PPPoE Server, allowing client PPPoE configurations to be tested and traced, while also providing Internet Connectivity to the client.
Server Configuration (2000/XP)
If you have access to registered IP addresses managed by a DHCP Server on your enterprise LAN, you should allow address assignment to be done via DHCP.
If you have no spare registered IP addresses, simply use a private IP address like 172.16.1.252 for the Server end of the connection and 172.16.1.253 for the Client end of the connection. To test the client's access to the Internet, simply run NAT32 Plus (Build 4044 or later), binding it to your registered adapter (Primary Interface) and to your RASPPPoE adapter (Secondary Interface).
Server Configuration (98/ME)
HKLM/System/CurrentControlSet/Services/Class/NetTrans/000x
where 000x is the key of the desired DUN Adapter. Set the IPaddress and IPMask values as needed.
Before the client connects to your new RASPPPoE Server, open Control Panel | Network on the client and select the Properties of the PPP over Ethernet Protocol. Set the MTU to 1472 bytes.
Open the Properties of the TCP/IP Protocol for that Connection and set the IP address to 172.16.1.253 or similar. If the DUN server to which you are connecting uses DHCP to obtain an IP address for the client (Windows 2000/XP), then this step is not needed.
On 98/ME systems, be sure the "Use IP header compression" option in the TCP/IP Properties of the connection is off.
Now "dial" the connection by clicking the Shortcut which the RASPPPOE.EXE program will have placed on your Desktop.
The client machine (98/SE/ME/2000/XP) will now have Internet Connectivity via the PPPoE protocol.
To trace TCP/IP traffic, simply click the NAT32P Trace Icon.
Tracing Raw PPPoE Traffic
NAT32P Builds 4045 and higher have support for tracing raw PPPoE traffic being sent and received over the Ethernet adapter which the RASPPPOE driver is using to transfer packets. This feature is useful for testing PPPoE implementations.
To trace raw PPPoE traffic, enter the commands:
start pppoed ifnwhere ifn is the NAT32P interface number of the LAN adapter to which the RASPPPOE driver is bound. Note that you will need to have Microsoft TCP/IP bound to that adapter and it should be configured to use a "dummy" IP address such as 10.1.1.1, Mask 255.0.0.0.
start pppoes ifn
Limitations
Windows 2000 Professional allows only two such connections to be in place simultaneously. Windows 2000 Server (and higher) supports more than two simultaneous RASPPPoE connections.
Due to an implementation error in the Windows 98/ME DUN Server, the clients of the DUN server on those platforms must be Windows 2000/XP PPPoE clients. Please see this link for an explanation of this problem.
NAT32P supports only one such connection, NAT32X supports up to 8 such connections.
conf mtu