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

PPPoE Help

Discussion in 'Tomato Firmware' started by moffa, Jan 31, 2013.

  1. moffa

    moffa Serious Server Member

    I am using Shibby v105 on an E3200. I am currently trying to setup my VDSL but it just doesn't work. It keeps getting a WAN IP address of 192.168.1.1. I've flashed back to the OEM firmware and it works fine. The overview page shows it as connected (with the 192.168.1.1 ip) and there is no internet connection.

    I've checked the PPPoE username/password multiple times, it's correct. Even tried leaving it when flashing from the Linksys software.

    Your help is appreciated.
     
  2. moffa

    moffa Serious Server Member

    I tried dd-wrt and it works as well. I'm not sure what the issue is. I could use some help debugging.
     
  3. Porter

    Porter LI Guru Member

    Please use the search in this forum or google. Via Google you can find some guides for Tomato.
     
  4. moffa

    moffa Serious Server Member

    I've tried searching, and it's not really complicated so I'm not sure why it isn't working
     
  5. gfunkdave

    gfunkdave LI Guru Member

    Sounds like your DSL modem is not in bridge mode.
     
  6. moffa

    moffa Serious Server Member

    I know it sounds like bridge mode, but the IP address is always the local IP address. I've tried 192.168.3,5,10,etc.1 and it always uses that IP. When the modem is in router mode, it gives a 192.168.2.x IP instead. Is anyone using Bell Canada VDSL and have Tomato working? I'm really missing the lacking functionality.

    I've even tried Toastman but it doesn't work either.
     
  7. sarelc

    sarelc Addicted to LI Member

    I would suggest making sure the only entries in the PPPoE configuration are your username, password, and (if necessary) your MTU. Filling in the Service Name field has been known to cause problems, for example.

    If that does not fix your issue, reboot the router and then watch the log page (Status > Logs > All Entries) for everything marked pppoe. The entries are not exactly easy to read, but they may give you (or us) some idea of what's going wrong.
     
  8. moffa

    moffa Serious Server Member

    This is my log with grep ppp: the xx's are my router's wan mac address


    Jan 1 01:04:15 unknown daemon.info pppd[664]: Plugin rp-pppoe.so loaded.
    Jan 1 01:04:15 unknown daemon.info pppd[664]: RP-PPPoE plugin version 3.10 compiled against pppd 2.4.5
    Jan 1 01:04:15 unknown daemon.notice pppd[665]: pppd 2.4.5 started by root, uid 0
    Jan 1 01:04:15 unknown daemon.info pppd[665]: PPP session is 1 (0x1)
    Jan 1 01:04:15 unknown daemon.warn pppd[665]: Connected to xx:xx:xx:xx:xx:xx via interface vlan2
    Jan 1 01:04:15 unknown daemon.info pppd[665]: Using interface ppp0
    Jan 1 01:04:15 unknown daemon.notice pppd[665]: Connect: ppp0 <--> vlan2
    Jan 1 01:04:16 unknown daemon.notice pppd[665]: PAP authentication succeeded
    Jan 1 01:04:16 unknown daemon.notice pppd[665]: peer from calling number xx:xx:xx:xx:xx:xx authorized
    Jan 1 01:04:16 unknown daemon.notice pppd[665]: local IP address 192.168.1.1
    Jan 1 01:04:16 unknown daemon.notice pppd[665]: remote IP address 192.168.30.6
    Jan 1 01:04:16 unknown daemon.notice pppd[665]: primary DNS address 204.197.191.194
    Jan 1 01:04:16 unknown daemon.notice pppd[665]: secondary DNS address 66.28.0.61
    Jan 1 01:04:18 unknown daemon.warn pppd[665]: Child process /tmp/ppp/ip-up (pid 687) terminated with signal 15
    Jan 1 01:04:18 unknown daemon.info pppd[665]: Terminating on signal 15
    Jan 1 01:04:18 unknown daemon.info pppd[665]: Connect time 0.1 minutes.
    Jan 1 01:04:18 unknown daemon.info pppd[665]: Sent 122 bytes, received 0 bytes.
    Jan 1 01:04:18 unknown daemon.notice pppd[665]: Connection terminated.
    Jan 1 01:04:19 unknown daemon.info pppd[665]: Exit.
    Jan 1 01:04:24 unknown daemon.info pppd[974]: Plugin rp-pppoe.so loaded.
    Jan 1 01:04:24 unknown daemon.info pppd[974]: RP-PPPoE plugin version 3.10 compiled against pppd 2.4.5
    Jan 1 01:04:24 unknown daemon.notice pppd[975]: pppd 2.4.5 started by root, uid 0
    Jan 1 01:04:25 unknown daemon.info pppd[975]: PPP session is 1 (0x1)
    Jan 1 01:04:25 unknown daemon.warn pppd[975]: Connected to xx:xx:xx:xx:xx:xx via interface vlan2
    Jan 1 01:04:25 unknown daemon.info pppd[975]: Using interface ppp0
    Jan 1 01:04:25 unknown daemon.notice pppd[975]: Connect: ppp0 <--> vlan2
    Jan 1 01:04:25 unknown daemon.notice pppd[975]: PAP authentication succeeded
    Jan 1 01:04:25 unknown daemon.notice pppd[975]: peer from calling number XX:XX:XX:XX:XX:XX authorized
    Jan 1 01:04:25 unknown daemon.notice pppd[975]: local IP address 192.168.1.1
    Jan 1 01:04:25 unknown daemon.notice pppd[975]: remote IP address 192.168.30.6
    Jan 1 01:04:25 unknown daemon.notice pppd[975]: primary DNS address 204.197.191.194
    Jan 1 01:04:25 unknown daemon.notice pppd[975]: secondary DNS address 66.28.0.61
     
  9. sarelc

    sarelc Addicted to LI Member

    That is strange, I take it the connect/disconnect cycle continues? If you have checked that the other PPPoE settings fields are empty there are two things you might look into - but be aware I'm not very familiar with VDSL so these aren't much more than guesses:

    The first is to search for something like "[name of provider] vlan settings". If your provider uses VLANs to separate access types (net/iptv/tel) then you may need to assign your router interfaces to the proper one. From your log it appears your wan? port is set to VLAN 2, maybe the oem firmware and DD-WRT assign it a different number by default. I'm unsure that would cause it to actually disconnect like this though.

    Second, you can try to find other mentions of pppd disconnects due to "signal 15". I have previously looked for that info when troubleshooting ADSL, but I don't remember finding anything particularily enlightening. Hopefully someone else has other (and better) suggestions! :oops:
     
  10. moffa

    moffa Serious Server Member

    Yeah it continues. All the other fields are blank such as service name etc.
    dd-wrt uses vlan2 for the WAN port.
    I found some links about using VLAN 35 for it, but I have nothing like that setup in dd-wrt.
     
  11. sarelc

    sarelc Addicted to LI Member

    Sorry to hear that. I suppose the other firmware could be choosing the correct setting automatically, but otherwise I guess that's a dead end. Have you tried any other Tomato builds, or compared the above pppd logs to those of DD-WRT?
     
  12. moffa

    moffa Serious Server Member

    If anyone ends up searching this thread, the solution is to add "noipdefault" without the quotes to the Options box under WAN / Internet.
    It took many hours to figure it out, hope it can help someone else.
     
    Armand1234 and gfunkdave like this.

Share This Page