RE: [smartBridges] FW: PPPoE does not work with current firmware.

[Michael Saathoff]

Title: Message

I'm hardly using the Windows PPPoE.  I could stomach using RASPPPoE if I had to for the clients that need it.  What's killing my business is the inability to use ANY of the hardware based routers on the market that support PPPoE. 

 

Linksys

D-Link

SMC

None of them work.

 

This is how we provide provide service to our customers that have multiple machines, whether it be home networks or business.

 

I know you said you would update us if there is any change/improvement in handling PPPoE, but what I, and others who are having the same problems really need is to know, is are you working on a fix and when.  Otherwise I have to find a new vendor.  I don't want use someone else as I've had good luck with the SB gear in every other way however, your leaving me little choice.

 

--Mike

 

 

-----Original Message-----
From: Alex Wong [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 04, 2003 9:36 AM
To: 'Blaine Fleming'; 'Michael Saathoff'
Subject: RE: FW: PPPoE does not work with current firmware.

Hi Blaine/Michael,

To date, our finding shows that PPPoE is working fine with airBridge (CD version 1.5) if using RASPPPoE client. The Win native PPPoE client is not working and we are investigating on it. I understand your preference in using the Win native PPPoE client as this is out of the box and easy to roll out.

But Microsoft may not be the best tool if there is limitation in its feature. Pls see below extract from www.raspppoe.com

FAQ 3. Windows XP/.NET comes with builtin PPPoE support, why use RASPPPOE instead?

Even though Windows XP/.NET comes with builtin PPPoE support, Microsoft's implementation is not yet as sophisticated as RASPPPOE. See this feature comparison chart:

Feature	Microsoft PPPoE in Windows XP/.NET	RASPPPOE
Seamless integration with the operating system	Yes	Yes
Fully exploits the maximum possible PPPoE MTU (1492)	No	YES
Supports Internet Connection Sharing and NAT seamlessly	No	YES
Allows tuning the TCP RWIN without registry changes*	No	YES
Offers PPPoE server (Access Concentrator) capability	No	YES

* To increase the autonegotiated TCP RWIN with RASPPPOE, use the Specify Link Speed option and specify a link speed of 101Mbps or greater, e.g. enter 101000 (kbps) as the link speed the protocol should report. Windows XP/.NET will then autonegotiate a TCP RWIN of approx. 64KB instead of the default 16KB, which is often too small for broadband connections.

In the interrim, pls use RASPPPoE client if using with airBridge (current version).

Below is the difference between the old and new ver of airBridge.

 

With the addition of remote management and the multi MAC support, here are the major differences in the behavior. As this may affect the changes in the WISP operator’s network design, these differences should be noted and upgrade should be planned properly.

airBridge	New airBridge (Indoor, Outdoor and TOTAL)
Firmware – 09.xx series (currently at 09.10)	Firmware - 01.xx series (currently at 01.04)
Transparent device. Device IP number used for configuration purpose only.	An active Network Element with it’s own IP number that is used for various functions.
From the AP side, only the MAC number of the PC is visible. This number is used for MAC level authentication.	From the AP side MAC number of the airBridge is visible. This number should be used for the MAC authentication.
Can be connected only to a single PC.	Can be connected to PC with airBridge gateway setting 0.0.0.0 Can be connected to LAN with valid gateway and IP settings using a cross cable.
No DHCP client available in the device.	DHCP client implemented in the device. The airBridge obtains DHCP lease from either Ethernet or wireless ports.
The device supports only one MAC address on the Ethernet side.	Up to 64 MAC addresses can be supported on the Ethernet side.
Remote configuration not possible from the wireless side. The device must be configured from the Ethernet side.	Remote configuration is possible from both Ethernet and Wireless side.
Completely transparent bridge that passes all the Ethernet frames, irrespective of the protocol.	The traffic is limited to IP packets. PPPoE frames are not supported.
Gateway settings not required.	Gateway settings have to be set to configure the device on LAN
Factory Settings IP 192.168.0.22 MASK 255.255.255.0	Factory Settings IP 192.168.0.22 MASK 255.255.255.0 Default Gateway 0.0.0.0

 

We will update you again if there is any change/improvement in handling PPPoE.


Alex
sB Tech Support




-----Original Message-----
From: Blaine Fleming [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 04, 2003 7:36 AM
To: 'Michael Saathoff'
Cc: '[EMAIL PROTECTED]'
Subject: Re: FW: PPPoE does not work with current firmware.


I have been doing extensive testing of PPPoE with the newest firmware on
the airBridge.  Below is a list of the equipment and combinations that were
used in testing.

Clients:
WinXP with built in PPPoE client
WinXP with RAS PPPoE
W2K with built in PPPoE client
W2K with RAS PPPoE
Win98 with RAS PPPoE
Linksys BEFSX41
Sonciwall Pro 200

Client Bridges:
AB indoor with firmware from CD Release 1.5
AB indoor with firmware from CD Release 1.43
AB outdoor with firmware from CD Release 1.43
AB outdoor with firmware from CD Release 1.5

Access Point:
Orinoco AP-1000 (Bridging)
Orinoco COR-1100 (AP Mode with Bridging)
Orinoco ROR-1000 (AP Mode with Bridging)

PPPoE Servers:
Mikrotik 2.6.12
Mikrotik 2.7
ServPoET BMS 200

What I found is that RasPPPoE does work with any combination of bridges,
access points and PPPoE concentrators.  Hardware solutions, windows native
and other PPPoE client software will not function on the new firmware
regardless of the other equipment.  All of this stuff works fine with the
previous (CD Release 1.43) firmware.  My testing shows that PPPoE discovery
(protocol 0x8863) works fine but the airBridge does not transport PPPoE
session (0x8864) frames back to the client.  Sniffing the network shows
that the frames are received by the airBridge.

My question still is, what changed between the last two firmware releases
that makes/breaks PPPoE for many different client types?

--Blaine