Transfer of IPCOP to Endian

[Guest]

[craigray]

Hi all,
    Moving to Endian from an IPCOP machine, hopefully to do some AD integration.  Having a little trouble getting the machine to connect to the PPPoE.  Have the username and password in the IPCOP box, which works fine, but the Endian box will not establish a PPPoE connection at all.
    Not sure if I am overlooking something in the setup, as it seems straight forward.  Any ideas would be most helpful, as I am stumped.

Setting is as follows:
D-Link DSL-500T in bridging mode.
Ethernet cable from modem to red on Endian (no other choice here, ethernet or nothing.)
IP Range from ISP  x.x.x.100/30
PAP or CHAP
All the optional stuff blank.

Cut and paste from the log:

eth2 = red
eth1 = orange (not connected.)
eth0 = green

Apr 16 11:18:33 kernel: eth2 link up, 100Mbps, full-duplex, lpa 0x41E1
Apr 16 11:18:33 kernel: eth1 link down
Apr 16 11:18:33 kernel: eth0 link up, 100Mbps, full-duplex, lpa 0x45E1
Apr 16 11:18:44 kernel: eth2 no IPv6 routers present
Apr 16 11:18:48 pppd[7182] Plugin rp-pppoe.so loaded.
Apr 16 11:18:48 pppd[7182] RP-PPPoE plugin version 3.3 compiled against pppd 2.4.4
Apr 16 11:18:48 pppd[7182] pppd 2.4.4 started by root, uid 0
Apr 16 11:19:23 pppd[7182] Timeout waiting for PADO packets
Apr 16 11:19:23 pppd[7182] Unable to complete PPPoE Discovery
Apr 16 11:19:23 pppd[7182] Exit.
Apr 16 11:19:25 kernel: eth2 link up, 100Mbps, full-duplex, lpa 0x41E1
Apr 16 11:19:25 pppd[8095] Plugin rp-pppoe.so loaded.
Apr 16 11:19:25 pppd[8095] RP-PPPoE plugin version 3.3 compiled against pppd 2.4.4
Apr 16 11:19:25 pppd[8095] pppd 2.4.4 started by root, uid 0
Apr 16 11:20:01 pppd[8095] Timeout waiting for PADO packets
Apr 16 11:20:01 pppd[8095] Unable to complete PPPoE Discovery
Apr 16 11:20:01 pppd[8095] Exit.

I only have a production system, so I have to organise an outage to test.  Al the moment testing means disconnecting the production internet link, and connecting the Endian firewall to the D-Link Router.  I use the same cable from the D-Link to the firewall as is normally in the IPCOP firewall, so the only difference is the firewall hardware.  I have tried the following:

Used a reversing cable between the Router/Modem and the firewall.  Result:  Eth2 link down.
The test result above are when I use the cable that is currently on the production firewall.  Hope someone has a clue as to the issue.

Thanks,
Craig

[Steve]

If the only thing that is different is Endian and the system works properly with IPCop, I'd change the Red network card in Endian and see if that helps.

[craigray]

Thanks Steve.  Already tried that without success by reconfiguring the orange to be the red...   Exactly the same error.  The network port on my home system, but in that case I was using DHCP, not PPPoE connection on Red.

[Steve]

Timeout waiting for PADO packets means you can't 'hear' the PPP server (Access Concentrator).
Generally, this could be because of:

1. The connection between the Modem and Endian is not correct  - You have tried this
2. The Modem has no physical link to the Access Concentrator (You should see a link light on your Modem) - But IPCop works, so this is fine
3. The configured Service Name is not correct.  - Some ISPs require you to provide the service and/or Access Concentrator name - Not sure if you need this.
4. There is a physical problem with your Wan (RED) interface - Card, Cable or even Device Driver
5. The Access Concentrator was shut down.

I've had item 5 happen to me on various occasions.
The Access Concentrator will refuse to service your connection if there have been too many attempted connections in a short period of time.
Basically, the AC thinks it is under attack and switches to ignore mode (much like a firewall).

If you have a good ISP they should be able to see what is happening at their end while you try to connect.

I'd even try letting the Modem do the PPoE Dialing (Instead of Endian) and set Endian as the Modem's DMZ (Effectively sending all traffic to Endian)

Just a few suggestions ....

[craigray]

Thanks Steve.  Will try a few things, including completely differect hardware in case it is an issue with drivers.   Don't know about the option 5 on your list.  The ISP here does not seem to be doing this, as that would mean the IPCOP would not reconnect after I had been testing.  It always reconnects and establishes connection almost immediately.