Problems gettin DSL setup

Wesson · 01-15-2003, 03:17 PM

Hello, I am a total Linux newbie. I downloaded Mandrake 9.0 and installed the os fine, but when I log into KDE 3 as root, I run the linuxconf to setup my dsl connection and it will not work at all.

I have a static ip address, and I have been given my ip, subnet, dns, and gateway addresses, but it also asks for like hostname or domains, and I didn't get that information, so I am stuck, I can ping my gateway, but that is it, I can't ping the dns servers or anything past the gateway, so I was going to start the networking setup over again and we rreally appreciate anyone who can give me tips on how to get this DSL working

Thanks

phoenix · 01-15-2003, 03:47 PM

I had the same problem with my Red Hat 8.0 when we got DSL. I had my comp going through a switch to a router and then to the DSL modem. One of the RJ45's was connected to the uplink. I dont know why it didnt work that way but when I removed the one cable from the uplink and put it in one of the regular jacks it worked just fine without having to configure anything. (The router was already set up with the info from my ISP).

I hope this helps...

Wesson · 01-15-2003, 03:55 PM

Thanks for the reply, but unfortunatly, I have my phone line running directly into my Alcatel DSL modem/router, then from the modem into my nic on my computer, there is no switch or router....

macewan · 01-16-2003, 07:15 PM

mine going through router to modem using dhcp

neo77777 · 01-17-2003, 10:41 PM

I am a lazy one to go from step to step but here is the guide I pasted from speakeasy support page

Quote:

(in the examples below, the items marked (xx.xx.xxx) are specific to your configuration, please refer to your Network Information email sent to your Speakeasy address priot to your DSL installation.)

1. Get into text mode. either open an xterm or use ctrl-alt-f1 to go to a virtual console

2. Become root. either login as root or su
[enter password].

3. Run ifconfig eth0 ( should be /sbin/ifconfig ) to display ethernet adapters
This should list something like: eth0 Link encap:Ethernet HWaddrxx:xx:xx:xx:xx:xx:xx
inet addr: xxx.xxx.xxx.xxx Bcast: xxx.xxx.xxx.xxx Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:9 txqueuelen:100
Interrupt:15 Base address:0xa800

4. If eth0 shows up, goto step 8
if there is no eth0 listed the ethernet adapater was not detected.

5. Determine type of ethernet card. PCI ethernet cards are listed in /proc/pci
grep Ethernet /proc/pci

6. Find the kernel module for your ethernet card The most common drivers are
Ethernet controller: Module:
Intel 82557 eepro100
DEC DC2104* tulip
NE2000 and Compatible 8390 + ne2k-pci
Fast EtherLink 3c590/3c592/3c595/3c597,
EtherLink XL 3c900 and 3c905 3c59x
VIA VT86c100A Rhine-II PCI Fast Ethernet,
3043 Rhine-I via-rhine
lo (loopback,local,lo) loopback

7. insmod Module ( insmod should be /sbin/insmod )
The required module should be in /lib/modules/`uname -r`/net/
where `uname -r` is the kernel revision
( for ne2000 cards, first insmod 8390, then insmod ne2k-pci )

8. ifconfig eth0 xxx.xxx.xxx.xxx (replace xxx.xxx.xxx.xxx with your IP )
The gateway is usually the same as your IP number but with 1 as the last number,
ie. xxx.xxx.xxx.1
route add xxx.xxx.xxx.x eth0 (replace xxx.xxx.xxx.x with your gateway IP )
( route should be /sbin/route )
route add default gw xxx.xxx.xxx.x

9. Verify routes with
netstat -rn ( should be /bin/netstat )
Output:
Destination Gateway Genmask Flags MSS Window irtt Iface
xxx.xxx.xxx.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
xxx.xxx.xxx.1 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 xxx.xxx.xxx.1 0.0.0.0 UG 0 0 0 eth0

10. ping -c 5 xxx.xxx.xxx.1 (ping the gateway)
(should be /bin/ping)
Ping the name server address to verify internet connectivity

11. If the ping commands report
5 packets transmitted, 5 packets received, 0% packet loss
the interface is properly configured. put the insmod command from step 7
( if you had to load a module ) and the ifconfig and route commands from step 8 to the end of the file /etc/rc.d/rc.local

12. put up to 3 nameservers (as provided in your netwotrk information email) in /etc/resolv.conf
like:
nameserver yyy.yyy.yyy.yyy
nameserver zzz.zzz.zzz.zzz

13. Verify that the resolver is setup to use /etc/hosts and bind in /etc/host.conf
like:
order hosts,bind
multi on