Ein Internet-Cafe machte es dann doch noch möglich!
Hier nun die diversen Ausgaben und Angaben:
Ein Rechner direkt via Netzwerkkarte an DSL Modem (das schöne alte weiße Teil) der Telekom.
Internet funktionierte vorher mit Windows porblemlos.
lspci | grep Ethernet
0000:00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
0000:01:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
egrep -v "^$|^#" /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet dhcp
auto eth2
iface eth2 inet dhcp
auto ath0
iface ath0 inet dhcp
auto wlan0
iface wlan0 inet dhcp
auto dsl-provider
iface dsl-provider inet ppp
provider dsl-provider
pre-up /sbin/ifconfig eth1 up # line maintained by pppoeconf
egrep -v "^$|^#" /etc/resolv.conf
domain home
nameserver 194.25.2.129
nameserver 82.141.0.101
egrep -v "^$|^#" /etc/hosts
127.0.0.1 localhost radio
127.0.1.1 radio
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
ifconfig -a
eth0 Protokoll:Ethernet Hardware Adresse 00:0C:76:BC:FC:7F
UP BROADCAST MULTICAST MTU:1500 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:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:201 Basisadresse:0x2000
eth1 Protokoll:Ethernet Hardware Adresse 00:C1:26:05:2F:2E
inet6 Adresse: fe80::2c1:26ff:fe05:2f2e/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:43 errors:0 dropped:0 overruns:0 frame:0
TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX bytes:2640 (2.5 KiB) TX bytes:15617 (15.2 KiB)
Interrupt:217 Basisadresse:0x6000
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:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:0
RX bytes:272 (272.0 b) TX bytes:272 (272.0 b)
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)
route
Kernel IP Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
Ich hoffe nun sind erstmal alle Informationen da, die benötigt werden...
und ich hoffe nun kann man mir hlefen....
Ach ja...die Zugangasdaten xxxxxxxxxxxxyyyyyyyyyyyy#001@t-online.de bzw. ohne "#" sind schon getestet worden...
Passwort wurde mehrfach überprüft und ist korrekt!
pppoeconf findet angeblich alles trägt aber die DNS Server nicht automatisch ein.
Wenn dann mit pon dsl-provider gestartet werden soll, kommt folgende Meldung
Plugin rp-pppoe.so loaded
Und Internet ist immer noch tot.
Dann mit ps -ela | grep pppd überprüft ob der Dämon laüft - tut er nicht.
Also mit
sudo pppd
pppd: The remote system is required to authenticate itself
pppd: but I couldn't find any suitable secret (password) for it to use to do so.
pppd: (None of the available passwords would let it use an IP address.)
Die pap-secrets sieht wie folgt aus
#
# /etc/ppp/pap-secrets
#
# This is a pap-secrets file to be used with the AUTO_PPP function of
# mgetty. mgetty-0.99 is preconfigured to startup pppd with the login option
# which will cause pppd to consult /etc/passwd (and /etc/shadow in turn)
# after a user has passed this file. Don't be disturbed therefore by the fact
# that this file defines logins with any password for users. /etc/passwd
# (again, /etc/shadow, too) will catch passwd mismatches.
#
# This file should block ALL users that should not be able to do AUTO_PPP.
# AUTO_PPP bypasses the usual login program so it's necessary to list all
# system userids with regular passwords here.
#
# ATTENTION: The definitions here can allow users to login without a
# password if you don't use the login option of pppd! The mgetty Debian
# package already provides this option; make sure you don't change that.
# INBOUND connections
# Every regular user can use PPP and has to use passwords from /etc/passwd
* hostname "" *
# UserIDs that cannot use PPP at all. Check your /etc/passwd and add any
# other accounts that should not be able to use pppd!
guest hostname "*" -
master hostname "*" -
root hostname "*" -
support hostname "*" -
stats hostname "*" -
# OUTBOUND connections
# Here you should add your userid password to connect to your providers via
# PAP. The * means that the password is to be used for ANY host you connect
# to. Thus you do not have to worry about the foreign machine name. Just
# replace password with your password.
# If you have different providers with different passwords then you better
# remove the following line.
# * password
"usernamexxxxxxxxxxxxyyyyyyyyyyyy#0001@t-online.de" * "xxxxxxxx"
dsl-providers
# Minimalistic default options file for DSL/PPPoE connections
noipdefault
defaultroute
replacedefaultroute
hide-password
#lcp-echo-interval 30
#lcp-echo-failure 4
noauth
persist
#mtu 1492
usepeerdns
plugin rp-pppoe.so eth1
user "usernamexxxxxxxxxxxxyyyyyyyyyyyy#0001@t-online.de"
So siehts aus!
Wer weiß Rat????? Bitte