1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

PPPoE doesnt work

Discussion in 'Tomato Firmware' started by famols, Feb 15, 2010.

  1. famols

    famols Addicted to LI Member

    Hello,
    I have two Routers in my Network:
    a Sphairon Modem/Router with RouterTech FW (http://www.routertech.org/)
    and a Linksys WRT54G with Tomato FW.

    Currently I use the Sphairon as Modem and Router and the Linksys as a 2nd router in "downstream".

    Actually I want to configure the Sphairon only as a modem and use the Linksys as the only router.
    However I failed to achieve this so far (now we come to the point).

    1. Configure Sphairon in modem-mode, check
    2. check DSL-Link, ok
    3. Configure Tomato for PPPoE:
    Basic -> Network: WAN/Internet
    Type: PPPoE
    Username: same as in sphairon before
    Password: dito
    Service Name: {empty} <- what is this for?
    MTU: default
    4. Establish Internet connection, fail

    I also tried it with another (pure) modem, but it also didn't work.

    Am I missing something? Is there another setting, anything else I could try?

    Thanks so far
    famols
     
  2. Beast

    Beast Network Guru Member

    Hi

    Some service providers use your PC MAC address in your account. Go to advance settings under MAC ADDRESS and clone your PC MAC address to the WAN Port.

    As for the service name, some providers require it, but that should be evident in your setup as router on the modem. If you did not use it there, then it should not be needed on the router.
     
  3. famols

    famols Addicted to LI Member

    Hi Beast,
    thanks or your reply.
    I didn't used that before, so this is definitely not the problem (the Sphairon is not from the service provider).

    In the Sphairon is no field for the service name, so I guess an empty field in the tomato should work?

    Any other ideas?
     
  4. Disman_ca

    Disman_ca Super Moderator Staff Member Member

    Service name shouldn't matter but you could enter something in there to see if it helps. Have you considered keeping it setup as a router and configuring your Linksys in a different subnet like 192.168.2.xxx? If you do try this only connect 1 cable form your Sphairon to the WAN link of the Linksys. Also disable any firewall on the Sphairon to avoid double NAT problems for clients connected to the Linksys.
     
  5. Disman_ca

    Disman_ca Super Moderator Staff Member Member

    I forgot to tell you to enable logging on the Linksys with all options to see if the log tells you anything.
     
  6. famols

    famols Addicted to LI Member

    Ah, obviously I didn't make myself clear here, that IS in fact my current setup (thats what I meant with "downstream"). But I don't think it is an elegant solution and by turning of all firewall settings, I'm afraid to make the Sphairon itself prone to attacks.

    Ah, thats a good idea! I just enabled them and will do some testings this week and come back with the logs.

    Thanks!
     
  7. famols

    famols Addicted to LI Member

    Hi,
    here is the log, I hope you can evaluate it (I can't) ...

    TIA
    famols

    Code:
    Jan  1 01:00:10 Linksys_tomato_host user.info kernel: Freeing unused kernel memory: 64k freed
    Jan  1 01:00:10 Linksys_tomato_host user.warn kernel: Algorithmics/MIPS FPU Emulator v1.5
    Jan  1 01:00:10 Linksys_tomato_host user.warn kernel: ip_conntrack_pptp version 1.9 loaded
    Jan  1 01:00:10 Linksys_tomato_host user.warn kernel: ip_nat_pptp version 1.5 loaded
    Jan  1 01:00:10 Linksys_tomato_host user.warn kernel: ip_conntrack_rtsp v0.01 loading
    Jan  1 01:00:10 Linksys_tomato_host user.warn kernel: ip_nat_rtsp v0.01 loading
    Jan  1 01:00:10 Linksys_tomato_host user.warn kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.38.0
    Jan  1 01:00:10 Linksys_tomato_host user.warn kernel: eth1: Broadcom BCM4320 802.11 Wireless Controller 3.90.38.0
    Jan  1 01:00:10 Linksys_tomato_host user.warn kernel: tomato_ct.c [Nov 29 2009 06:54:59]
    Jan  1 01:00:10 Linksys_tomato_host user.info kernel: vlan0: dev_set_promiscuity(master, 1)
    Jan  1 01:00:10 Linksys_tomato_host user.info kernel: device eth0 entered promiscuous mode
    Jan  1 01:00:10 Linksys_tomato_host user.info kernel: device vlan0 entered promiscuous mode
    Jan  1 01:00:10 Linksys_tomato_host user.info kernel: device eth1 entered promiscuous mode
    Jan  1 01:00:10 Linksys_tomato_host user.info kernel: br0: port 2(eth1) entering learning state
    Jan  1 01:00:10 Linksys_tomato_host user.info kernel: br0: port 1(vlan0) entering learning state
    Jan  1 01:00:10 Linksys_tomato_host user.warn kernel: vlan1: Setting MAC address to  00 25 9c 43 bc b0.
    Jan  1 01:00:10 Linksys_tomato_host user.info kernel: br0: port 2(eth1) entering forwarding state
    Jan  1 01:00:10 Linksys_tomato_host user.info kernel: br0: topology change detected, propagating
    Jan  1 01:00:10 Linksys_tomato_host user.info kernel: br0: port 1(vlan0) entering forwarding state
    Jan  1 01:00:10 Linksys_tomato_host user.info kernel: br0: topology change detected, propagating
    Jan  1 01:00:11 Linksys_tomato_host daemon.info dnsmasq[109]: started, version 2.51 cachesize 150
    Jan  1 01:00:11 Linksys_tomato_host daemon.info dnsmasq[109]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP no-scripts no-TFTP
    Jan  1 01:00:11 Linksys_tomato_host daemon.info dnsmasq-dhcp[109]: DHCP, IP range 192.168.22.31 -- 192.168.22.99, lease time 1d
    Jan  1 01:00:11 Linksys_tomato_host daemon.info dnsmasq[109]: reading /etc/resolv.dnsmasq
    Jan  1 01:00:11 Linksys_tomato_host daemon.info dnsmasq[109]: using nameserver 1.1.1.1#53
    Jan  1 01:00:11 Linksys_tomato_host daemon.info dnsmasq[109]: read /etc/hosts - 0 addresses
    Jan  1 01:00:11 Linksys_tomato_host daemon.info dnsmasq[109]: read /etc/hosts.dnsmasq - 7 addresses
    Jan  1 01:00:11 Linksys_tomato_host user.info init[1]: Tomato 1.27.1798
    Jan  1 01:00:11 Linksys_tomato_host daemon.info pppoe[64]: Sending PADI.
    Jan  1 01:00:11 Linksys_tomato_host cron.err crond[113]: crond (busybox 1.14.4) started, log level 9
    Jan  1 01:00:11 Linksys_tomato_host user.info init[1]: Linksys WRT54G/GS/GL
    Jan  1 01:00:11 Linksys_tomato_host daemon.info pppoe[64]: Received PADO.
    Jan  1 01:00:11 Linksys_tomato_host daemon.info pppoe[64]: Sending PADR.
    Jan  1 01:00:11 Linksys_tomato_host daemon.info pppoe[64]: Received PADS. SID: 0xCE14
    Jan  1 01:00:11 Linksys_tomato_host daemon.info pppoe[64]: Sending LCP Configuration-Request
    Jan  1 01:00:11 Linksys_tomato_host daemon.info pppoe[64]: Received LCP Configuration-Request
    Jan  1 01:00:11 Linksys_tomato_host daemon.info pppoe[64]: Sending LCP Configuration-Reject
    Jan  1 01:00:11 Linksys_tomato_host daemon.info pppoe[64]: Received LCP Configuration-Ack
    Jan  1 01:00:11 Linksys_tomato_host daemon.info pppoe[64]: Received LCP Configuration-Request
    Jan  1 01:00:11 Linksys_tomato_host daemon.info pppoe[64]: Sending LCP Configuration-Ack
    Jan  1 01:00:11 Linksys_tomato_host daemon.info pppoe[64]: Sending IPCP Configuration-Request
    Jan  1 01:00:11 Linksys_tomato_host daemon.info pppoe[64]: Received LCP Termination-Request
    Jan  1 01:00:11 Linksys_tomato_host daemon.info pppoe[64]: Sending LCP Termination-Ack
    Jan  1 01:00:14 Linksys_tomato_host user.info kernel: vlan1: add 01:00:5e:00:00:01 mcast address to master interface
    Jan  1 01:00:14 Linksys_tomato_host daemon.info pppoe[64]: Connection terminated.
    Jan  1 01:00:14 Linksys_tomato_host daemon.notice pppoe[64]: Disconnected.
    Jan  1 01:00:14 Linksys_tomato_host daemon.info pppoe[64]: Sending PADT.
    Jan  1 01:00:26 Linksys_tomato_host daemon.info pppoe[64]: Sending PADI.
    Jan  1 01:00:26 Linksys_tomato_host daemon.info pppoe[64]: Received PADT for 0xCE14, expecting 0x0000
    Jan  1 01:00:26 Linksys_tomato_host daemon.info pppoe[64]: Received PADO.
    Jan  1 01:00:26 Linksys_tomato_host daemon.info pppoe[64]: Sending PADR.
    Jan  1 01:00:26 Linksys_tomato_host daemon.info pppoe[64]: Received PADS. SID: 0xD414
    Jan  1 01:00:26 Linksys_tomato_host daemon.info pppoe[64]: Sending LCP Configuration-Request
    Jan  1 01:00:27 Linksys_tomato_host daemon.info pppoe[64]: Received LCP Configuration-Request
    Jan  1 01:00:27 Linksys_tomato_host daemon.info pppoe[64]: Sending LCP Configuration-Reject
    Jan  1 01:00:27 Linksys_tomato_host daemon.info pppoe[64]: Received LCP Configuration-Ack
    Jan  1 01:00:27 Linksys_tomato_host daemon.info pppoe[64]: Received LCP Configuration-Request
    Jan  1 01:00:27 Linksys_tomato_host daemon.info pppoe[64]: Sending LCP Configuration-Ack
    Jan  1 01:00:27 Linksys_tomato_host daemon.info pppoe[64]: Sending IPCP Configuration-Request
    Jan  1 01:00:27 Linksys_tomato_host daemon.info pppoe[64]: Received LCP Termination-Request
    Jan  1 01:00:27 Linksys_tomato_host daemon.info pppoe[64]: Sending LCP Termination-Ack
    Jan  1 01:00:30 Linksys_tomato_host daemon.info pppoe[64]: Connection terminated.
    Jan  1 01:00:30 Linksys_tomato_host daemon.notice pppoe[64]: Disconnected.
    Jan  1 01:00:30 Linksys_tomato_host daemon.info pppoe[64]: Sending PADT.
    Jan  1 01:00:41 Linksys_tomato_host daemon.info pppoe[64]: Sending PADI.
    Jan  1 01:00:41 Linksys_tomato_host daemon.info pppoe[64]: Received PADT for 0xD414, expecting 0x0000
    Jan  1 01:00:43 Linksys_tomato_host daemon.info dnsmasq[109]: exiting on receipt of SIGTERM
    Jan  1 01:00:45 Linksys_tomato_host daemon.info dnsmasq[134]: started, version 2.51 cachesize 150
    Jan  1 01:00:45 Linksys_tomato_host daemon.info dnsmasq[134]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP no-scripts no-TFTP
    Jan  1 01:00:45 Linksys_tomato_host daemon.info dnsmasq-dhcp[134]: DHCP, IP range 192.168.22.31 -- 192.168.22.99, lease time 1d
    Jan  1 01:00:45 Linksys_tomato_host daemon.info pppoe[136]: Starting
    Jan  1 01:00:45 Linksys_tomato_host daemon.warn dnsmasq[134]: no servers found in /etc/resolv.dnsmasq, will retry
    Jan  1 01:00:45 Linksys_tomato_host daemon.info dnsmasq[134]: read /etc/hosts - 0 addresses
    Jan  1 01:00:45 Linksys_tomato_host daemon.info dnsmasq[134]: read /etc/hosts.dnsmasq - 7 addresses
    Jan  1 01:00:46 Linksys_tomato_host daemon.info dnsmasq[134]: exiting on receipt of SIGTERM
    Jan  1 01:00:46 Linksys_tomato_host daemon.info dnsmasq[141]: started, version 2.51 cachesize 150
    Jan  1 01:00:46 Linksys_tomato_host daemon.info dnsmasq[141]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP no-scripts no-TFTP
    Jan  1 01:00:46 Linksys_tomato_host daemon.info dnsmasq-dhcp[141]: DHCP, IP range 192.168.22.31 -- 192.168.22.99, lease time 1d
    Jan  1 01:00:46 Linksys_tomato_host daemon.info dnsmasq[141]: reading /etc/resolv.dnsmasq
    Jan  1 01:00:46 Linksys_tomato_host daemon.info dnsmasq[141]: using nameserver 1.1.1.1#53
    Jan  1 01:00:46 Linksys_tomato_host daemon.info dnsmasq[141]: read /etc/hosts - 0 addresses
    Jan  1 01:00:46 Linksys_tomato_host daemon.info dnsmasq[141]: read /etc/hosts.dnsmasq - 7 addresses
    Jan  1 01:00:48 Linksys_tomato_host daemon.notice miniupnpd[92]: received signal 15, good-bye
    Jan  1 01:00:48 Linksys_tomato_host daemon.info pppoe[136]: Sending PADI.
    Jan  1 01:00:48 Linksys_tomato_host daemon.notice miniupnpd[165]: HTTP listening on port 5000
    Jan  1 01:00:48 Linksys_tomato_host daemon.info pppoe[136]: Received PADO.
    Jan  1 01:00:48 Linksys_tomato_host daemon.info pppoe[136]: Sending PADR.
    Jan  1 01:00:48 Linksys_tomato_host daemon.info pppoe[136]: Received PADS. SID: 0xD914
    Jan  1 01:00:48 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Request
    Jan  1 01:00:49 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Request
    Jan  1 01:00:49 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Reject
    Jan  1 01:00:49 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Ack
    Jan  1 01:00:49 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Request
    Jan  1 01:00:49 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Ack
    Jan  1 01:00:49 Linksys_tomato_host daemon.info pppoe[136]: Sending IPCP Configuration-Request
    Jan  1 01:00:49 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Termination-Request
    Jan  1 01:00:49 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Termination-Ack
    Jan  1 01:00:52 Linksys_tomato_host daemon.info pppoe[136]: Connection terminated.
    Jan  1 01:00:52 Linksys_tomato_host daemon.notice pppoe[136]: Disconnected.
    Jan  1 01:00:52 Linksys_tomato_host daemon.info pppoe[136]: Sending PADT.
    Jan  1 01:01:08 Linksys_tomato_host daemon.info pppoe[136]: Sending PADI.
    Jan  1 01:01:08 Linksys_tomato_host daemon.info pppoe[136]: Received PADT for 0xD914, expecting 0x0000
    Jan  1 01:01:18 Linksys_tomato_host daemon.info pppoe[136]: Resending...
    Jan  1 01:01:28 Linksys_tomato_host daemon.info pppoe[136]: Resending...
    Jan  1 01:01:28 Linksys_tomato_host daemon.info pppoe[136]: Received PADO.
    Jan  1 01:01:28 Linksys_tomato_host daemon.info pppoe[136]: Sending PADR.
    Jan  1 01:01:28 Linksys_tomato_host daemon.info pppoe[136]: Received PADS. SID: 0xE314
    Jan  1 01:01:28 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Request
    Jan  1 01:01:29 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Request
    Jan  1 01:01:29 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Reject
    Jan  1 01:01:29 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Ack
    Jan  1 01:01:29 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Request
    Jan  1 01:01:29 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Ack
    Jan  1 01:01:29 Linksys_tomato_host daemon.info pppoe[136]: Sending IPCP Configuration-Request
    Jan  1 01:01:29 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Termination-Request
    Jan  1 01:01:29 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Termination-Ack
    Jan  1 01:01:32 Linksys_tomato_host daemon.info pppoe[136]: Connection terminated.
    Jan  1 01:01:32 Linksys_tomato_host daemon.notice pppoe[136]: Disconnected.
    Jan  1 01:01:32 Linksys_tomato_host daemon.info pppoe[136]: Sending PADT.
    Jan  1 01:01:48 Linksys_tomato_host daemon.info pppoe[136]: Sending PADI.
    Jan  1 01:01:48 Linksys_tomato_host daemon.info pppoe[136]: Received PADT for 0xE314, expecting 0x0000
    Jan  1 01:01:58 Linksys_tomato_host daemon.info pppoe[136]: Resending...
    Jan  1 01:02:08 Linksys_tomato_host daemon.info pppoe[136]: Resending...
    Jan  1 01:02:18 Linksys_tomato_host daemon.info pppoe[136]: Resending...
    Jan  1 01:02:28 Linksys_tomato_host daemon.info pppoe[136]: Resending...
    Jan  1 01:02:39 Linksys_tomato_host daemon.info pppoe[136]: Sending PADI.
    Jan  1 01:02:39 Linksys_tomato_host daemon.info pppoe[136]: Received PADO.
    Jan  1 01:02:39 Linksys_tomato_host daemon.info pppoe[136]: Sending PADR.
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received PADS. SID: 0xF914
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Request
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Request
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Reject
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Ack
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Request
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Ack
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending IPCP Configuration-Request
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Termination-Request
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Termination-Ack
    Jan  1 01:02:43 Linksys_tomato_host daemon.info pppoe[136]: Connection terminated.
    Jan  1 01:02:43 Linksys_tomato_host daemon.notice pppoe[136]: Disconnected.
    Jan  1 01:02:43 Linksys_tomato_host daemon.info pppoe[136]: Sending PADT.
     
  8. Disman_ca

    Disman_ca Super Moderator Staff Member Member

    Code:
    Jan  1 01:01:32 Linksys_tomato_host daemon.notice pppoe[136]: Disconnected.
    Jan  1 01:01:32 Linksys_tomato_host daemon.info pppoe[136]: Sending PADT.
    Jan  1 01:01:48 Linksys_tomato_host daemon.info pppoe[136]: Sending PADI.
    Jan  1 01:01:48 Linksys_tomato_host daemon.info pppoe[136]: Received PADT for 0xE314, expecting 0x0000
    Jan  1 01:01:58 Linksys_tomato_host daemon.info pppoe[136]: Resending...
    Jan  1 01:02:08 Linksys_tomato_host daemon.info pppoe[136]: Resending...
    Jan  1 01:02:18 Linksys_tomato_host daemon.info pppoe[136]: Resending...
    Jan  1 01:02:28 Linksys_tomato_host daemon.info pppoe[136]: Resending...
    Jan  1 01:02:39 Linksys_tomato_host daemon.info pppoe[136]: Sending PADI.
    Jan  1 01:02:39 Linksys_tomato_host daemon.info pppoe[136]: Received PADO.
    Jan  1 01:02:39 Linksys_tomato_host daemon.info pppoe[136]: Sending PADR.
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received PADS. SID: 0xF914
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Request
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Request
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Reject
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Ack
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Request
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Ack
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending IPCP Configuration-Request
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Termination-Request
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Termination-Ack
    Jan  1 01:02:43 Linksys_tomato_host daemon.info pppoe[136]: Connection terminated.
    Jan  1 01:02:43 Linksys_tomato_host daemon.notice pppoe[136]: Disconnected.
    I'm not really familiar with PPoE connection but this is certainly showing the connection is not being established. It looks like it can't netgotiate configuration options for LCP. Maybe that service field needs something in there to assist it.
     
  9. famols

    famols Addicted to LI Member

    Ok, thanks.
    What does LCP mean?

    Could this also possibly be from a wrong setup in the Sphairon or does this mean the setup of the Linksys and Sphairon are correct (so far)?
     
  10. arafey

    arafey Addicted to LI Member

    LCP (link control protocol) is the main component of PPPoE connections and basically controls your pppoe connection (it starts it, controls it and can close it.). Based on your log, it seems that your end and the other end of the connection are not agreeing.

    See, this is the problematic part of yours:
    Code:
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Request
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Request
    [B]Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Reject[/B]
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Ack
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Configuration-Request
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Configuration-Ack
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending IPCP Configuration-Request
    [B]Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Received LCP Termination-Request
    Jan  1 01:02:40 Linksys_tomato_host daemon.info pppoe[136]: Sending LCP Termination-Ack[/B]
    Jan  1 01:02:43 Linksys_tomato_host daemon.info pppoe[136]: Connection terminated.
    Jan  1 01:02:43 Linksys_tomato_host daemon.notice pppoe[136]: Disconnected.

    A healthy PPPoE connection attempt should look like this:

    Code:
    192.168.1.1	12/31/10 19:00:15	02/16/10 12:32:28		system	Info	pppoe[43]		"Received LCP Configuration-Ack"
    192.168.1.1	12/31/10 19:00:15	02/16/10 12:32:28		system	Info	pppoe[43]		"Sending LCP Configuration-Ack"
    192.168.1.1	12/31/10 19:00:15	02/16/10 12:32:28		system	Info	pppoe[43]		"Received LCP Configuration-Request"
    192.168.1.1	12/31/10 19:00:15	02/16/10 12:32:28		system	Info	pppoe[43]		"Sending LCP Configuration-Request"
    192.168.1.1	12/31/10 19:00:15	02/16/10 12:32:28		system	Info	pppoe[43]		"Received PADS. SID: 0x1503"
    192.168.1.1	12/31/10 19:00:15	02/16/10 12:32:28		system	Info	pppoe[43]		"Sending PADR."
    192.168.1.1	12/31/10 19:00:15	02/16/10 12:32:28		system	Info	pppoe[43]		"Received PADO."
    192.168.1.1	12/31/10 19:00:15	02/16/10 12:32:28		system	Info	pppoe[43]		"Sending PADI."
    192.168.1.1	12/31/10 19:00:49	02/16/10 02:57:49		system	Info	pppoe[43]		"Received IPCP Configuration-Ack"
    192.168.1.1	12/31/10 19:00:50	02/16/10 02:57:49		system	Notice	pppoe[43]		"DNS Address: x.x.x.x(dnsr-1)"
    192.168.1.1	12/31/10 19:00:50	02/16/10 02:57:49		system	Notice	pppoe[43]		"IP Address: y.y.y.y(y-y-y-y)"
    192.168.1.1	12/31/10 19:00:50	02/16/10 02:57:49		system	Notice	pppoe[43]		"Connected."
    
    Based on the bolded portions of your log, it looks like between you and the connection gateway, there are some configuration differences. I don't think it is your username/password but you should double check, and DSL (your connection type, right?) doesn't usually care about MAC addresses. So it is probably on the modem end that something is wrong, rather than your linksys router's end.


    EDIT: For more info on LCP, go here: http://www.tcpipguide.com/free/t_PPPLinkControlProtocolLCP.htm

    As you can see from the picture on that page, you are making a connection to the connection gateway but encounter problems while the router and "other end" are negotiating.
     
  11. famols

    famols Addicted to LI Member

    Hello arafey,
    thanks for the information.
    Yes, my connection type is DSL, more precisely ADSL 2+.

    So I guess I have to check the settings in the sphairon again...

    Also besides the Basic -> Network: WAN/Internet, Type: PPPoE Settings there is nothing else to setup/configure for PPPoE in tomato?

    Another side note:
    In order to access&configure the sphairon in modem mode, I configured the following scripts in the tomato (someone at the RT-Forum provided them):
    in Init:
    Code:
    sleep 10
    ifconfig vlan1:0 192.168.1.2
    in Firewall:
    Code:
    iptables -t nat -I POSTROUTING -o vlan1 -d 192.168.1.1 -j MASQUERADE
    Just to check this shouldn't make any problems? (At first I tried without the scripts and it didn't work as well, but you never know...)

    TIA
    famols
     
  12. Beast

    Beast Network Guru Member

    Hi
    Since it looks like when you setup ppoe on the linksys there is a protcol config error, i just want give you this info. It may or may not be of use.

    I don't know anything about the sphairon, but on my speedstream DSL modem there are actually three ways to configure it.

    1. PPoe and router function on modem
    2. Bridged mode---- ppoe on router or pc
    3. Bridged mode---- no ppoe used

    Initially the modem must be set up to use the proper protocol, which i did. And i used option number 1. But later i shifted ppoe to the linksys as you are trying to do. Now i use option 2. And im assuming the modem still retains the protocol settings.

    Do you have similar options in your modem, perhaps your present choice may be the same as option 3 on mine?

    Just a thought......
     
  13. myersw

    myersw Network Guru Member

    You beat me Beast. If you are trying to have the Linksys to control the PPoE then the modem needs to be in bridged mode. So in Beast's example option 2 would be what needs to be used. --bill
     
  14. famols

    famols Addicted to LI Member

    I must say I have the strange feeling, that it is really something stupid that I'm missing. Probably something like Beast mentioned - unfortunately there are no such obvious option labeled, but I keep looking...

    Thanks
     
  15. parrapanos

    parrapanos Guest

    have the same problem

    I am going to try things i red in this forum. Does anyone solved it for sure?
     

Share This Page