Jump to content

adsl help needed - newbie


arctic
 Share

Recommended Posts

Okay, I changed everthing, just as you told me, but sadly it still doesn't work. Here come the results I got:

 

[root@localhost root]# ifup eth0

[root@localhost root]# ifconfig -a

eth0 Protokoll:Ethernet Hardware Adresse 00:50:BF:A0:68:30

inet Adresse:10.0.0.2 Bcast:10.255.255.255 Maske:255.0.0.0

inet6 Adresse: fe80::250:bfff:fea0:6830/64 Gültigkeitsbereich:Verbindung

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:62 dropped:0 overruns:0 carrier:124

Kollisionen:0 Sendewarteschlangenlänge:1000

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Interrupt:11 Basisadresse:0xec00

 

lo Protokoll:Lokale Schleife

inet Adresse:127.0.0.1 Maske:255.0.0.0

inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:181 errors:0 dropped:0 overruns:0 frame:0

TX packets:181 errors:0 dropped:0 overruns:0 carrier:0

Kollisionen:0 Sendewarteschlangenlänge:0

RX bytes:11652 (11.3 Kb) TX bytes:11652 (11.3 Kb)

 

sit0 Protokoll:IPv6-nach-IPv4

NOARP MTU:1480 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

Kollisionen:0 Sendewarteschlangenlänge:0

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

 

[root@localhost root]# pppoe -I eth0 -A

pppoe: Timeout waiting for PADO packets

[root@localhost root]# ping -c5 10.0.0.2

PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.

64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.075 ms

64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.066 ms

64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.061 ms

64 bytes from 10.0.0.2: icmp_seq=4 ttl=64 time=0.064 ms

64 bytes from 10.0.0.2: icmp_seq=5 ttl=64 time=0.062 ms

 

--- 10.0.0.2 ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 3998ms

rtt min/avg/max/mdev = 0.061/0.065/0.075/0.010 ms

[root@localhost root]# ping -c5 217.160.137.199

connect: Network is unreachable

 

Still, when I type http://10.0.0.3 in web browser, the result is still the same....

I never thought that setting up a dsl-connection with linux will be thta hard. But I don't want to give up. ; )

And by the way: thanx for your patience.

Link to comment
Share on other sites

  • Replies 30
  • Created
  • Last Reply

Top Posters In This Topic

You have still got the IP address of your PC set to 10.0.0.2 !

 

So you are pinging the PC eth0 network interface...

 

The default IP address of the modem is 10.0.0.2 , so you ABSOLUTELY CANNOT have the same address on your PC.

 

So change the PC eth0 address to 10.0.0.3 in /etc/sysconfig/network-scripts/ifcfg-eth0 and reboot or "ifup eth0" and "ping 10.0.0.2" (the modem) should then work, as well as http://10.0.0.2 in your browser.

 

Chris

Link to comment
Share on other sites

Okay... should my ifconfig.eth0 look like this then?

 

DEVICE=eth0

BOOTPROTO=10.0.0.3

IPADDR=10.0.0.3

NETMASK=255.0.0.0

NETWORK=10.0.0.0

BROADCAST=10.255.255.255

ONBOOT=yes

MII_NOT_SUPPORTED=yes

 

If yes, this is the result i get now.

 

[[root@localhost root]# ifup eth0

[root@localhost root]# ifconfig eth0

eth0 Protokoll:Ethernet Hardware Adresse 00:50:BF:A0:68:30

inet Adresse:10.0.0.3 Bcast:10.255.255.255 Maske:255.0.0.0

inet6 Adresse: fe80::250:bfff:fea0:6830/64 Gültigkeitsbereich:Verbindung

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:98 dropped:0 overruns:0 carrier:196

Kollisionen:0 Sendewarteschlangenlänge:1000

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Interrupt:11 Basisadresse:0xec00

 

[root@localhost root]# ping -c5 10.0.0.2

PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.

64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.068 ms

64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=0.063 ms

64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.063 ms

64 bytes from 10.0.0.2: icmp_seq=4 ttl=64 time=0.057 ms

64 bytes from 10.0.0.2: icmp_seq=5 ttl=64 time=0.065 ms

 

--- 10.0.0.2 ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 3999ms

rtt min/avg/max/mdev = 0.057/0.063/0.068/0.006 ms

 

 

I also tried with ping 10.0.0.3, in order to see what happens. The result is here:

 

 

[root@localhost root]# ping -c5 10.0.0.3

PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.

64 bytes from 10.0.0.3: icmp_seq=1 ttl=64 time=0.075 ms

64 bytes from 10.0.0.3: icmp_seq=2 ttl=64 time=0.061 ms

64 bytes from 10.0.0.3: icmp_seq=3 ttl=64 time=0.062 ms

64 bytes from 10.0.0.3: icmp_seq=4 ttl=64 time=0.062 ms

64 bytes from 10.0.0.3: icmp_seq=5 ttl=64 time=0.063 ms

 

--- 10.0.0.3 ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 3999ms

rtt min/avg/max/mdev = 0.061/0.064/0.075/0.010 ms

 

 

Acessing 10.0.0.2 in browser still won't work.

Link to comment
Share on other sites

Excellent - except for the BOOTPROTO=10.0.0.3 bit - should be BOOTPROTO=static (but that's not causing your problem).

 

So your network is up, and you can ping between the modem and the computer. :)

 

Now we need to look at why you cannot access the modem set up in your browser...

 

Try the browser for me again - type or copy/paste

 http://10.0.0.2/

exactly like that in the address bar. Then hit the refresh button to make sure.

 

Could also try typing "lynx 10.0.0.2" in a terminal - this is a text based browser, and may work for you.

 

If neither of these work, there is a reset button under your modem (see your manual) Press it and try again.

 

Chris

Link to comment
Share on other sites

Changed the BOOTPROTO to static, rebooted and started ifup eth0, then tried to access http://10.0.0.2/ in Mozilla. The result was that Mozilla told me "Connection to 10.0.0.2 was refused"

Then I tried to look if ping does work, the result is this:

 

[root@localhost root]# ping -c5 10.0.0.2

PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.

From 10.0.0.3 icmp_seq=1 Destination Host Unreachable

From 10.0.0.3 icmp_seq=2 Destination Host Unreachable

From 10.0.0.3 icmp_seq=3 Destination Host Unreachable

From 10.0.0.3 icmp_seq=4 Destination Host Unreachable

From 10.0.0.3 icmp_seq=5 Destination Host Unreachable

 

--- 10.0.0.2 ping statistics ---

5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 3998ms

, pipe 3

 

I made reset on the modem, but it remained the same. Although I made everything the way you explained... :wall:

Link to comment
Share on other sites

???

 

Please post output of the command "ifconfig eth0" and your ifcfg-eth0 file again.

 

"Connection to 10.0.0.2 was refused" implies packet filtering - a firewall..

 

So please install iptables - type "urpmi iptables" as root, then post the output of

 iptables -nvL -t nat

 

Chris

Link to comment
Share on other sites

Here comes the ifcongig eth0- output:

 

[root@localhost root]# ifup eth0

[root@localhost root]# ifconfig eth0

eth0 Protokoll:Ethernet Hardware Adresse 00:50:BF:A0:68:30

inet Adresse:10.0.0.3 Bcast:10.255.255.255 Maske:255.0.0.0

inet6 Adresse: fe80::250:bfff:fea0:6830/64 Gültigkeitsbereich:Verbindung

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:19 dropped:0 overruns:0 carrier:38

Kollisionen:0 Sendewarteschlangenlänge:1000

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Interrupt:11 Basisadresse:0xec00

 

Strangely, ping functioned again! But in the browser, the http://10.0.0.2/ and 10.0.0.3 still could not be accessed.

 

[root@localhost root]# ping -c5 10.0.0.3

PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.

64 bytes from 10.0.0.3: icmp_seq=1 ttl=64 time=0.068 ms

64 bytes from 10.0.0.3: icmp_seq=2 ttl=64 time=0.060 ms

64 bytes from 10.0.0.3: icmp_seq=3 ttl=64 time=0.061 ms

64 bytes from 10.0.0.3: icmp_seq=4 ttl=64 time=0.063 ms

64 bytes from 10.0.0.3: icmp_seq=5 ttl=64 time=0.066 ms

 

--- 10.0.0.3 ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 3999ms

rtt min/avg/max/mdev = 0.060/0.063/0.068/0.009 ms

[root@localhost root]#

 

This is the current igcfg-eth0 file

 

DEVICE=eth0

BOOTPROTO=static

IPADDR=10.0.0.3

NETMASK=255.0.0.0

NETWORK=10.0.0.0

BROADCAST=10.255.255.255

ONBOOT=yes

MII_NOT_SUPPORTED=yes

 

Now starting the iptables thing:

 

[root@localhost root]# urpmi iptables

Alles bereits installiert [it says, I have already installed all parts of iptables]

[root@localhost root]# iptables -nvL -t nat

Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)

pkts bytes target prot opt in out source destination

 

Chain POSTROUTING (policy ACCEPT 6 packets, 504 bytes)

pkts bytes target prot opt in out source destination

 

Chain OUTPUT (policy ACCEPT 6 packets, 504 bytes)

pkts bytes target prot opt in out source destination

[root@localhost root]#

 

The only good thing on this problem is, that I do learn a little bit about the way, linux works (or, as in my case: doesn't work) *lol*.

Link to comment
Share on other sites

[root@localhost root]# ifup eth0

[root@localhost root]# ping -c5 10.0.0.2

PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.

From 10.0.0.3 icmp_seq=1 Destination Host Unreachable

From 10.0.0.3 icmp_seq=2 Destination Host Unreachable

From 10.0.0.3 icmp_seq=3 Destination Host Unreachable

From 10.0.0.3 icmp_seq=4 Destination Host Unreachable

From 10.0.0.3 icmp_seq=5 Destination Host Unreachable

 

--- 10.0.0.2 ping statistics ---

5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 3999ms

, pipe 3

 

[root@localhost root]# iptables -nvL

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)

pkts bytes target prot opt in out source destination

 

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)

pkts bytes target prot opt in out source destination

 

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)

pkts bytes target prot opt in out source destination

 

[root@localhost root]# ifconfig eth0

eth0 Protokoll:Ethernet Hardware Adresse 00:50:BF:A0:68:30

inet Adresse:10.0.0.3 Bcast:10.255.255.255 Maske:255.0.0.0

inet6 Adresse: fe80::250:bfff:fea0:6830/64 Gültigkeitsbereich:Verbindung

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:34 dropped:0 overruns:0 carrier:68

Kollisionen:0 Sendewarteschlangenlänge:1000

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Interrupt:11 Basisadresse:0xec00

 

I tried ping 10.0.0.3 once again, in order to see, if everything was weird again, but ping worked here.

 

[root@localhost root]# ping -c5 10.0.0.3

PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.

64 bytes from 10.0.0.3: icmp_seq=1 ttl=64 time=0.080 ms

64 bytes from 10.0.0.3: icmp_seq=2 ttl=64 time=0.071 ms

64 bytes from 10.0.0.3: icmp_seq=3 ttl=64 time=0.084 ms

64 bytes from 10.0.0.3: icmp_seq=4 ttl=64 time=0.072 ms

64 bytes from 10.0.0.3: icmp_seq=5 ttl=64 time=0.073 ms

 

--- 10.0.0.3 ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 3998ms

rtt min/avg/max/mdev = 0.071/0.076/0.084/0.005 ms

[root@localhost root]# iptables -nvL

Chain INPUT (policy ACCEPT 30 packets, 2094 bytes)

pkts bytes target prot opt in out source destination

 

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)

pkts bytes target prot opt in out source destination

 

Chain OUTPUT (policy ACCEPT 30 packets, 2094 bytes)

pkts bytes target prot opt in out source destination

 

[root@localhost root]#

 

In the browser, it still says: connection to 10.0.0.2 was refused.

Link to comment
Share on other sites

Ah, I almost forgot... by accident I forgot the -c5 before the ping the first time. That time I got that result in an endless turn, so that i had to restart the system in order to stop it. Output is here:

 

[root@localhost root]# ifup eth0

[root@localhost root]# ping 10.0.0.2

PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.

From 10.0.0.3 icmp_seq=1 Destination Host Unreachable

From 10.0.0.3 icmp_seq=2 Destination Host Unreachable

From 10.0.0.3 icmp_seq=3 Destination Host Unreachable

From 10.0.0.3 icmp_seq=4 Destination Host Unreachable

From 10.0.0.3 icmp_seq=5 Destination Host Unreachable

From 10.0.0.3 icmp_seq=6 Destination Host Unreachable

From 10.0.0.3 icmp_seq=7 Destination Host Unreachable

From 10.0.0.3 icmp_seq=8 Destination Host Unreachable

From 10.0.0.3 icmp_seq=9 Destination Host Unreachable

From 10.0.0.3 icmp_seq=10 Destination Host Unreachable

From 10.0.0.3 icmp_seq=11 Destination Host Unreachable

From 10.0.0.3 icmp_seq=12 Destination Host Unreachable

From 10.0.0.3 icmp_seq=13 Destination Host Unreachable

From 10.0.0.3 icmp_seq=14 Destination Host Unreachable

From 10.0.0.3 icmp_seq=15 Destination Host Unreachable

From 10.0.0.3 icmp_seq=16 Destination Host Unreachable

From 10.0.0.3 icmp_seq=17 Destination Host Unreachable

...and so on and so on....

I restarted the system, when I reached... icmp_seq=242 Destination Host Unreachable

Link to comment
Share on other sites

This is getting frustrating...

 

Right - we have got your Ip address on the computer OK (192.168.0.3), and your network card is working because you can ping it.

 

You have no firewall rules, so that's not stopping it working.

 

I don't think the modem has a firewall (and you reset it anyway), but please check the manual.

 

Please post your routing table - type "route -n" as root.

 

All that remains after that is the cabling...

 

Try unplugging the cable, then plugging it back in again.

 

Are you using the cable that came with the modem?

 

Or is it a crossover cable?

In a normal cable, the coloured wires all go to the same pins at each end, eg orange/white is pin 1 on both ends, pin 2 is orange. (these 2 pins could also be green/white & green, but the point is, they are 'straight through').

In a crossover cable, the cables at pins 1&2 at each end go to pins 3&6 at the other.

 

Chris

Link to comment
Share on other sites

Okay, it is not only me, who is getting frustrated with that stuff . :cheesy:

before I log off, I give you all information on the cables I have (I attached both cables that are inluded in the package). One ethernet cable RJ45:

 

pin 1 = Rx+, orange/white

pin 2 = Rx-, orange

pin 3 = Tx+, green/white

pin 4 = N/A, blue

pin 5 = N/A, blue

pin 6 = Tx-, green

pin 7 = N/A, brown/white

pin 8 = N/A, brown

 

Then there is the RJ-11 ADSLl cable, whrere it says

 

pin 1 = not used

pin 2 = ADSL-signal UKA'a

pin 3 = ADSL-signal UKA'b

pin 4 = not used

 

I do have a second set of cables here and will try them in a minute. Maybe it is simply a broken cable? That would be quite weird....

Will be back soon.

:screwy:

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share


×
×
  • Create New...