ppp server problem with Redhat 7.2 Kernel 2.4.7-10

ppp server problem with Redhat 7.2 Kernel 2.4.7-10

Post by Kamb » Thu, 22 Aug 2002 04:55:55



Hi
Please help me as soon as possible.My network in down for this reason!:(
I installed Linux Redhat 7.2(Kernel 2.4.7) and portslave under it for PPP
connection and so on.
I have configured portslave with out any problems.When I dialed to my Linux PPP
server, I authenticated successfully, even my remote radius server reported
that authenticating and accounting was successful.The problem start here:
Linux send a error message that PPP module not loaded or didn't compile with
Kernel try using modprobe -v ppp and ... ,finally disconnecting user.
I have ran /usr/local/sbin/pppd-radius by hand and got same error, then the
problem is here.But...
I have compiled PPP as module and configured my /etc/module.conf:
alias ppp ppp_async
alias /dev/ppp and ....
even I have compiled PPP in to the kernel.
Any way my problems is:
1.I have not ppp.o file(I think my problem is it)!
2.When I ran "depmod -a" then "lsmod" I can see that ppp_async.o and slhc.o
  is loaded, but pppd-radius could not be execute!
I have not compatibility problem: ppp-2.4.1.tar.gz which compatible with my kernel.
I have compiled kernel successfully and update my lilo and so on.It's mean I
have not compile problem.
Why ppp.o doesn't exist!
How can I solve this problem?Please

regards - K.N
MCSE
CHE
CCNA

 
 
 

1. Davicom 9102 AF, Redhat 7.2, Dell 8200, kernel 2.4.7-10

Hi,

I have a Dell 8200 with Redhat 7.2 and a 2.4.7-10 kernel.

When I installed Linux, it thought that I had some kind of DEC network
card (at least that is what is said in "neat"). It used the tulip
driver which caused lots of RX and TX errors which made things very,
very slow. Here are the appropriate messages in /var/log/messages:

Jan 21 15:45:29 localhost kernel: tulip0:  EEPROM default media type Autosense.
Jan 21 15:45:29 localhost kernel: tulip0:  Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
Jan 21 15:45:29 localhost kernel: tulip0:  Index #1 - Media 10baseT(#0) described by a 21140 non-MII (0) block.
Jan 21 15:45:29 localhost kernel: tulip0:  Index #2 - Media 100baseTx(#3) described by a 21140 non-MII (0) block.
Jan 21 15:45:29 localhost kernel: tulip0:  Index #3 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block.
Jan 21 15:45:29 localhost kernel: tulip0:  Index #4 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
Jan 21 15:45:29 localhost kernel: tulip0:  MII transceiver #1 config 3100 status 7809 advertising 01e1.
Jan 21 15:45:29 localhost kernel: eth0: Davicom DM9102/DM9102A rev 49 at 0xd0968c00, 00:80:AD:C0:79:4D, IRQ 11

I'm certainly no expert, but it is interesting that the message even
says that the Davicom NIC was detected, but "neat" still reports some
DEC card and the tulip driver is used.

The fix was to make the system use the default dmfe driver instead of
the tulip driver. I edited /etc/modules.conf and changed:

    alias eth0 tulip

to this:

    alias eth0 dmfe

Then I did this:

    ifdown eth0
    rmmod tulip
    insmod dmfe
    ifup eth0

This solved my problem. The message in /var/log/messages at boot is
now:

    Davicom DM9xxx net driver, version 1.36p1 (May 12, 2001)

I don't know why the dmfe driver wasn't used in the first place.

I also don't know who to tell to get this fixed or where to tell them.
If you know, can you tell me, and/or forward this email to them?

Thanks,

Jeff

2. Spelling fixes for 2.5.63 - ugliness

3. TC ingress policer not working -- RedHat 7.2, Kernel 2.4.7-10

4. Does anybody knows how to configure SRM (

5. Unable to Record Sound: RedHat 7.2 Kernel 2.4.7-10

6. Linux kills my CD drive

7. Problem accessing my ISP with RH 7.2 (kernel 2.4.7-10, LTModem driver 8.26a9)

8. dual boot w/NT?

9. Kernel upgrade from RH 7.2(2.4.7-10) to 2.4.18

10. Looking for driver for RHL 7.2 kernel 2.4.7-10

11. RHLinux 7.2 2.4.9-10 kernel lost tape device

12. Kernel Issue - Anything after RH 7.2 (2.4.7-10) - Help!!!

13. Weird filesystem problems with RedHat 2.4.7-10 and 2.4.16