[Solved] pppoe config question

Doctor Drive · 2012-01-18 10:59:17

On Windows OS when I setup the connection I have next attributes:

IP: 192.168.1.2
Mask: 255.255.255.0
Gateway: 192.168.1.1

DNS1: 213.130.16.3
DNS2: 213.130.16.20

Login: login
Password: pass

When I run pppoe-setup it asks me about login, pass, primary and secondary dns, about firewall stuff etc.
Then I add to /etc/resolv.conf

nameserver 213.130.16.3
nameserver 213.130.16.20

The interface should that should be registered is ppp0, right?
After that I run these

ifconfig ppp0 up
route del default
route add default ppp0

But what about the gateway, netmask and IP address?
There are no such parameters in /etc/pppoe/pppoe.conf.

Last edited by Doctor Drive (2012-01-19 16:46:47)

pyther · 2012-01-18 15:20:56

Unfortunately, I do not know much about pppoe configuration on Linux. However take a look at https://wiki.archlinux.org/index.php/PP … _with_pppd

Doctor Drive · 2012-01-18 16:23:58

Thx, but pppd is not included in the installation media. I have to use rp-pppoe

Last edited by Doctor Drive (2012-01-18 16:32:21)

pyther · 2012-01-18 16:51:12

I looked at the config and man pages a bit more.

Run pppoe-startup (it seems that you have). The interface should be the interface that has the ethernet cable connect from your modem to your computer (most likely eth0 unless if you have multiple NIC adapters on your computer).

Run pppoe-start

It seems like this will start the connection. It is my understanding that it will automatically acquire an IP address

Last edited by pyther (2012-01-18 16:52:02)

Gusar · 2012-01-18 16:54:14

rp-pppoe depends on ppp, so the media *does* have pppd. It's the way to go. You can also use rp-pppoe, it works too, it's just less efficient (though I doubt the difference is noticeable on modern computers). In which case simply run pppoe-setup, answer the questions, then run pppoe-start.

Doctor Drive · 2012-01-18 18:54:30

Gusar wrote:

rp-pppoe depends on ppp, so the media *does* have pppd. It's the way to go. You can also use rp-pppoe, it works too, it's just less efficient (though I doubt the difference is noticeable on modern computers). In which case simply run pppoe-setup, answer the questions, then run pppoe-start.

1) Sorry, I stupidly entered pacman -Q pppd instead of pacman -Q ppp.
2) I tried pppoe-setup then pppoe-start.

I created the /etc/pppoe-pppoe.conf (which I mentioned in first post) via pppoe-setup

Running pppoe-start times out. So I assumed that I have to enter some extra params (like ip, gateway and mask)

pyther · 2012-01-18 22:56:41

export DEBUG=1
pppoe-start

paste the output

Doctor Drive · 2012-01-19 15:33:44

pyther wrote:

export DEBUG=1
pppoe-start
paste the output

---------------------------------------------
* The following section contains information about your system
Thu Jan 19 19:28:10 EET 2012
Output of uname -a
Linux myhost 3.0-ARCH #1 SMP PREEMPT Wed Aug 17 21:55:57 CEST 2011 x86_64 Intel(R) Celeron(R) CPU 2.80GHz GenuineIntel GNU/Linux
---------------------------------------------
* The following section contains information about your network
* interfaces.  The one you chose for PPPoE should contain the words:
* 'UP' and 'RUNNING'.  If it does not, you probably have an Ethernet
* driver problem.
Output of ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:30:67:E4:16: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:17 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          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)

---------------------------------------------
* The following section contains information about kernel modules
* If the module for your Ethernet card is 'tulip', you might
* want to look for an updated version at http://www.scyld.com
Output of lsmod
Module                  Size  Used by
appletalk              26298  0 
ipx                    20363  0 
p8022                   1171  1 ipx
psnap                   1973  2 appletalk,ipx
llc                     3761  2 p8022,psnap
p8023                   1068  1 ipx
ipv6                  290407  14 
fuse                   67290  2 
nls_cp437               5921  1 
vfat                   10247  1 
fat                    49473  1 vfat
ppdev                   5774  0 
i915                  707307  1 
evdev                   9530  0 
drm_kms_helper         25409  1 i915
usb_storage            44263  1 
snd_hda_codec_via      55568  1 
usbhid                 35256  0 
pcspkr                  1819  0 
uas                     8088  0 
i2c_i801                8187  0 
hid                    81635  1 usbhid
sg                     25557  0 
drm                   183380  2 i915,drm_kms_helper
snd_hda_intel          22122  0 
iTCO_wdt               12717  0 
snd_hda_codec          77927  2 snd_hda_codec_via,snd_hda_intel
iTCO_vendor_support     1929  1 iTCO_wdt
snd_hwdep               6325  1 snd_hda_codec
parport_pc             31610  0 
snd_pcm                73856  2 snd_hda_intel,snd_hda_codec
parport                31375  2 ppdev,parport_pc
processor              24256  0 
i2c_algo_bit            5199  1 i915
i2c_core               20133  5 i915,drm_kms_helper,i2c_i801,drm,i2c_algo_bit
snd_timer              19416  1 snd_pcm
atl1c                  32528  0 
thermal                 7863  0 
snd                    57786  6 snd_hda_codec_via,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore               6146  1 snd
button                  4470  1 i915
video                  11228  1 i915
intel_agp              10904  1 i915
intel_gtt              14423  3 i915,intel_agp
snd_page_alloc          7121  2 snd_hda_intel,snd_pcm
ext4                  369556  1 
mbcache                 5817  1 ext4
jbd2                   71074  1 ext4
crc16                   1297  1 ext4
sr_mod                 14951  0 
cdrom                  36329  1 sr_mod
sd_mod                 28307  6 
pata_acpi               3376  0 
ata_piix               22005  3 
uhci_hcd               23084  0 
libata                173297  2 pata_acpi,ata_piix
ehci_hcd               39511  0 
scsi_mod              131482  6 usb_storage,uas,sg,sr_mod,sd_mod,libata
usbcore               142544  6 usb_storage,usbhid,uas,uhci_hcd,ehci_hcd
---------------------------------------------
* The following section lists your routing table.
* If you have an entry which starts with '0.0.0.0', you probably
* have defined a default route and gateway, and pppd will
* not create a default route using your ISP.  Try getting
* rid of this route.
Output of netstat -n -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
---------------------------------------------
Contents of /etc/resolv.conf
* The following section lists DNS setup.
* If you can browse by IP address, but not name, suspect
* a DNS problem.
# MADE-BY-RP-PPPOE
nameserver 213.130.16.3
nameserver 213.130.16.20
---------------------------------------------
* The following section lists /etc/ppp/options.
* You should have NOTHING in that file.
Contents of /etc/ppp/options
# /etc/ppp/options
# 
# Originally created by Jim Knoble <jmknoble@mercury.interpath.net>
# Modified for Debian by alvar Bray <alvar@meiko.co.uk>
# Modified for PPP Server setup by Christoph Lameter <clameter@debian.org>
# Modified for ArchLinux by Manolis Tzanidakis <manolis@archlinux.org>
#
# To quickly see what options are active in this file, use this command:
#   egrep -v '#|^ *$' /etc/ppp/options

# Specify which DNS Servers the incoming Win95 or WinNT Connection should use
# Two Servers can be remotely configured
# ms-dns 192.168.1.1
# ms-dns 192.168.1.2

# Specify which WINS Servers the incoming connection Win95 or WinNT should use
# ms-wins 192.168.1.50
# ms-wins 192.168.1.51

# Run the executable or shell command specified after pppd has
# terminated the link.  This script could, for example, issue commands
# to the modem to cause it to hang up if hardware modem control signals
# were not available.
#disconnect "chat -- \d+++\d\c OK ath0 OK"

# async character map -- 32-bit hex; each bit is a character
# that needs to be escaped for pppd to receive it.  0x00000001
# represents '\x01', and 0x80000000 represents '\x1f'.
asyncmap 0

# Require the peer to authenticate itself before allowing network
# packets to be sent or received.
# Please do not disable this setting. It is expected to be standard in
# future releases of pppd. Use the call option (see manpage) to disable
# authentication for specific peers.
auth

# Use hardware flow control (i.e. RTS/CTS) to control the flow of data
# on the serial port.
crtscts

# Use software flow control (i.e. XON/XOFF) to control the flow of data
# on the serial port.
#xonxoff

# Specifies that certain characters should be escaped on transmission
# (regardless of whether the peer requests them to be escaped with its
# async control character map).  The characters to be escaped are
# specified as a list of hex numbers separated by commas.  Note that
# almost any character can be specified for the escape option, unlike
# the asyncmap option which only allows control characters to be
# specified.  The characters which may not be escaped are those with hex
# values 0x20 - 0x3f or 0x5e.
#escape 11,13,ff

# Don't use the modem control lines.
#local

# Specifies that pppd should use a UUCP-style lock on the serial device
# to ensure exclusive access to the device.
lock

# Don't show the passwords when logging the contents of PAP packets.
# This is the default.
hide-password

# When logging the contents of PAP packets, this option causes pppd to
# show the password string in the log message.
#show-password

# Use the modem control lines.  On Ultrix, this option implies hardware
# flow control, as for the crtscts option.  (This option is not fully
# implemented.)
modem

# Set the MRU [Maximum Receive Unit] value to <n> for negotiation.  pppd
# will ask the peer to send packets of no more than <n> bytes. The
# minimum MRU value is 128.  The default MRU value is 1500.  A value of
# 296 is recommended for slow links (40 bytes for TCP/IP header + 256
# bytes of data).
#mru 542

# Set the interface netmask to <n>, a 32 bit netmask in "decimal dot"
# notation (e.g. 255.255.255.0).
#netmask 255.255.255.0

# Disables the default behaviour when no local IP address is specified,
# which is to determine (if possible) the local IP address from the
# hostname. With this option, the peer will have to supply the local IP
# address during IPCP negotiation (unless it specified explicitly on the
# command line or in an options file).
#noipdefault

# Enables the "passive" option in the LCP.  With this option, pppd will
# attempt to initiate a connection; if no reply is received from the
# peer, pppd will then just wait passively for a valid LCP packet from
# the peer (instead of exiting, as it does without this option).
#passive

# With this option, pppd will not transmit LCP packets to initiate a
# connection until a valid LCP packet is received from the peer (as for
# the "passive" option with old versions of pppd).
#silent

# Don't request or allow negotiation of any options for LCP and IPCP
# (use default values).
#-all

# Disable Address/Control compression negotiation (use default, i.e.
# address/control field disabled).
#-ac

# Disable asyncmap negotiation (use the default asyncmap, i.e. escape
# all control characters).
#-am

# Don't fork to become a background process (otherwise pppd will do so
# if a serial device is specified).
#-detach

# Disable IP address negotiation (with this option, the remote IP
# address must be specified with an option on the command line or in
# an options file).
#-ip

# Disable IPCP negotiation and IP communication. This option should
# only be required if the peer is buggy and gets confused by requests
# from pppd for IPCP negotiation.
#noip

# Disable magic number negotiation.  With this option, pppd cannot
# detect a looped-back line.
#-mn

# Disable MRU [Maximum Receive Unit] negotiation (use default, i.e.
# 1500).
#-mru

# Disable protocol field compression negotiation (use default, i.e.
# protocol field compression disabled).
#-pc

# Require the peer to authenticate itself using PAP.
#+pap

# Don't agree to authenticate using PAP.
#-pap

# Require the peer to authenticate itself using CHAP [Cryptographic
# Handshake Authentication Protocol] authentication.
#+chap

# Don't agree to authenticate using CHAP.
#-chap

# Disable negotiation of Van Jacobson style IP header compression (use
# default, i.e. no compression).
#-vj

# Increase debugging level (same as -d).  If this option is given, pppd
# will log the contents of all control packets sent or received in a
# readable form.  The packets are logged through syslog with facility
# daemon and level debug. This information can be directed to a file by
# setting up /etc/syslog.conf appropriately (see syslog.conf(5)).  (If
# pppd is compiled with extra debugging enabled, it will log messages
# using facility local2 instead of daemon).
#debug

# Append the domain name <d> to the local host name for authentication
# purposes.  For example, if gethostname() returns the name porsche,
# but the fully qualified domain name is porsche.Quotron.COM, you would
# use the domain option to set the domain name to Quotron.COM.
#domain <d>

# Enable debugging code in the kernel-level PPP driver.  The argument n
# is a number which is the sum of the following values: 1 to enable
# general debug messages, 2 to request that the contents of received
# packets be printed, and 4 to request that the contents of transmitted
# packets be printed.
#kdebug n

# Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer
# requests a smaller value via MRU negotiation, pppd will request that
# the kernel networking code send data packets of no more than n bytes
# through the PPP network interface.
#mtu <n>

# Set the name of the local system for authentication purposes to <n>.
# This is a privileged option. With this option, pppd will use lines in the
# secrets files which have <n> as the second field when looking for a
# secret to use in authenticating the peer. In addition, unless overridden
# with the user option, <n> will be used as the name to send to the peer
# when authenticating the local system to the peer. (Note that pppd does
# not append the domain name to <n>.)
#name <n>

# Enforce the use of the hostname as the name of the local system for
# authentication purposes (overrides the name option).
#usehostname

# Set the assumed name of the remote system for authentication purposes
# to <n>.
#remotename <n>

# Add an entry to this system's ARP [Address Resolution Protocol]
# table with the IP address of the peer and the Ethernet address of this
# system.
proxyarp

# Use the system password database for authenticating the peer using
# PAP. Note: mgetty already provides this option. If this is specified
# then dialin from users using a script under Linux to fire up ppp wont work.
# login

# If this option is given, pppd will send an LCP echo-request frame to the
# peer every n seconds. Normally the peer should respond to the echo-request
# by sending an echo-reply. This option can be used with the
# lcp-echo-failure option to detect that the peer is no longer connected.
lcp-echo-interval 30

# If this option is given, pppd will presume the peer to be dead if n
# LCP echo-requests are sent without receiving a valid LCP echo-reply.
# If this happens, pppd will terminate the connection.  Use of this
# option requires a non-zero value for the lcp-echo-interval parameter.
# This option can be used to enable pppd to terminate after the physical
# connection has been broken (e.g., the modem has hung up) in
# situations where no hardware modem control lines are available.
lcp-echo-failure 4

# Set the LCP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#lcp-restart <n>

# Set the maximum number of LCP terminate-request transmissions to <n>
# (default 3).
#lcp-max-terminate <n>

# Set the maximum number of LCP configure-request transmissions to <n>
# (default 10).
#lcp-max-configure <n>

# Set the maximum number of LCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#lcp-max-failure <n>

# Set the IPCP restart interval (retransmission timeout) to <n>
# seconds (default 3).
#ipcp-restart <n>

# Set the maximum number of IPCP terminate-request transmissions to <n>
# (default 3).
#ipcp-max-terminate <n>

# Set the maximum number of IPCP configure-request transmissions to <n>
# (default 10).
#ipcp-max-configure <n>

# Set the maximum number of IPCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#ipcp-max-failure <n>

# Set the PAP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#pap-restart <n>

# Set the maximum number of PAP authenticate-request transmissions to
# <n> (default 10).
#pap-max-authreq <n>

# Set the maximum time that pppd will wait for the peer to authenticate
# itself with PAP to <n> seconds (0 means no limit).
#pap-timeout <n>

# Set the CHAP restart interval (retransmission timeout for
# challenges) to <n> seconds (default 3).
#chap-restart <n>

# Set the maximum number of CHAP challenge transmissions to <n>
# (default 10).
#chap-max-challenge

# If this option is given, pppd will rechallenge the peer every <n>
# seconds.
#chap-interval <n>

# With this option, pppd will accept the peer's idea of our local IP
# address, even if the local IP address was specified in an option.
#ipcp-accept-local

# With this option, pppd will accept the peer's idea of its (remote) IP
# address, even if the remote IP address was specified in an option.
#ipcp-accept-remote

# Disable the IPXCP and IPX protocols.
# To let pppd pass IPX packets comment this out --- you'll probably also
# want to install ipxripd, and have the Internal IPX Network option enabled
# in your kernel.  /usr/doc/HOWTO/IPX-HOWTO.gz contains more info.
noipx

# Exit once a connection has been made and terminated. This is the default,
# unless the `persist' or `demand' option has been specified.
#nopersist

# Do not exit after a connection is terminated; instead try to reopen
# the connection.
#persist

# Terminate after n consecutive failed connection attempts.
# A value of 0 means no limit. The default value is 10.
#maxfail <n>

# Initiate the link only on demand, i.e. when data traffic is present. 
# With this option, the remote IP address must be specified by the user on
# the command line or in an options file.  Pppd will initially configure
# the interface and enable it for IP traffic without connecting to the peer. 
# When traffic is available, pppd will connect to the peer and perform
# negotiation, authentication, etc.  When this is completed, pppd will
# commence passing data packets (i.e., IP packets) across the link.
#demand

# Specifies that pppd should disconnect if the link is idle for <n> seconds.
# The link is idle when no data packets (i.e. IP packets) are being sent or
# received.  Note: it is not advisable to use this option with the persist
# option without the demand option.  If the active-filter option is given,
# data packets which are rejected by the specified activity filter also
# count as the link being idle.
#idle <n>

# Specifies how many seconds to wait before re-initiating the link after
# it terminates.  This option only has any effect if the persist or demand
# option is used.  The holdoff period is not applied if the link was
# terminated because it was idle.
#holdoff <n>

# Wait for up n milliseconds after the connect script finishes for a valid
# PPP packet from the peer.  At the end of this time, or when a valid PPP
# packet is received from the peer, pppd will commence negotiation by
# sending its first LCP packet.  The default value is 1000 (1 second).
# This wait period only applies if the connect or pty option is used.
#connect-delay <n>

# Packet filtering: for more information, see pppd(8)
# Any packets matching the filter expression will be interpreted as link
# activity, and will cause a "demand" connection to be activated, and reset
# the idle connection timer. (idle option)
# The filter expression is akin to that of tcpdump(1)
#active-filter <filter-expression>

# uncomment the line below this if you use PPPoE
#plugin /usr/lib/pppd/plugins/pppoe.so

# ---<End of File>---
---------------------------------------------
* The following section identifies your Ethernet interface
* and user name.  Some ISP's need 'username'; others
* need 'username@isp.com'.  Try both
ETH=eth0; USER=serbin
---------------------------------------------
* The following section shows the pppd command we will invoke
pppd invocation
/usr/bin/setsid /usr/sbin/pppd pty '/usr/sbin/pppoe -p /var/run/pppoe.conf-pppoe.pid.pppoe -I eth0 -T 80 -U  -m 1412   '  noipdefault noauth default-asyncmap defaultroute hide-password nodetach  mtu 1492 mru 1492 noaccomp nodeflate nopcomp novj novjccomp user serbin lcp-echo-interval 20 lcp-echo-failure 3   debug
---------------------------------------------
using channel 1
Using interface ppp0
Connect: ppp0 <--> /dev/pts/0
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0xf5bd490b>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0xf5bd490b>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0xf5bd490b>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0xf5bd490b>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0xf5bd490b>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0xf5bd490b>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0xf5bd490b>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0xf5bd490b>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0xf5bd490b>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0xf5bd490b>]
LCP: timeout sending Config-Requests
Connection terminated.
Modem hangup
Waiting for 1 child processes...
  script /usr/sbin/pppoe -p /var/run/pppoe.conf-pppoe.pid.pppoe -I eth0 -T 80 -U  -m 1412    -D /tmp/pppoe-debug-674/pppoe-debug.txt-0, pid 744
pppoe: Timeout waiting for PADO packets
Script /usr/sbin/pppoe -p /var/run/pppoe.conf-pppoe.pid.pppoe -I eth0 -T 80 -U  -m 1412    -D /tmp/pppoe-debug-674/pppoe-debug.txt-0 finished (pid 744), status = 0x1
---------------------------------------------
* The following section is an extract from your log.
* Look for error messages from pppd, such as
* a lack of kernel support for PPP, authentication failure
* etc.
Can't find messages file (looked for /var/{log,adm}/messages
Thu Jan 19 19:28:45 EET 2012
---------------------------------------------
* The following section is a dump of the packets
* sent and received by rp-pppoe.  If you don't see
* any output, it's an Ethernet driver problem.  If you only
* see three PADI packets and nothing else, check your cables
* and modem.  Make sure the modem lights flash when you try
* to connect.  Check that your Ethernet card is in
* half-duplex, 10Mb/s mode.  If all else fails,
* try using pppoe-sniff.
rp-pppoe debugging dump
rp-pppoe-3.10
19:28:10.635 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr 00:30:67:e4:16:8b DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 e8 02 00 00               ............

19:28:15.641 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr 00:30:67:e4:16:8b DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 e8 02 00 00               ............

19:28:25.651 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr 00:30:67:e4:16:8b DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 e8 02 00 00               ............

pyther · 2012-01-19 15:49:03

Taking a quick glance, it seems as if your machine is sending pppoe discovery requests, but it is not receiving any responses. It is odd that you would be using an address in the 192.168.*.* range with pppoe.

Have you tried dhcp?

dhcpcd eth0

Last edited by pyther (2012-01-19 15:49:25)

Doctor Drive · 2012-01-19 16:07:29

pyther wrote:

Taking a quick glance, it seems as if your machine is sending pppoe discovery requests, but it is not receiving any responses. It is odd that you would be using an address in the 192.168.*.* range with pppoe.
Have you tried dhcp?
dhcpcd eth0

version 5.1.2 starting
eth0: acknowleged 192.168.1.2
eth0: checking for 192.168.1.2 from 192.168.1.1
eth0: checking for 192.168.1.2
eth0: leased 192.168.1.2 for 86400 seconds
forked to background, child pid 777

Also, about pppd method, I created /etc/ppp/peers/provider file

# /etc/ppp/peers/provider
 
plugin rp-pppoe.so
rp_pppoe_ac LOGIN

eth0
name LOGIN
usepeerdns
persist
defaultroute
hide-password
noauth

running pon gives the output

pon
Plugin rp-pppoe.so loaded
RP_PPPoE plugin version 3.8p compiled against pppd 2.4.5

Maybe it is badly described in the wik but I don't see here also where to put IP, gateway, mask, dns1 and dns2

Last edited by Doctor Drive (2012-01-19 16:09:30)

pyther · 2012-01-19 16:11:36

Your modem is giving you an ip address via DHCP. You don't need configure pppoe on your machine. After issuing dhcp, you should have a net connection.

Doctor Drive · 2012-01-19 16:46:33

pyther wrote:

Your modem is giving you an ip address via DHCP. You don't need configure pppoe on your machine. After issuing dhcp, you should have a net connection.

Thanks. I did not know that adsl could get up via dhcp.

Gusar · 2012-01-19 17:24:23

Doctor Drive wrote:

Thanks. I did not know that adsl could get up via dhcp.

From what I know, it can't. It's your modem that's doing all the ADSL work, then sharing that connection to a LAN. 192.168.x.x are internal IPs.

Last edited by Gusar (2012-01-19 17:24:49)

pyther · 2012-01-19 21:10:03

Gusar wrote:

From what I know, it can't. It's your modem that's doing all the ADSL work, then sharing that connection to a LAN. 192.168.x.x are internal IPs.

This is, more than less, correct. Basically the modem is taking care of the authentication. You could put the modem in bridge mode and then you would have to use pppoe on a client device (router or your machine). If you don't have a router in the picture, I would strongly suggest setting up a firewall.

Doctor Drive · 2012-01-20 10:00:00

Thank you for help.

Arch Linux

#1 2012-01-18 10:59:17

[Solved] pppoe config question

#2 2012-01-18 15:20:56

Re: [Solved] pppoe config question

#3 2012-01-18 16:23:58

Re: [Solved] pppoe config question

#4 2012-01-18 16:51:12

Re: [Solved] pppoe config question

#5 2012-01-18 16:54:14

Re: [Solved] pppoe config question

#6 2012-01-18 18:54:30

Re: [Solved] pppoe config question

#7 2012-01-18 22:56:41

Re: [Solved] pppoe config question

#8 2012-01-19 15:33:44

Re: [Solved] pppoe config question

#9 2012-01-19 15:49:03

Re: [Solved] pppoe config question

#10 2012-01-19 16:07:29

Re: [Solved] pppoe config question

#11 2012-01-19 16:11:36

Re: [Solved] pppoe config question

#12 2012-01-19 16:46:33

Re: [Solved] pppoe config question

#13 2012-01-19 17:24:23

Re: [Solved] pppoe config question

#14 2012-01-19 21:10:03

Re: [Solved] pppoe config question

#15 2012-01-20 10:00:00

Re: [Solved] pppoe config question

Board footer