Linux & PPPoE again?

K

kay

New Member
Joined
Jul 1, 2004
Messages
4
Reaction score
0
Location
.
Hello,

I remember a while ago there was a discussion about this problem, however nobody seemed to know anything about it. I've spoken to Sentech's technical support about it and they seem lost too - one guy suggested that I check my password and the firewall rules [}:)]

This is what happens:

# pppd call mywireless nodetach maxfail 3
using channel 4217
Using interface ppp1
Connect: ppp1 <--> /dev/pts/1
PADS: System-Error: Call disconnected (3)
Modem hangup
Connection terminated.
using channel 4218
Using interface ppp1
Connect: ppp1 <--> /dev/pts/1
Script pppoe -I eth1 finished (pid 1363), status = 0x1
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xa9c5381b> <pcomp> <accomp>]
PADS: System-Error: Call disconnected (3)
Modem hangup
Connection terminated.
using channel 4219
Using interface ppp1
Connect: ppp1 <--> /dev/pts/1
Script pppoe -I eth1 finished (pid 1375), status = 0x1
sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x77d3f954> <pcomp> <accomp>]
PADS: System-Error: Call disconnected (3)
Modem hangup
Connection terminated.
Waiting for 1 child processes...
script pppoe -I eth1, pid 1391
Script pppoe -I eth1 finished (pid 1391), status = 0x1

Sometimes it works (we've done nothing, just tried a little later) but most of the time this is what I get. Tried restarting the IPW modem, playing with pppoe and pppd options... alas, no luck. I'm running PPPoE over a dedicated network card (no firewalling or anything like that) to the Sentech modem equipped with an ethernet adapter.

Any suggestions welcome.
 
Kay - I saw this exact behaviour for 4 days... I went through the following:

The modem was running firmware revision 4.2.1.8

1) Replaced ethernet cable
* This did not fix it but made the modem reliably detect it's in pppoe mode.
2) Downgraded back to 4.2.1.2 firmware
* Still fscked
3) Upgraded to v5 ...
* could connect but now had issues mentioned with the v5 upgrade
4) Moved back to 4.2.1.8
* fixed

Sadly, I'm not sure which of all these fixed it ... got too **** tired to write notes etc etc. Who knows.... I KNOW that the firmware change did not cause this to start with ... it just happened....

R
 
Thanks a lot! I'll try different firmware versions. We've already tried two different ethernet cables, doesn't seem to make any difference. Also I can always see the modem on the network (i.e. the Access Concentrator), without fail. Oh, fun and games :)
 
Upgraded the firmware. Ohhhh....

# pppd call mywireless nodetach
using channel 179
Using interface ppp1
Connect: ppp1 <--> /dev/pts/1
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xbfc157c8> <pcomp> <accomp>]
rcvd [LCP ConfReq id=0x1 <auth chap MD5> <magic 0x83311449>]
sent [LCP ConfAck id=0x1 <auth chap MD5> <magic 0x83311449>]
rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0xbfc157c8> <pcomp> <accomp>]
rcvd [CHAP Challenge id=0x1 <77a387b4a2c0fb10957ad972225ce680>, name = "STPLR01"]
sent [CHAP Response id=0x1 <bd9856b52596b825ff82869d676b224b>, name = "wms"]
rcvd [CHAP Success id=0x1 ""]
sent [IPCP ConfReq id=0x1 <addr 192.168.11.1> <compress VJ 0f 01> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15>]
rcvd [LCP ProtRej id=0x2 80 21 01 01 00 1c 03 06 c0 a8 0b 01 02 06 00 2d 0f 01 81 06 00 00 00 00 83 06 00 00 00 00]
rcvd [IPCP ConfReq id=0x1 <addr 10.11.253.1>]
rcvd [LCP ProtRej id=0x3 80 fd 01 01 00 0c 1a 04 78 00 18 04 78 00]
rcvd [LCP EchoReq id=0x1 magic=0x83311449 78 00 18 04]
sent [LCP EchoRep id=0x1 magic=0xbfc157c8 00 2d 0f 01]
...

The IP layer doesn't even come up. Notice how the remote side tries to assign me a 10.11.253.1 address? Weird. Apparently that's only supposed to happen when registering.
 
After the flashing the modem no longer has your username and password details.

At this point I suggest you plug the usb cable in and dial up via the Mywireless dialler.

After that has worked.... unplug usb ... plug in ethernet... turn modem off and back on ... she should be humming ;-)

R
 
Hi

I had a similar issue this weekend.
Went back to JHB with the modem antenna etc since there's no reception in Centurion yet and had to go through the registration pages again before the modem would connect... strange.
 
I am ready to pull my hair out... I did not check the firmware on the IPW box, but was told that it was upgraded to the newest one. I'll do all the checks tomorrow.
I am using Debian 3.0 (stable, R2) which uses debian version of pppoe. In a fact this is debianised rp-pppoe 3.3. The pppoe session starts, computer finds the access point and after few session packets are exchanged the access point sends PADT (active discovery terminate) and.... thats end of it :((.
I upgraded the system to Debian testing distribution, kernel 2.4.26 and rp-pppoe 3.5 (debianised) and... same story.
I did the full installation of the IPW over USB using Win XP (funny enough, with 98 and Explorer 5.0 it did not want to access the registration page) and run the whole registration process.
Does anyone have some positive experience with pppoe... or I have to go USB route? I would prefer pppoe... less hassles :))
 
jersey

I run mine through a linux firewall (www.smoothwall.org) via PPPoE without hassles.

Sentech suggested when I phoned about using PPPoE with Linux that I should use Roaring penguin client freely downloadable. After some digging in the firewall software I discovered that it was indeed the same client built into it.

I did have some issues in the beginning but found that I needed to reset the modem when swopping from the USB cable (on win2k) to the Ethenet cable (on linux) otherwise it doesn't detect the cable properly and has problems dialing.

1.5 cents worth
 
There is something funny about the PPPoE on Linux -I've seen it work fine on some boxes for a few days and then Zip...

Would be nice if Rodent can have a look at it.

-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<
What you really need to know is how the mind works, for as the mind goes, so goes the life.
Vernon Howard
 
Brolloks,

Thnx... I am downloading iso image of the smoothwalll as I wright tis posting. I will try it tomorrow. I will compare the pppoe settings with the debian one... of course if it works. Debian uses roaring penguin. It might be just slightly differently configured.

If it does not... well, my conspiracy theory is... some of the towers are not configured properly. Thing which worries me is that I can connect. It is the tower sending me PADT before I have a chance to identify myself :((. I do not have same problem which "kay" had. PADS in my case is exchanged properly. In which area are you, so I can take the notebook and test? :)).

Will keep you guys posted.
 
Guys,

Bear in mind that all the pppoe interaction is simply between you and the modem.

Modem-->tower remains unchhanged.

Make sure you lcp_timeout is set high and your lcp_keepalive is set low...
 
TheRoDent :)),
***************
I will... if pppoe upsets me enough... today I am trying the final installation :))....

regardtv :)),
***************
Do you try to say that if I am getting PADT, it is coming from the modem and not from the tower? This would change the picture.

Best regards guys... and wish me luck :))
 
My goodness how dumb one can be???

I enabled low level debugging and... the whole thing wants to authenticate using CHAP and not PAP :(((.
I am connecting and getting IP addresses assigned. I can ping the address assigned to myself but not the remote IP... at least I connect :))... I am using MTU 1492 and I clamped MSS to 1412... this way it seems to connect allmost every time. I have to check that pinging story... I am not running any firewall as yet, just a vanilla system... ufff... thnx everybody for the input :)))

regardtv - the communication happens between the peers and enduser machine. Modem has nothing to do with that :))... it is simply the means of connectivity :))
 
Nope, jersey. I'd have to disagree there. PPPoE ... Point-to-Point protocol over ethernet ... The session initation etc is between YOU (your PC) and your modem. Once you've sucesssfully esablished the pppoe session the modem can then pass authentication and other data to the tower to let you communicate.

A good review and explanation is available on the roaring penguin web site.

R
 
As an aside...

Jul 22 22:08:31 gateway pppd[4526]: pppd 2.4.2 started by root, uid 0
Jul 22 22:08:31 gateway pppd[4526]: Using interface ppp0
Jul 22 22:08:31 gateway pppd[4526]: Connect: ppp0 <--> /dev/pts/201
Jul 22 22:08:32 gateway pppoe[4527]: PPP session is 100
Jul 22 22:08:33 gateway pppd[4526]: CHAP authentication succeeded
Jul 22 22:08:34 gateway pppd[4526]: local IP address 66.18.80.29
Jul 22 22:08:34 gateway pppd[4526]: remote IP address 66.18.87.50
Jul 22 22:08:34 gateway pppd[4526]: primary DNS address 66.18.68.1
Jul 22 22:08:34 gateway pppd[4526]: secondary DNS address 66.18.65.1

Chap works just fine

Have you checked that you've set this connection as the default route after connection ?

What I meant with my earlier post is that the pppoe session initiation is between you and the modem. The user/network authentication obviously goes back to the radius server on the network.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X