Hallo so, bin folgendermaßen vorgegagen
1. ifconfig -a
Ausgabe:
eth0 Link encap:Ethernet HWaddr 00:16:D3:5B:FB:8B
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
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
so dann hab ich mir mit "dhcpcd eth0" eine IP besorgt (im Windows und Ubuntu musste die Lan verbindung auch erst stehen bevor es geht)
so nun kommen wieder die beiden Varianten.
1. Variante vorgehen nach Wiki:
- alle dateien wie im Wiki angelegt und bearbeitet.
- Da keine resolv.conf im /etc/ppp/ lag hab ich eine erstellt mit den gleichen Daten wie im Ubuntu
- pppd call pppoe aufgerufen (wie im Wiki)
Ausgabe auf der Konsole:
Plugin rp-pppoe.so loaded.
Linux kernel does not support PPPoE -- are you running 2.4.x?
Eintrag aus der /var/log/errors.log:
Apr 1 22:07:47 (none) pppd[3906]: Linux kernel does not support PPPoE -- are you running 2.4.x?
Eintrag aus der /var/log/messages.log:
Apr 1 22:07:47 (none) pppd[3906]: Plugin rp-pppoe.so loaded.
Apr 1 22:07:47 (none) pppd[3906]: Exit.
- als nachstes habe ich dann mit "modprobe pppoe" versucht das Problem zu behen. keinerlei ausgaben dabei
- erneut pppd call pppoe aufgerufen
Ausgabe auf der Konsole:
Plugin rp-pppoe.so loaded.
RP-PPPoE plugin version 3.3 compiled against pppd 2.4.4
Eintrag aus der /var/log/messages.log
Apr 1 22:08:57 (none) PPP generic driver version 2.4.2
Apr 1 22:08:57 (none) NET: Registered protocol family 24
Apr 1 22:09:03 (none) pppd[3922]: Plugin rp-pppoe.so loaded.
Apr 1 22:09:03 (none) pppd[3922]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.4
Apr 1 22:09:13 (none) pppd[3923]: pppd 2.4.4 started by root, uid 0
Apr 1 22:09:13 (none) pppd[3923]: PPP session is 110
Apr 1 22:09:13 (none) pppd[3923]: Using interface ppp0
Apr 1 22:09:13 (none) pppd[3923]: Connect: ppp0 <--> eth0
Apr 1 22:09:13 (none) pppd[3923]: Warning - secret file /etc/ppp/pap-secrets has world and/or group access
Apr 1 22:09:16 (none) pppd[3923]: peer from calling number 00:0C:6E:E3:F0:B8 authorized
Apr 1 22:09:16 (none) pppd[3923]: LCP terminated by peer (peer refused to authenticate)
Apr 1 22:09:19 (none) pppd[3923]: Connection terminated.
Apr 1 22:09:19 (none) pppd[3923]: Modem hangup
kein eintrag in der errors.log
- danach noch ipconfig -a und route -n ausgeführt:
eth0 Link encap:Ethernet HWaddr 00:16:D3:5B:FB:8B
inet addr:192.168.1.90 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1548 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:152048 (148.4 Kb) TX bytes:2498 (2.4 Kb)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
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
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
Variante 2 nutzen von pppoe-setup + pppoe-start
- zuerst pppoe-setup gemacht hat folgende /etc/ppp/pppoe.conf produziert:
#***********************************************************************
#
# pppoe.conf
#
# Configuration file for rp-pppoe. Edit as appropriate and install in
# /etc/ppp/pppoe.conf
#
# NOTE: This file is used by the pppoe-start, pppoe-stop, pppoe-connect and
# pppoe-status shell scripts. It is *not* used in any way by the
# "pppoe" executable.
#
# Copyright (C) 2000 Roaring Penguin Software Inc.
#
# This file may be distributed under the terms of the GNU General
# Public License.
#
# LIC: GPL
# $Id: pppoe.conf,v 1.1.1.1 2007/02/22 22:46:50 kth5 Exp $
#***********************************************************************
# When you configure a variable, DO NOT leave spaces around the "=" sign.
# Ethernet card connected to DSL modem
ETH='eth0'
# PPPoE user name. You may have to supply "@provider.com" Sympatico
# users in Canada do need to include "@sympatico.ca"
# Sympatico uses PAP authentication. Make sure /etc/ppp/pap-secrets
# contains the right username/password combination.
# For Magma, use
xxyyzz@magma.ca
USER='<mein username>'
# Bring link up on demand? Default is to leave link up all the time.
# If you want the link to come up on demand, set DEMAND to a number indicating
# the idle time after which the link is brought down.
DEMAND=no
#DEMAND=300
# DNS type: SERVER=obtain from server; SPECIFY=use DNS1 and DNS2;
# NOCHANGE=do not adjust.
DNSTYPE=SERVER
# Obtain DNS server addresses from the peer (recent versions of pppd only)
# In old config files, this used to be called USEPEERDNS. Changed to
# PEERDNS for better Red Hat compatibility
PEERDNS=yes
DNS1=
DNS2=
# Make the PPPoE connection your default route. Set to
# DEFAULTROUTE=no if you don't want this.
DEFAULTROUTE=yes
### ONLY TOUCH THE FOLLOWING SETTINGS IF YOU'RE AN EXPERT
# How long pppoe-start waits for a new PPP interface to appear before
# concluding something went wrong. If you use 0, then pppoe-start
# exits immediately with a successful status and does not wait for the
# link to come up. Time is in seconds.
#
# WARNING WARNING WARNING:
#
# If you are using rp-pppoe on a physically-inaccessible host, set
# CONNECT_TIMEOUT to 0. This makes SURE that the machine keeps trying
# to connect forever after pppoe-start is called. Otherwise, it will
# give out after CONNECT_TIMEOUT seconds and will not attempt to
# connect again, making it impossible to reach.
CONNECT_TIMEOUT=30
# How often in seconds pppoe-start polls to check if link is up
CONNECT_POLL=2
# Specific desired AC Name
ACNAME=
# Specific desired service name
SERVICENAME=
# Character to echo at each poll. Use PING="" if you don't want
# anything echoed
PING="."
# File where the pppoe-connect script writes its process-ID.
# Three files are actually used:
# $PIDFILE contains PID of pppoe-connect script
# $PIDFILE.pppoe contains PID of pppoe process
# $PIDFILE.pppd contains PID of pppd process
CF_BASE=`basename $CONFIG`
PIDFILE="/var/run/$CF_BASE-pppoe.pid"
# Do you want to use synchronous PPP? "yes" or "no". "yes" is much
# easier on CPU usage, but may not work for you. It is safer to use
# "no", but you may want to experiment with "yes". "yes" is generally
# safe on Linux machines with the n_hdlc line discipline; unsafe on others.
SYNCHRONOUS=no
# Do you want to clamp the MSS? Here's how to decide:
# - If you have only a SINGLE computer connected to the DSL modem, choose
# "no".
# - If you have a computer acting as a gateway for a LAN, choose "1412".
# The setting of 1412 is safe for either setup, but uses slightly more
# CPU power.
CLAMPMSS=1412
#CLAMPMSS=no
# LCP echo interval and failure count.
LCP_INTERVAL=20
LCP_FAILURE=3
# PPPOE_TIMEOUT should be about 4*LCP_INTERVAL
PPPOE_TIMEOUT=80
# Firewalling: One of NONE, STANDALONE or MASQUERADE
FIREWALL=NONE
# Linux kernel-mode plugin for pppd. If you want to try the kernel-mode
# plugin, use LINUX_PLUGIN=/etc/ppp/plugins/rp-pppoe.so
LINUX_PLUGIN=
# Any extra arguments to pass to pppoe. Normally, use a blank string
# like this:
PPPOE_EXTRA=""
# Rumour has it that "Citizen's Communications" with a 3Com
# HomeConnect DSL Modem DualLink requires these extra options:
# PPPOE_EXTRA="-f 3c12:3c13 -S ISP"
# Any extra arguments to pass to pppd. Normally, use a blank string
# like this:
PPPD_EXTRA=""
########## DON'T CHANGE BELOW UNLESS YOU KNOW WHAT YOU ARE DOING
# If you wish to COMPLETELY overrride the pppd invocation:
# Example:
# OVERRIDE_PPPD_COMMAND="pppd call dsl"
# If you want pppoe-connect to exit when connection drops:
# RETRY_ON_FAILURE=no
- danach habe ich dann pppoe-start versucht das endete mit einem Timeout
Auf der Konsole nur Nachricht das Timeout war
/var/log/messages.log:
Apr 1 22:17:07 (none) PPP generic driver version 2.4.2
Apr 1 22:17:07 (none) pppd[4011]: pppd 2.4.4 started by root, uid 0
Apr 1 22:17:07 (none) pppd[4011]: Using interface ppp0
Apr 1 22:17:07 (none) pppd[4011]: Connect: ppp0 <--> /dev/pts/0
Apr 1 22:17:07 (none) pppoe[4012]: PPP session is 73 (0x49)
Apr 1 22:17:08 (none) pppd[4011]: Warning - secret file /etc/ppp/pap-secrets has world and/or group access
Apr 1 22:17:08 (none) pppd[4011]: Warning - secret file /etc/ppp/chap-secrets has world and/or group access
Apr 1 22:17:08 (none) pppd[4011]: CHAP authentication succeeded
Apr 1 22:17:08 (none) pppd[4011]: CHAP authentication succeeded
Apr 1 22:17:08 (none) PPP BSD Compression module registered
Apr 1 22:17:08 (none) pppd[4011]: local IP address 192.168.100.125
Apr 1 22:17:08 (none) pppd[4011]: remote IP address 192.168.200.1
Apr 1 22:17:08 (none) pppd[4011]: primary DNS address 192.168.0.1
Apr 1 22:17:08 (none) pppd[4011]: secondary DNS address 218.214.17.1
/var/log/errors.log:
Apr 1 22:17:08 (none) pppd[4011]: not replacing existing default route via 192.168.1.1
Apr 1 22:17:08 (none) pppd[4011]: Cannot determine ethernet address for proxy ARP
- danach habe ich dann händisch die route neugesetzt mit:
route del default
route add default dev ppp0
route -n (vorher):
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.200.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
route -n (hinterher):
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.200.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
- dann ping auf
www.heise.de:
PING
www.heise.de (193.99.144.85) 56(84) bytes of data.
64 bytes from
www.heise.de (193.99.144.85): icmp_seq=1 ttl=229 time=358 ms
64 bytes from
www.heise.de (193.99.144.85): icmp_seq=2 ttl=229 time=358 ms
64 bytes from
www.heise.de (193.99.144.85): icmp_seq=3 ttl=229 time=357 ms
---
www.heise.de ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 357.596/358.209/358.834/0.856 ms