Configure Router

Configure Router for PPPoE:3com

Important Notes on "Home Networks" Section of Website:

AS IS: This information was compiled by the author and is provided as a public service. The author is not responsible for any errors or omissions, or for any consequential problems that might result. USE AT YOUR OWN RISK.
NO LIABILITY: Use of this information may void your warranty, or cause irreparable harm to your equipment. Changing the configuration of your device may be in violation of your contract with your service provider. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES.
PRIVACY POLICY: This site collects no personal information; does not require registration; and does not use browser cookies.
SUPPORT: The author does not have the time to give individual technical support.
FEEDBACK: Email comments and suggestions to webmaster@bbarrera.com.

OK, after that stern warning I'll let you know that upgrading firmware is a standard procedure. Check out the pdf documentation or the Netgear and Zyxel support websites. But loading Zyxel firmware into a Netgear router isn't officially supported.

!!! WARNING!!!

Netgear routers will work using v3.24 firmware. Some Netgear routers can use Zyxel v3.21 firmware (but not later versions).

Regarding Zyxel firmware on a Netgear router... Only Netgear routers with bootbase 1.x can load Zyxel firmware. Only Zyxel firmware v3.21 supports both PPPoE:3com AND Netgear routers. Later versions of Zyxel firmware will not work with any Netgear router (because firmware checks manufacturer code).

!!! WARNING!!!

This page only discusses configuring these routers:

Netgear RT311/RT314 router series
Zyxel P310/P314 router series

The information should apply to the new Netgear RP114, which is basically a RT314 with a redesigned motherboard (according to PracticallyNetworked).

This section does not cover the Netgear FR314, which uses Sonicwall hardware and firmware.

Overview of Configuring Router for PPPoE:3com

Here is brief overview of the procedure to get router working with 3Com Dual Link:

Step 1: If Netgear router, check bootbase. If bootbase is v1.x then you can upgrade to Netgear v3.24 or Zyxel v3.21 firmware. If bootbase is v2.x then you can only upgrade to Netgear v3.24 firmware.

Step 2: Upgrade the router firmware.

Step 3: Configure the router for PPPoE:3com.

Step 4: Configure the router for ISP settings.

Steps 1: Check Bootbase if Netgear Router

Netgear owners can upgrade to v3.24 firmware available on Netgear support website.

I have successfully tested Zyxel v3.21 firmware on my RT314. Not all Netgear owners can upgrade to Zyxel firmware (see next paragraph). The first firmware from Zyxel that supports PPPoE:3com is v3.21 (dated January 2001).

Netgear RT314 and RT311 models with bootbase 2.x CANNOT use Zyxel firmware. You can check the bootbase by telnet into router (or thru serial port using HyperTerminal). Then go to menu 24.8 and type the command "sys version" (without the quotes).

Here is what I get, and you can see that I'm running bootbase version 1.05 dated 4/14/2000. Since I'm running bootbase 1.x, I can use Zyxel firmware v3.21 (but am running Netgear v3.24 firmware at the present time).

314> sys version

RAS version: V3.24(CA.0) | 2/8/2001
romRasSize: 837000
system up time: 40:06:37 (dc54b2 ticks)
bootbase version: V1.05 | 4/14/2000
314>

Step 2: Upgrade Firmware

I won't cover how to upgrade the firmware. Read the manual, contact router tech support, or search the Netgear/Zyxel forum on DSLreports (http://www.dslreports.com/forum/equip,9).

UPDATE May, 4, 2001: I've successfully loaded and tested the Netgear v3.24 firmware and ROM file.

UPDATE February 18, 2001: I've successfully loaded and tested the v3.21 firmware and ROM file.

UPDATE February 6, 2001: DrTCP spots the official release of Zyxel version 3.21 that fixes the 3Com Dual Link problem. I will install and test as soon as possible. Click here to get the official firmware.

UPDATE January 31, 2001: Zyxel has published the firmware upgrade as a beta release (no support).

Step 3: Configure the Router for PPPoE:3com

There are two items that must be configured to enable the Netgear router to connect with the 3Com Dual Link. These are in additions to whatever is required by your ISP (next section).

The first special configuration item is "Service Name = ISP" and it can be found in menu 11.1 - Remote Node Profile. Your screen should look similar -- the only really important options for PPPoE are "Encapsulation= PPPoE," "Service Type= Standard," and "Service Name= ISP" (and of course your login and password given to you by ISP).

------------------------------------------------------------------
                Menu 11.1 - Remote Node Profile

Rem Node Name= My_ISP             Route= IP
Active= Yes

Encapsulation= PPPoE              Edit IP= No
Service Type= Standard            Telco Option:
Service Name= ISP                   Allocated Budget(min)= 0
Outgoing:                           Period(hr)= 0
My Login= your_login_name         Schedules=
My Password= ********             Nailed-Up Connection= No
Authen= CHAP/ PAP
                                  Session Options:
                                    Edit Filter Sets= No
                                    Idle Timeout(sec)= 900

------------------------------------------------------------------

The second special configuration item is to set the PPPoE dialect to PPPoE:3com. Here are the CLI commands (menu 24.8) and instructions I originally received from Zyxel (also covered in release notes for v3.21 firmware):

----------------------------------------- -------------------------
New commands to switch between the RFC and 3com types:
"poe eth ?" help
"poe eth rfc" change to rfc type
"poe eth 3com" change to 3com type.
----------------------------------------- -------------------------

This command is only remembered by the router until it reboots or the power is cycled off/on. You can setup the router to always use PPPoE:3com by editing the router's "autoexec.net" file while in CLI mode (menu 24.8). I added the line "poe eth 3com" to the end of the file. Now the 3Com and Netgear always work together even if the rotuer reboots or you cycle the power.

Here are the CLI commands for that, with my usage notes:
"sys view autoexec.net"        note: view the autoexec.net file
"sys edit autoexec.net"         note: follow editing instructions on screen
"sys view autoexec.net"        note: verify changes

At the CLI command prompt type everything between the quotes (but not the quotes).

You should see something similar when done, pay attention to the last line of the modified autoexec.net file:

314> sys view autoexec.net
sys errctl 0
sys trcl level 5
sys trcl type 1180
sys trcp cr 96 128
sys trcl sw on
ip tcp mss 512
ip tcp limit 2
ip tcp irtt 65000
ip tcp window 2
ip tcp ceiling 6000
ip rip activate
ip rip merge on
ip icmp disc enif0 off
ppp ipcp com off
sys mbuf debug off
sys wdog sw on
poe eth 3com
314>

I had a few typing problems ("pilot error") while editing autoexec.net, so I started over by reloading the firmware. I highly recommend using the serial port connection between the PC and router when doing firmware upgrades. The only issue with the serial connection is strange cursor behavior on menu 24.10 (but this menu works fine using the Telnet interface).

Step 4: Configure the Router for ISP

I won't cover any specific ISP instructions here, if you are having trouble just read the manual and it explains which options affect establishing a connection with an ISP.

If authentication is failing then it is typically due to one or more of the following reasons:

incorrect username (check upper/lower case, extra spaces, etc)
incorrect password
ISP checks for MAC address of computer first used to successfully establish a connection (fix via menu 2)
ISP checks system name (fix via menu 1)
ISP checks domain name (fix via menu 1)

If your ISP assigned a computer name (system name) and domain name, you would have originally configured these settings in the Windows Network control panel.

Verify that Step 3 instructions were followed for menu 11.1:

"PPPoE Service Name= ISP" setting required for 3Com Dual Link ADSL Modem
encapsulation (PPPoE) and service type (Standard)
router configured incorrectly to use ISP's authentication protocols (use CHAP/PAP)

Verify that Step 3 instructions were followed for menu 24.8:

"poe eth 3com" setting required to enable PPPoE:3com protocol support

If all else fails go to the Netgear/Zyxel forum at http://www.dslreports.com/forum/equip,9 and post a question.

[ Home ] [ Up ]