arctic
-
Posts
8155 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by arctic
-
-
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.
-
oops... emoticon-bug... sorry. *g*
-
Okay, I changed all and now I get this result.
[root@localhost root]# ifup eth0
Determining IP information for eth0... failed; no link present. Check cable?
[root@localhost root]# ifconfig -a
eth0 Protokoll:Ethernet Hardware Adresse 00:50:BF:A0:68:30
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:44 dropped:0 overruns:0 carrier:88
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:64 errors:0 dropped:0 overruns:0 frame:0
TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:4078 (3.9 Kb) TX bytes:4078 (3.9 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)
I don't understand, why it bothers me now with "cable connection check". The parts are new and they ARE functional and I connected the cables to the defined parts of the dsl-modem, the splitter and the network card...
Just in case that this one helps, her comes my "ifcfg.eth0"
DEVICE=eth0
BOOTPROTO=dhcp
IPADDR=10.0.0.2
NETMASK=255.0.0.0
NETWORK=10.0.0.0
BROADCAST=10.255.255.255
ONBOOT=yes
MII_NOT_SUPPORTED=no
Any clues?
-
okay... will try it one more time... *logging off once again*
-
nope... when I tried to access ip 10.0.0.1, 10.0.0.2 or 10.0.0.3, the only message I got in the browser was something like this (translation):
time limit expended on server
connection existed to 10.0.0.1 at port 80
So, what do I do now? :o
-
Most user use the ALSA output. You can choose between the different sound-systems e.g. in the k-control center. I had to change to ALSA, because most applications crashed with OSS, especially XMMS. By the way, if you start some applications, check their native sound settings also. With XMMS, I had to change OSS to ALSA in the "Options" menu, too, otherwise, it froze.
-
changed IP adress to 10.0.0.2. Here are the new results.
[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:90 dropped:0 overruns:0 carrier:180
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:260 errors:0 dropped:0 overruns:0 frame:0
TX packets:260 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:18514 (18.0 Kb) TX bytes:18514 (18.0 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
-
okay, back again... I didn't get it to work. I tried several ip's.
Just in case that it helps, here is the result i got from the konsole:
[root@xerxes root]# ifup eth0
[root@xerxes root]# ifconfig -a
eth0 Protokoll:Ethernet Hardware Adresse 00:50:BF:A0:68:30
inet Adresse:1.1.1.1 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:39 dropped:0 overruns:0 carrier:78
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:162 errors:0 dropped:0 overruns:0 frame:0
TX packets:162 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:10172 (9.9 Kb) TX bytes:10172 (9.9 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@xerxes root]# pppoe -I eth0 -A
pppoe: Timeout waiting for PADO packets
I always get the PADO-timeout message (dunno what this means), and it is irrelevant if I config the net via LAN or ADSL. Any clues?... This is so annoying. : (
-
Okay, I will give it a try... if it works, thanx in advance, if not, I will come back. ; )
*logging off and starting mandrake*
-
I do know this bug and it is annoying. The only way not to crash kontact is NOT to click on notes, until you get a patch for kontact. If you need some notes, try alternative programs for that one. There are many alternatives (just browse e.g. kde-apps.org).
-
Hello, everyone.
I just installed Mandrake 10 (2.6 kernel) next to my win98 partition and need help, in order to get rid of microsoft. I still don't have a net access under mdk. : (
So, here is my problem:
I have a rather old comp (750mhz, 330 mb ram) and two network cards. One old teledat 300pci-dsl/ethernet modem (which won't and can't function under linux ) and a newly acquired LG LAM200E adsl modem (kernel 2.4 - 2.6 compatible, works with pppoe) with a sitecom network 10/100 pci-card.
Mandrake finds my network card. no problem there. Adsl-setup under mdk is also fine so far. My problem is the self-configuring LG ADSL-modem which is especially suited for Linux. When I start the modem, I have to set the ip settings of mdk(same in win98) to 10.0.0.2 (so says the installation handbook, which is a mess by the way...). Then I have to open the browser and the modem should open a configure-dialogue. It says in the handbook, that it should work like a router-setup (dunno, how that works, never had a router).
When I open Konqueror/Mozilla and try to access the 10.0.0.2 ip, I don't get any results, just a blank screen in Konqueror/Mozilla, so there is no chance to "self-configure" the adsl modem.
Is there anyone who can help me/give me a clue, what I am doing wrong, so that I can finally access the web via mandrake? (by the way, the adsl-networking under win98 with the teledat works fine, so this shouldn't be a problem with my provider, right?) :unsure:
Thanx in advance.
arctic
adsl help needed - newbie
in Networking
Posted
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.