uGAH man wrote:
Micha Feigin wrote:
> On Mon, 2003-09-29 at 05:54, devotion wrote:
>
>> Hi.
>> I asked help some time ago and got no reply... trying again (sorry if
>>that unappropriate).
>> I have very recently installed the Debian 3.0r1 Linux cd, using
>>default kernel that comes with it, the 2.2.20idepci.
>> I am using adsl, whose modem is connected to my only NIC, a Realtek
>>8139C (not C+, i see 8139C on the chip), and the realtek 8139C driver
>>(8139too.o) detected 2 network interfaces (eth0 and eth1), both on the
>>same IRQ (10).
>> When i boot, eth0 is brought up and eth1 stays down.
>> When i start pppoeconf, it searches for Access Concentrators on
>>"both" the nics, and finds it in the eth1 card.
>> pppoeconf saves my setup, and when i boot, eth0 is brought up, and
>>eth1 is also brought up. When ppp tries to use eth1, the box resets
>>(IRQ conflict?).
>> I therefore edited the ppp_on_boot script to bring eth0 down and
>>bring eth1 up, and now everything related to internet works fine in my
>>2.2 kernel.
>> Problem is, I want to install the 2.4 kernel to support all my other
>>hardware. I installed the same driver, but now it only detects 1
>>network interface card (which was expected at first). pppoeconf
>>detects the concentrator in eth0 (which was also expected) (it does
>>not detect it when i unplug the cable, so i assume its communicating
>>with the modem), but i am not getting any reply from my ISP's
>>authentication server (at 200.165.104.12) nor any DNS servers...
>> Does anyone what this is all about?
>> I have tried to:
>> - download the driver from the realtek site, compile it with the new
>>kernel, same result
>> - recompile the 2.2 kernel (debian package), but no 8139too.c
within it
>> - recompile the 2.4 8139too.c with the 2.2 kernel includes, does not
>>compile
>> None of these attempts succeded.
>> Any help is very appreciated, thanks.
>> -- Fred
>>
>
> Try running tcpdump on the iterface while you are starting ppp and see
> if you can see any requests the card is sending out and not getting
replies
> to. Whats the output of tcpdump if you run a dhco client in the
interface?
>Are you sure it's a driver issue?
> What does the output of this command look like?
> dmesg |grep -n -B 3 -A 3 eth
>
> Also, what about /etc/network/interfaces , /sbin/ifconfig and
> /sbin/route ?
OK, i tried running these commands, i got:
Kernel 2.4 (non working):
ike:/home/ugah# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:E0:7D:C8:12:93
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)
Kernel 2.2 (working):
ike:~ugah# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:E0:7D:C8:12:93
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xb800
eth1 Link encap:Ethernet HWaddr 00:E0:7D:C8:12:93
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2883 errors:0 dropped:0 overruns:0 frame:0
TX packets:1911 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:2835304 (2.7 MiB) TX bytes:191356 (186.8 KiB)
Interrupt:10 Base address:0xd000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)
ppp0 Link encap:Point-to-Point Protocol
inet addr:200.165.218.232 P-t-P:200.216.95.212
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:2881 errors:0 dropped:0 overruns:0 frame:0
TX packets:1909 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:3553263 (3.3 MiB) TX bytes:204722 (199.9 KiB)
When I run dmesg|grep -n -B 3 -A 3 eth , i get:
Kernel 2.2:
53-3c59x.c 18Feb01 Donald Becker and others
http://www.scyld.com/network/vortex.html
54-pcnet32.c: PCI bios is present, checking for devices...
55-rtl8139.c:v1.07 5/6/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html
56:eth0: RealTek RTL8139 Fast Ethernet at 0xb800, IRQ 10,
00:e0:7d:c8:12:93.
57-via-rhine.c:v1.08b-LK1.0.1 12/14/2000 Written by Donald Becker
58- http://www.scyld.com/network/via-rhine.html
66:eth1: 8139too Fast Ethernet driver 0.9.18-pre4 Jeff Garzik
<jgarzik@mandrakesoft.com>
67:eth1: Linux-2.2 bug reports to Jens David
<dg1kjd@afthd.tu-darmstadt.de>
68:eth1: RealTek RTL8139 Fast Ethernet board found at 0xd004d000, IRQ 10
69:eth1: Chip is 'RTL-8139C' - MAC address '00:e0:7d:c8:12:93'.
70-CSLIP: code copyright 1989 Regents of the University of California
71-PPP: version 2.3.7 (demand dialling)
72-PPP line discipline registered.
74-PPP BSD Compression module registered
75-PPP Deflate Compression module registered
76:eth1: Setting half-duplex based on auto-negotiated partner ability
0000.
77-registered device ppp0
78-probable hardware bug: clock timer configuration lost - probably a
VIA686a.
79-probable hardware bug: restoring chip configuration.
--
81-device ppp0 left promiscuous mode
82-device ppp0 entered promiscuous mode
83-device ppp0 left promiscuous mode
84:eth1: Promiscuous mode enabled.
85:device eth1 entered promiscuous mode
86:device eth1 left promiscuous mode
87:device eth0 entered promiscuous mode
88:device eth0 left promiscuous mode
89-device ppp0 entered promiscuous mode
90-device ppp0 left promiscuous mode
Kernel 2.4:
ike:/home/ugah# dmesg | grep -n -B 3 -A 3 eth
78-Adding Swap: 514100k swap-space (priority -1)
79-8139too Fast Ethernet driver 1.6.0 loaded
80-PCI: Found IRQ 10 for device 00:09.0#
81:eth0: use memory map. ioaddr=0xd086e000
82:eth0: Identified 8139CP chip type 'RTL-8139C'
83:eth0: RealTek RTL8139CP Fast Ethernet at 0xd086e000,
00:e0:7d:c8:12:93, IRQ 10
84-NTFS driver v1.1.22 [Flags: R/O MODULE]
85-CSLIP: code copyright 1989 Regents of the University of California
86-PPP generic driver version 2.4.2
--
93-PPP Deflate Compression module registered
94-usb.c: registered new driver usblp
95-printer.c: v0.11: USB Printer Device Class driver
96:eth0: Setting half-duplex based on auto-negotiated partner ability
0000.
The file /etc/network/interfaces: (a file, same on both kernels)
# The loopback interface
auto lo
iface lo inet loopback
# The first network card - this entry was created during the Debian
installation
# (network, broadcast and gateway are optional)
auto eth0
iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.2
And finally, the command pppoeconf installed on
/etc/ppp/peers/dsl-provider:
pty "/usr/sbin/pppoe -i eth0 -t 80 -m 1452"
When its configuring pppoeconf, i get:
ppp0: error fetching interface information: Device not found
Route is empty .. :(
ike:/home/ugah# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
localnet * 255.255.255.0 U 0 0
0 eth0
Does anybody know what this is?
-- Fred
Also, information on tcpdump and /proc/pci:
/proc/pci (kernel 2.2)
Bus 0, device 9, function 0:
Ethernet controller: Realtek 8139 (rev 16).
Medium devsel. Fast back-to-back capable. IRQ 10. Master
Capable. Latency=32. Min Gnt=32.Max Lat=64.
I/O at 0xb800 [0xb801].
Non-prefetchable 32 bit memory at 0xe3800000 [0xe3800000].
/proc/pci (kernel 2.4)
Bus 0, device 9, function 0:
Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 16).
IRQ 10.
Master Capable. Latency=32. Min Gnt=32.Max Lat=64.
I/O at 0xb800 [0xb8ff].
Non-prefetchable 32 bit memory at 0xe3800000 [0xe38000ff].
tcpdump on eth0 on kernel 2.4:
ike:/home/ugah# tcpdump -i eth0
tcpdump: listening on eth0
23:15:47.642860 PPPoE PADI
23:15:47.683561 PPPoE PADO [Service-Name] [AC-Name "ARC-RJ-VELOX-03"]
[AC-Cookie UTF8]
23:15:47.683772 PPPoE PADR [Service-Name] [AC-Cookie UTF8]
23:15:47.717543 PPPoE PADS [ses 0xc7f] [Service-Name] [AC-Cookie UTF8]
23:15:47.718496 PPPoE PADT [ses 0xc7f] [Generic-Error "RP-PPPoE: System
call error"] [AC-Cookie UTF8]
23:15:47.721465 PPPoE [ses 0xc7f] LCP 20: Conf-Req(1), MRU=1492,
Auth-Prot PAP, Magic-Num=b3663d07
23:16:17.722103 PPPoE PADI
23:16:17.756798 PPPoE PADO [Service-Name] [AC-Name "ARC-RJ-VELOX-03"]
[AC-Cookie UTF8]
23:16:17.757031 PPPoE PADR [Service-Name] [AC-Cookie UTF8]
23:16:17.788579 PPPoE PADS [ses 0xc99] [Service-Name] [AC-Cookie UTF8]
23:16:17.789487 PPPoE PADT [ses 0xc99] [Generic-Error "RP-PPPoE: System
call error"] [AC-Cookie UTF8]
23:16:17.792762 PPPoE [ses 0xc99] LCP 20: Conf-Req(1), MRU=1492,
Auth-Prot PAP, Magic-Num=b366b2c6
23:16:47.752036 PPPoE PADI
23:16:47.791857 PPPoE PADO [Service-Name] [AC-Name "ARC-RJ-VELOX-03"]
[AC-Cookie UTF8]
23:16:47.792087 PPPoE PADR [Service-Name] [AC-Cookie UTF8]
23:16:47.828056 PPPoE PADS [ses 0xcbb] [Service-Name] [AC-Cookie UTF8]
23:16:47.828941 PPPoE PADT [ses 0xcbb] [Generic-Error "RP-PPPoE: System
call error"] [AC-Cookie UTF8]
23:16:47.831990 PPPoE [ses 0xcbb] LCP 20: Conf-Req(1), MRU=1492,
Auth-Prot PAP, Magic-Num=b3672870
23:17:17.779422 PPPoE PADI
23:17:17.815333 PPPoE PADO [Service-Name] [AC-Name "ARC-RJ-VELOX-03"]
[AC-Cookie UTF8]
23:17:17.815565 PPPoE PADR [Service-Name] [AC-Cookie UTF8]
23:17:17.851306 PPPoE PADS [ses 0xcd0] [Service-Name] [AC-Cookie UTF8]
23:17:17.852285 PPPoE PADT [ses 0xcd0] [Generic-Error "RP-PPPoE: System
call error"] [AC-Cookie UTF8]
Now, tcpdump on eth1 (after this, i can connect to internet sites):
ike:/home/ugah# tcpdump -i eth1
tcpdump: WARNING: eth1: no IPv4 address assigned
tcpdump: listening on eth1
23:20:33.329695 PPPoE PADI
23:20:33.362696 PPPoE PADO [Service-Name] [AC-Name "ARC-RJ-VELOX-03"]
[AC-Cookie UTF8]
23:20:33.362815 PPPoE PADR [Service-Name] [AC-Cookie UTF8]
23:20:33.398642 PPPoE PADS [ses 0xd5f] [Service-Name] [AC-Cookie UTF8]
23:20:33.402574 PPPoE [ses 0xd5f] LCP 20: Conf-Req(1), MRU=1492,
Auth-Prot PAP, Magic-Num=b36a9978
23:20:33.403208 PPPoE [ses 0xd5f] LCP 22: Conf-Req(1), ACCM=00000000,
Magic-Num=f6acfba4, PFC, ACFC
23:20:33.403322 PPPoE [ses 0xd5f] LCP 20: Conf-Ack(1), MRU=1492,
Auth-Prot PAP, Magic-Num=b36a9978
23:20:33.438561 PPPoE [ses 0xd5f] LCP 22: Conf-Ack(1), ACCM=00000000,
Magic-Num=f6acfba4, PFC, ACFC
23:20:33.439325 PPPoE [ses 0xd5f] LCP 10: Echo-Req(0), Magic-Num=f6acfba4
23:20:33.439424 PPPoE [ses 0xd5f] PAP 28: Auth-Req(1), Peer=2125697246,
Name=2125697246
23:20:33.470611 PPPoE [ses 0xd5f] LCP 10: Echo-Rep(0), Magic-Num=b36a9978
23:20:33.498733 PPPoE [ses 0xd5f] PAP 7: Auth-Ack(1), Msg=
23:20:33.498798 PPPoE [ses 0xd5f] IPCP 12: Conf-Req(1),
IP-Addr=200.216.95.212
23:20:33.500090 PPPoE [ses 0xd5f] IPCP 30: Conf-Req(1),
IP-Addr=0.0.0.0, IP-Comp VJ-Comp, Pri-DNS=0.0.0.0, Sec-DNS=0.0.0.0
23:20:33.500103 PPPoE [ses 0xd5f] CCP 17: Conf-Req(1), Deflate, MVRCA,
BSD-Comp
23:20:33.500112 PPPoE [ses 0xd5f] IPCP 12: Conf-Ack(1),
IP-Addr=200.216.95.212
23:20:33.538579 PPPoE [ses 0xd5f] IPCP 12: Conf-Rej(1), IP-Comp VJ-Comp
23:20:33.538935 PPPoE [ses 0xd5f] IPCP 24: Conf-Req(2),
IP-Addr=0.0.0.0, Pri-DNS=0.0.0.0, Sec-DNS=0.0.0.0
23:20:33.550652 PPPoE [ses 0xd5f] LCP 23: Prot-Rej(2),
Rejected-Protocol=80fd
23:20:33.574552 PPPoE [ses 0xd5f] IPCP 24: Conf-Nak(2),
IP-Addr=200.165.206.11, Pri-DNS=200.149.55.140, Sec-DNS=200.202.193.71
23:20:33.575452 PPPoE [ses 0xd5f] IPCP 24: Conf-Req(3),
IP-Addr=200.165.206.11, Pri-DNS=200.149.55.140, Sec-DNS=200.202.193.71
23:20:33.606605 PPPoE [ses 0xd5f] IPCP 24: Conf-Ack(3),
IP-Addr=200.165.206.11, Pri-DNS=200.149.55.140, Sec-DNS=200.202.193.71
23:20:34.490587 PPPoE [ses 0xd5f] LCP 14: Echo-Req(1), Magic-Num=b36a9978
23:20:34.490918 PPPoE [ses 0xd5f] LCP 14: Echo-Rep(1), Magic-Num=f6acfba4
23:17:17.855231 PPPoE [ses 0xcd0] LCP 20: Conf-Req(1), MRU=1492,
Auth-Prot PAP, Magic-Num=b3679df8
Hope this helps understanding my problem :(
Thanks
-- Fred