FC3 connect with adsl-start does not work, please HELP!

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
eth0 on both systems:

The working redhat 9 ifconfig eth0:
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

The non-working fc3 ifconfig eth0:
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

What is this "inet6 addr" stuff in the fc3 eth0 config that is not
present in the redhat 9 ifconfig eth0? I don't want to use ipv6 or
anything like that, could this be what is stopping it from working and if
so, how can I take this 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?

--
~Ohmster
ohmster at newsguy dot com

Ohmster <(E-Mail Removed)> wrote in
news:Xns964FBA2FA748MyBigKitty@216.77.188.18:

> What is this "inet6 addr" stuff in the fc3 eth0 config that is not
> present in the redhat 9 ifconfig eth0? I don't want to use ipv6 or
> anything like that, could this be what is stopping it from working and
> if so, how can I take this out?

Also have that inet6 stuff in my lo config. See total ifconfig outputs
for both machines. What is this inet6 stuff? This must be what is messing
me up. Arrrgh!

---------------------------------------------------------------------
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?

--
~Ohmster
ohmster at newsguy dot com

Ohmster wrote:

> The working redhat 9 ifconfig eth0:
> 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
>
> The non-working fc3 ifconfig eth0:
> 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
>
> What is this "inet6 addr" stuff in the fc3 eth0 config that is not
> present in the redhat 9 ifconfig eth0? I don't want to use ipv6 or
> anything like that, could this be what is stopping it from working and if
> so, how can I take this out?

IPv6 is the (fairly) new internet address scheme.
It may well be the cause of your problem.
I think you can turn it off by adding the line
IPV6INIT=no
to /etc/sysconfig/network-scripts/ifcfg-eth0
and running "service network restart"
(both as superuser).




--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

Timothy Murphy <(E-Mail Removed)> wrote in news:1Obfe.52849
$(E-Mail Removed):

> IPv6 is the (fairly) new internet address scheme.
> It may well be the cause of your problem.
> I think you can turn it off by adding the line
> IPV6INIT=no
> to /etc/sysconfig/network-scripts/ifcfg-eth0
> and running "service network restart"
> (both as superuser).

Man I really thought that you were onto something, Tim. I looked and
already had that line there. No dice. I still have that inet6 stuff all
over my ifconfigs. I had to revert to the working distro to get back
online again.

I did notice that there is also an
/etc/sysconfig/networking/profiles/default directory and it also has a
ifcfg-eth0 file in there. Did not get a chance to try it out as the wife
rushed me back online again. This sucks, now with her here, I might get
like 3 minutes to try again, maybe in a few hours or so...

Somehow we have to figure out how to turn off ipv6 in fc3 to make this
work. I think that you might be right and that might be what is messing
me up. I remember when I had ipv6 in windows that it really messed me up
and I had to take it out.

--
~Ohmster
ohmster at newsguy dot com

Ohmster <(E-Mail Removed)> wrote in
news:Xns964FC5AAFB01AMyBigKitty@216.77.188.18:

> Somehow we have to figure out how to turn off ipv6 in fc3 to make this
> work. I think that you might be right and that might be what is messing
> me up. I remember when I had ipv6 in windows that it really messed me up
> and I had to take it out.
>

....sigh. Got rid of ipv6 by putting

alias net-pf-10 off

into /etc/modprobe.conf and rebooting. It is really gone now but fc3 still
won't connect, still times out, still only sends 3 PADI packets and nothing
comes back from etho. I am getting really mad about this, wish I did not
have pppoe. Now I am stuck with a redhat 9 system that the script kiddies
have already partied down with, they go in through apache, and I cannot get
a new distro installed that will connect with pppoe.

--
~Ohmster
ohmster at newsguy dot com

Ohmster wrote:

> ...sigh. Got rid of ipv6 by putting
>
> alias net-pf-10 off
>
> into /etc/modprobe.conf and rebooting. It is really gone now but fc3 still
> won't connect, still times out, still only sends 3 PADI packets and
> nothing comes back from etho. I am getting really mad about this, wish I
> did not have pppoe. Now I am stuck with a redhat 9 system that the script
> kiddies have already partied down with, they go in through apache, and I
> cannot get a new distro installed that will connect with pppoe.

Did you try running adsl-setup?
Do you have the same /etc/ppp/chap-secrets and pap-secrets
as you did with the redhat-9 distribution?

What does "ifconfig ppp0" say with the two distributions?
Can you ping the two P-t-P addresses the old distribution gives
with the new distribution?

It might be worth turning off iptables temporarily on the new distribution
"service iptables stop".

It sounnds to me as though your new distribution is working,
except for some small point in the setup.

I'm not sure your alias command is correct.
Do you get a standard IP address where before you got an IPv6 address?
If I couldn't get rid of v6 addresses I would either
(a) remove the ipv6 modules in /lib/modules/<version>/kernel/net
or (b) run "lsmod", find the v6 module, and remove it with "rmmod ipv6",
or whatever.




--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

> 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 ............


Have you tried compiling the tar version of rp-pppoe from roaring
penguin site? Just a thought though.


--
Raqueeb Hassan
Bangladesh

"Raqueeb Hassan" <(E-Mail Removed)> wrote in
news:(E-Mail Removed) ups.com:

> Have you tried compiling the tar version of rp-pppoe from roaring
> penguin site? Just a thought though.

Yes, no luck at all. That is where I got the debug info.

--
~Ohmster
ohmster at newsguy dot com

Timothy Murphy <(E-Mail Removed)> wrote in
news:jrmfe.52857$(E-Mail Removed):

> Did you try running adsl-setup?
> Do you have the same /etc/ppp/chap-secrets and pap-secrets
> as you did with the redhat-9 distribution?

Yes of course. The secrets files are the same.

> What does "ifconfig ppp0" say with the two distributions?
> Can you ping the two P-t-P addresses the old distribution gives
> with the new distribution?

ppp0 never comes up with the new distribution so I cannot ifconfig it,
comes up fine in redhat 9, connects within seconds, almost immediately.

> It might be worth turning off iptables temporarily on the new
> distribution "service iptables stop".

Not sure how that would help. I installed without a firewall so that I
could add one later and so it would not mess up the connection. I choose
adsl-setup with no firewall and with masquerade, makes no differnce, it
sends padi packets to the modem and nobody answers. I think that perhaps
eth0 "just isn't right" or something in fc3, that is the connection to
the modem. Remeber, the very same hardware works just fine if I plug in
the redhat 9 drive.

> It sounnds to me as though your new distribution is working,
> except for some small point in the setup.

Yeah well, that is a pretty big point alright. No network connectivity,
no distribution. Pointless to have a server that cannot connect.

> I'm not sure your alias command is correct.
> Do you get a standard IP address where before you got an IPv6 address?
> If I couldn't get rid of v6 addresses I would either
> (a) remove the ipv6 modules in /lib/modules/<version>/kernel/net
> or (b) run "lsmod", find the v6 module, and remove it with "rmmod
> ipv6", or whatever.

No, I get some kind of inet6 addr, but it is no kind of IP that I ever
heard of, gettting that right away. I managed to turn off ipv6 in my
modeprobe.config file and don't get the inet6 addr anymore, but it makes
no difference, the adsl-start does not work, times out. Kocking on the
modem but nobody's home, or so it seems. The rp-pppoe-3.5-1 package was
the only one that worked previously in redhat 9, now it does not work in
fc3, altough it gives a row of pretty dots while it tries. I reinstalled
the distro again and tried with it's default package, no good at all. The
new one shows nothing other than it eventually times out. For the record,
sel-linux is turned off.

>
> --
> Timothy Murphy

This is really disappointing, Tim, not sure what to do about this. Either
chuck fc3 in favor of a different distro or make the modem/router be a
router once again and then try to figure out ip forwarding for it. The
modem defaults to connecting on it's own and will route and hand out NAT
addresses if I reset it. I like using it as a bridged modem and letting
linux do the connectiong and being the gateway.

This really bites, I am totally out of ideas here. Thanks for pitching
in, Tim.

--
~Ohmster
ohmster at newsguy dot com

Ohmster wrote:
> ---------------------------------------------------------------------
> 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
> ---------------------------------------------------------------------
> 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

If you check the MAC addresses for eth0 and eth1 you'll see they are
swapped. Either swap the cables from the NICs, or run pppoe on the other
interface.