LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 05-07-2005, 05:55 PM   #1
ohmster
Member
 
Registered: May 2005
Location: South Florida
Distribution: CentOS 7
Posts: 39

Rep: Reputation: 2
cannot adsl-start on FC3, works on redhat 9


I am changing from redhat 9 to FC3 on my linux box. I have decided to use
a new hard drive for fc3 so that I can just plug in the new drive until I
get things worked out, then I can always plug the old one back if I need
to get online for now.

My redhat 9 box always connects right away with adsl-start but the new
fc3 box will not connect, it always times out. I configured both distros
the same for rp-pppoe-3.5-1, using that version because it was the only
one that worked with redhat 9. Would like to use the new rp-pppoe package
that comes with fc3 but right now, I cannot get online to save my life. I
have both installs available to try and find out what is wrong with the
fc3 adsl-start problem. I did a debug on adsl-start to get more
information and this seems to indicate that something is not configured
correctly with eth0. Remember, I can plug in the old drive and connect
right away, plug in the new fc3 drive and it will not connect so this
rules out any hardware issues. This is the bottom of the debug file:

---------------------------------------------
Sat May 7 16:02:28 EDT 2005
---------------------------------------------
* The following section is a dump of the packets
* sent and received by rp-pppoe. If you don't see
* any output, it's an Ethernet driver problem. If you only
* see three PADI packets and nothing else, check your cables
* and modem. Make sure the modem lights flash when you try
* to connect. Check that your Ethernet card is in
* half-duplex, 10Mb/s mode. If all else fails,
* try using pppoe-sniff.
rp-pppoe debugging dump
rp-pppoe-3.5
16:01:53.549 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr 00:e0:7d:9a:0d:0c DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 bd 13 00 00 ............

16:01:58.548 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr 00:e0:7d:9a:0d:0c DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 bd 13 00 00 ............

16:02:08.546 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr 00:e0:7d:9a:0d:0c DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 bd 13 00 00 ............
---------------------------------------------

This information tells me that something is wrong with the eth0
interface, but what, what could possibly be wrong with it in that it will
not connect and always time out? Look at this part of the debug info:

If you only
* see three PADI packets and nothing else, check your cables
* and modem. Make sure the modem lights flash when you try
* to connect. Check that your Ethernet card is in
* half-duplex, 10Mb/s mode. If all else fails,
* try using pppoe-sniff.

That is what I have, only three PADI packets. Check cable and modem, this
cannot be, I can plug in the redhat 9 drive and it works right away. My
Westell modem ethernet light only barely flickers when the system is
really working so this does not help. Check that the card is configed
right? What could be wrong with it? Here is the output of ifconfig for
both systems:

---------------------------------------------------------------------
ifconfig working rehat 9 machine:
---------------------------------------------------------------------
eth0 Link encap:Ethernet HWaddr 00:50:04:26:A4:62
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:58884 errors:0 dropped:0 overruns:0 frame:0
TX packets:52422 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:44296587 (42.2 Mb) TX bytes:7001359 (6.6 Mb)
Interrupt:9 Base address:0xd000

eth1 Link encap:Ethernet HWaddr 00:E0:7D:9A:0D:0C
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:51273 errors:0 dropped:0 overruns:0 frame:0
TX packets:57837 errors:0 dropped:0 overruns:0 carrier:0
collisions:5 txqueuelen:100
RX bytes:5802070 (5.5 Mb) TX bytes:43824176 (41.7 Mb)
Interrupt:9 Base address:0x6000

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:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8680 (8.4 Kb) TX bytes:8680 (8.4 Kb)

ppp0 Link encap:Point-to-Point Protocol
inet addr:65.12.220.9 P-t-P:65.14.252.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:58433 errors:0 dropped:0 overruns:0 frame:0
TX packets:51969 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:42985355 (40.9 Mb) TX bytes:5830743 (5.5 Mb)
---------------------------------------------------------------------
ifconfig non-working fc3 machine:
---------------------------------------------------------------------
eth0 Link encap:Ethernet HWaddr 00:E0:7D:9A:0D:0C
inet6 addr: fe80::2e0:7dff:fe9a:d0c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1392 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:86418 (84.3 KiB) TX bytes:558 (558.0 b)
Interrupt:9 Base address:0xb800

eth1 Link encap:Ethernet HWaddr 00:50:04:26:A4:62
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::250:4ff:fe26:a462/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:4555 (4.4 KiB)
Interrupt:9 Base address:0xd000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:260 errors:0 dropped:0 overruns:0 frame:0
TX packets:260 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:21498 (20.9 KiB) TX bytes:21498 (20.9 KiB)
---------------------------------------------------------------------

I am sure that this must be what is going on, I have no "inet6 addr"
stuff in the working configs. What is this "inet6 addr" stuff in fc3 and
could it be what is making the adsl-start command time out?

Does anything look wrong with the bottom eth0 config? This cannot be
modem and cables as they are not touched at all and exactly the same for
both redhat 9 and fc3.

Somebody please help me to debug the FC3 adsl-start problem. I really
need this to work so that I can permanently take the EOL redhat 9 system
down for good. What else can I do, what is diffent about fc3 that makes
the adsl-start command not work? Are there any files on the working
system that I can use for the non-working system that I can examine or
copy over to get the internet up and running?
 
Old 05-08-2005, 01:32 AM   #2
camelrider
Member
 
Registered: Apr 2003
Location: Juneau, Alaska
Posts: 251

Rep: Reputation: 32
Have you "ifconfig eth0 down" before adsl-start?
When I used my Linux box as the router here I had to change my boot sequence to not bring up eth0. It seems PPPoE prefers to do that itself. Ifdown eth0, (check ifconfig eth0 to make sure) then try adsl-start.

If that doesn't work you may find a clue in a comparison of the files in /etc/sysconfig/network-scripts between the two distros.

Just a couple of thoughts.
 
Old 05-08-2005, 09:31 AM   #3
ohmster
Member
 
Registered: May 2005
Location: South Florida
Distribution: CentOS 7
Posts: 39

Original Poster
Rep: Reputation: 2
Yeah, tried that. Makes no difference. They tell you not to bring up the ethx card to the modem at boot, make sure the kernel can see the card, ifconfig ethx, Then start adsl. Once adsl starts, it brings up the eth0 card and the ppp0 interface. My eth1 card to my hub comes up fine and adsl will start eth0 but then I get a time out when the adsl script sends padi packets to the modem. It sends three of them, gets no answer, and gives up.

I probably need some way to watch what is going on during this adsl chat, would be neat to log it with redhat 9 and then do the same log with fc3 to see what is going on. Need some way to test that eth0 actually works all the way to the modem. This is not a hardware issue, dropping the redhat 9 drive into the unit connects immediately.

Quite a bit of files in network-scripts. Was thinking of tarring up the old network-scripts and networking directories and dropping them into the new distro, replacing what is there. This is a bad idea I think though, then I would be changing the distro. There is more to this than meets the eye.

I have two network cards in this machine, one to hub and LAN, one to dsl modem. Never saw either of them communicate with fc3, although they seem to come up just fine. Did not try to setup samba on the fc3 machine though until I can get online.
 
Old 05-08-2005, 10:33 AM   #4
ohmster
Member
 
Registered: May 2005
Location: South Florida
Distribution: CentOS 7
Posts: 39

Original Poster
Rep: Reputation: 2
Problem Solved!

There was nothing wrong with the distro at all and it really worked just fine. The problem was that the new distro configured my ethx devices opposite. See here:

---------------------------------------------------------------------
ifconfig working rehat 9 machine:
---------------------------------------------------------------------
eth0 Link encap:Ethernet HWaddr 00:50:04:26:A4:62
---------------------------------------------------------------------
ifconfig non-working fc3 machine:
---------------------------------------------------------------------
eth1 Link encap:Ethernet HWaddr 00:50:04:26:A4:62

The cards were reversed! Switching the cables around solved that problem. FC3 works just fine with pppoe. Sometimes it pays to actually pay attention to all of the data that one is collecting. The usenet newsgroup, comp.os.linux.networking, spotted this problem with the ifconfig output that I posted and brought it to my attention.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
adsl-setup or adsl-start not found as user! bnchakraborty Linux - Newbie 2 01-18-2008 10:23 PM
Monitoring ADSL (to keep online), adsl-start michaelsanford Linux - Networking 7 07-12-2006 06:43 PM
lan connection works but adsl doesn't, why? trendsetter Linux - Networking 25 11-04-2005 12:31 PM
Setup ADSL so that it works!! alan_t Linux - Networking 7 04-10-2005 08:34 AM
Everything works fine... but no ADSL!! Conexus Slackware 10 04-11-2004 06:29 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 01:05 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration