SOLUTION: got adsl-start, dsl working with Mandrake 9.1

SOLUTION: got adsl-start, dsl working with Mandrake 9.1

Post by Dale Hampl » Sun, 01 Jun 2003 12:22:58



I apologize for the length of this, but if you need it, you really need
it.  I'm using Mandrake 9.1.  Among my other problems was drakconnect,
the module of Mandrake Control Center that sets up your networking.  It
persistently created '/etc/sysconfig/ifcg-eth1 (using module tulip)' as
my network interface.  The parenthetical thing is the issue.  Not only
does that file, with the parens, get created, but reference to it
appears in /etc/ppp/pppoe.conf, and adsl-start (which is called by
everything) chokes on the first paren.  Putting '' marks around it
didn't do much good.  So I made sure that my ifcfg-eth1 file was right.

Here's what I did.

->Edited /etc/ppp/pppoe.conf as follows:
        got rid of the (using module tulip) and just have ETH1

->Edited /etc/sysconfig/network-scripts/ifcfg-eth1 to be:
DEVICE=eth1
BOOTPROTO=dhcp
IPADDR=
NETMASK=
NETWORK=
BROADCAST=
ONBOOT=no
MII_NOT_SUPPORTED=yes
NEEDHOSTNAME=yes

->Ignoring advice on the web, ran dhclient to get an IP address for eth1
        (neither eth1 nor the network is set to start on boot anymore)

->started the connection with DEBUG=1 adsl-start (not expecting it work,
really)

->looked at Network Monitoring, found to my surprise that it says
"connected" and shows activity on eth1.  There's no little tab for ppp0.
  Mozilla, etc., works.

->Here's the relevant section from ifconfig (no entry for ppp0):
eth1      Link encap:Ethernet  HWaddr y:y:y:y:y:y
           inet addr:x.x.x.x  Bcast:x.x.x.255  Mask:255.255.252.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:292 errors:0 dropped:0 overruns:0 frame:0
           TX packets:402 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:100
           RX bytes:119725 (116.9 Kb)  TX bytes:47493 (46.3 Kb)
           Interrupt:10 Base address:0xe000

->Here's the output from route (I have an internal lan on eth0):
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
x.x.x.0       0.0.0.0         255.255.252.0   U     0      0        0 eth1
0.0.0.0         x.x.x.1       0.0.0.0         UG    0      0        0 eth1

->The /tmp txt file that is mentioned at the end of the DEBUG=1
adsl-start still only shows 3 PADI packets, and does not appear to have
seen any PADO packets.  This is a mystery:
* The following section is a dump of the packets
* sent and received by rp-pppoe.
{snip}
rp-pppoe debugging dump
rp-pppoe-3.5
21:06:36.305 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr y:y:y:y:y:y DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 72 35 00 00               ........r5..

21:06:41.298 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr  y:y:y:y:y:y DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 72 35 00 00               ........r5..

21:06:51.298 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr  y:y:y:y:y:y DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 72 35 00 00               ........r5..

{the y:y: thing is my editing;  the ff:ff: thing is real}

 
 
 

SOLUTION: got adsl-start, dsl working with Mandrake 9.1

Post by Horst Knobloc » Sun, 01 Jun 2003 21:13:56



[...]

Quote:> Here's what I did.

[edit pppoe.conf]

Quote:> ->Edited /etc/sysconfig/network-scripts/ifcfg-eth1 to be:
> DEVICE=eth1
> BOOTPROTO=dhcp
> IPADDR=
> NETMASK=
> NETWORK=
> BROADCAST=
> ONBOOT=no
> MII_NOT_SUPPORTED=yes
> NEEDHOSTNAME=yes

> ->Ignoring advice on the web, ran dhclient to get an IP address for eth1
> (neither eth1 nor the network is set to start on boot anymore)

My advice to get rid off the DHCP stuff was based on the assumption
that you need to use PPPoE for connecting to your ISP. However
everything you wrote here in this posting indicates that your ISP
does not speak PPPoE.

In this case it is the other way around, you can forget about
the PPPoE and adsl-start stuff. Just use your eth interface and
DHCP to get the IP configuration. If you have BOOTPROTO=dhcp in
ifcfg-eth1, most GUI wrappers for bringing up this interface
also call the DHCP client to get the IP config.

Quote:> ->started the connection with DEBUG=1 adsl-start (not expecting it work,
> really)

> ->looked at Network Monitoring, found to my surprise that it says
> "connected" and shows activity on eth1.  There's no little tab for ppp0.
>   Mozilla, etc., works.

> ->Here's the relevant section from ifconfig (no entry for ppp0):
> eth1      Link encap:Ethernet  HWaddr y:y:y:y:y:y
>            inet addr:x.x.x.x  Bcast:x.x.x.255  Mask:255.255.252.0
[...]

> ->Here's the output from route (I have an internal lan on eth0):
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
[...]
> x.x.x.0       0.0.0.0         255.255.252.0   U     0      0        0
> eth1
> 0.0.0.0         x.x.x.1       0.0.0.0         UG    0      0        0
> eth1

This is a clear indication that you got your IP and netmask
as the default gateway via DHCP from your provider.

- Show quoted text -

Quote:> ->The /tmp txt file that is mentioned at the end of the DEBUG=1
> adsl-start still only shows 3 PADI packets, and does not appear to have
> seen any PADO packets.  This is a mystery:
[...]
> 21:06:36.305 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
> SourceAddr y:y:y:y:y:y DestAddr ff:ff:ff:ff:ff:ff
> 01 01 00 00 01 03 00 04 72 35 00 00               ........r5..

> 21:06:41.298 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
> SourceAddr  y:y:y:y:y:y DestAddr ff:ff:ff:ff:ff:ff
> 01 01 00 00 01 03 00 04 72 35 00 00               ........r5..

> 21:06:51.298 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
> SourceAddr  y:y:y:y:y:y DestAddr ff:ff:ff:ff:ff:ff
> 01 01 00 00 01 03 00 04 72 35 00 00               ........r5..

> {the y:y: thing is my editing;  the ff:ff: thing is real}

This is another indication that your ISP has no PPPoE access
concentrator listening to your request and so PPP/PPPoE is
of no use for your ISP access.

So in short forget about PPPoE and adsl-start, and just bring up
eth1 by "ifup eth1" or the GUI tool you have for this.

Ciao, Horst
--
?When pings go wrong (It hurts me too)? E.Clapton/E.James/P.Tscharn

 
 
 

1. Mandrake Control Center in Mandrake 9.1 not working

When i try to execute Mandrake Control Center in Mandrake 9.1 (I updated it
just few days ago from Mandrake 9.0), I get this error message:

drakconf.real:12591 WARNING : No builtin or dinamically loaded modules were
found - Pango will correct it. This problem was an error in the creation of
: '/etc/pango/pango.modules' FATAL: error loading image: couldn't recognize
the image file format for file
'/usr/share/mcc/themes/default/mcc_title_icon.png' at
'/usr/lib/libDrak/ugtk2.pm line 529

Could someone help me?

Francesco
--
----------------------------------------------------------------------------
-------------

Teaching OnLine

Corsi online di Informatica

VBA for Access, Visual Basic, Delphi, C/C++
PHP, ASP, JavaScript, SQL, Kylix, Fortran
MySQL, Linux, Apache, ECDL

http://www.teachingonline.it/index.asp

Bruce Eckel's Free Electronic Books
http://www.teachingonline.it/Bruceeckelbooks/

2. Segmentation faults when compiling kernel

3. ugly networking issue, any ideas out there?

4. netcfg question...

5. usb adsl modem and mandrake 9.1 help???

6. creating a bootable CD with a Redhat dist

7. Mandrake 9.1 and SpeedTouch ADSL modem

8. adsl-start times out - no dsl

9. No USB peripherials works with Mandrake 9.1

10. Opera 7.x Beta DOES NOT WORK WITH MANDRAKE 9.1

11. How to get Mandrake 9.1 to work with HP 5470c scanner?!?