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

WRT-54GL not picking up external IP from X3 modem

Discussion in 'Tomato Firmware' started by losimagic, Apr 21, 2007.

  1. losimagic

    losimagic LI Guru Member

    Been trying to set up a Zoom X3 ethernet modem with my WRT-54GL (running the latest version of Tomato) for the past few days with little success but I think I've finally got to the problem.

    I have the X3 setup to connect to the internet (DSL, PPPoA) and it's in half-bridge mode. When I connect my PC directly into the X3, my NIC receives my external IP address, 83.67.xx.xxx and 255.0.0.0, with a gateway of 194.106.xx.xxx. However, when I connect the X3 to the WRTs WAN port, it receives 10.0.0.6 and 255.255.255.0, with a gateway of 10.0.0.2.

    Has anyone seen this before? Is there a solution?

    Previously I was running the WRT connected via a safecom 4112 modem, that worked perfectly until the 4112 blew up - I've not changed any settings on the WRT

    Many thanks!
     
  2. roadkill

    roadkill Super Moderator Staff Member Member

    try to clone your pc mac address or if it doesn't work try to create a PPPoE connection to the zoom ip address and turn off automatic PPPoE/PPPoA dialers in the zoom webif
     
  3. losimagic

    losimagic LI Guru Member

    When cloning my PCs MAC onto the WAN port of the WRT it received my external IP address (83.67.xx.xxx and 255.0.0.0, with a gateway of 194.106.xx.xxx) but the router couldn't see the modem (didn't show up in attached devices) and I couldn't connect to 10.0.0.2, and I had no internet connection.

    Something strange happened after that though, I reset the MAC, rebooted the WRT and rebooted the X3, the correct IP address was being picked up by the WRT but I still couldn't see the X3 or access the internet.


    As for you second suggestion, I have to connect via PPPoA :(
     
  4. roadkill

    roadkill Super Moderator Staff Member Member

    no you can't connect via PPPoA from outside the device the first suggestion is the right one..
    you'll have to add a vlan to your modem on the router there is a thread here that explain how to add another vlan in order to access the webif of the modem
     
  5. losimagic

    losimagic LI Guru Member

    Thanks, I wish I could try that out... the X3 no longer wants to synch with the exchange now, it just sits there trying to do various learning handshakes but never actually synchs :(

    Looks like I'll be calling Zoom tomorrow - then maybe I can try your suggestion


    Thanks for your help, I might come back to it soon :)
     
  6. roadkill

    roadkill Super Moderator Staff Member Member

    Sure
    Good Luck with Zoom Support...
     
  7. losimagic

    losimagic LI Guru Member

    Well I feel pretty dumb now - the reason it wasn't syncing was because I was plugging my DSL line into the X3s telephone socket, not the adsl socket :(

    Anyway, after looking through that thread you showed me, I added the following to my WAN up page:

    ip addr add 10.0.0.1/24 dev vlan1 brd +
    /usr/sbin/iptables -I POSTROUTING -t nat -o vlan1 -d 10.0.0.0/24 -j MASQUERADE

    This now allows me to access my modems configuration at 10.0.0.2 when it's plugged into the WAN port on the router.

    However, I still can't access the internet.

    The X3 (in half-bridge) is receiving the following:
    IP: 83.67.xx,xxx
    Mask: 255.255.255.255
    Gateway: 194.106.xx.xxx

    The WRT is receiving:
    IP: 83.67.xx.xxx (same)
    Mask: 255.0.0.0 (different)
    Gateway: 194.106.xx.xxx (same)

    The different masks, could that be why I'm not getting online through the router?


    edit: just check what my PC gets when it's plugged directly into the X3, that also gets 255.0.0.0 :(

    another edit: could it be anything to do with DHCP/NAT on the X3 not switching off correctly? I'm clutching at straws here really :(

    I just don't understand how I can get on when plugged directly into the X3 but not via the WRT :(
     
  8. roadkill

    roadkill Super Moderator Staff Member Member

    how did you configured the WRT?
    do you have DHCP spoof mode in your modem?
     
  9. losimagic

    losimagic LI Guru Member

    What configuration are you talking about?
    Under Basic -> Network, WAN is set to:
    Type: DHCP
    MTU: Default

    The X3 has 3 modes for DHCP, None, Server and Relay

    Server allows me to set:
    Lease time
    Max Lease Time
    Domain name
    Status: enable/disable
    Excluded IP(s)

    Relay allows me to set:
    DHCP Server address (for PPP I think)
     
  10. roadkill

    roadkill Super Moderator Staff Member Member

    dhcp spoofing mean the modem dials the connection and then forward the ip address as dhcp to the lan port... which as I understand it the half-bridge mode does... what I can't seem to understand is why it is mac address specific and why you can't get connectivity now I think you should first get internet running on the damn thing before you start messing with vlans...
    get it to run with a computer and then clone the mac address like before
    it worked when you did that no?
     
  11. losimagic

    losimagic LI Guru Member

    so I should set the MAC address of the WAN port on the WRT the same as the MAC address of one on my PCS?

    I'll try that
     
  12. roadkill

    roadkill Super Moderator Staff Member Member

    if your computer is working with the zoom like it should...
    it suppose to work the same
    I'm going through the zoom manual now...
     
  13. roadkill

    roadkill Super Moderator Staff Member Member

    and I have another question are you configuring static dns in the wrt/zoom?
     
  14. losimagic

    losimagic LI Guru Member

    I have static DNS stored in Tomato and on the NICs - I actually thought it might be that so I tried setting up the DNS on the X3 (and still having it set on the WRT/NICs) but that didn't make any difference.

    I've also tried setting the WRTs WAN port MAC the same as a PC and as a random MAC, neither made any difference :(
     
  15. roadkill

    roadkill Super Moderator Staff Member Member

    when you hook the zoom to a computer you get normal internet netmask?
    e.g. 255.255.255.255
     
  16. losimagic

    losimagic LI Guru Member

    255.0.0.0

    and it supplies the correct IP/gateway

    EDIT: Thought the modem reports 255.255.255.255
     
  17. roadkill

    roadkill Super Moderator Staff Member Member

    do a traceroute to some ip address on the internet and post the result
     
  18. roadkill

    roadkill Super Moderator Staff Member Member

    on yeah and try setting your modem ip address as static DNS with your ISP DNS servers
     
  19. losimagic

    losimagic LI Guru Member

    Do a traceroute when connected directly to the modem?
     
  20. roadkill

    roadkill Super Moderator Staff Member Member

    no through WRT but do try to set the modem address as first static dns
     
  21. losimagic

    losimagic LI Guru Member

    The WRTs DNS servers were set as: (opendns)
    208.67.222.222
    208.67.222.220

    the X3 were set at: (ISPs)
    194.106.56.6
    194.106.33.42

    I traced 213.247.51.21 (irc server)
    1) 192.168.1.1 reports: destination net unreachable
     
  22. roadkill

    roadkill Super Moderator Staff Member Member

    try to set X3 as first static dns
     
  23. losimagic

    losimagic LI Guru Member


    Sorry, I don't quite understand
     
  24. roadkill

    roadkill Super Moderator Staff Member Member

    first static dns on WRT
    you see something has to do the translation from netmask A
    either first static dns on WRT does the translation or the gateway...
    one of them has to translate that subnet to a normal internet one...
    I really don't get the point with it working like that...
     
  25. losimagic

    losimagic LI Guru Member

    sorry, still not totally clear... set the first static DNS on the WRT to 10.0.0.2 (the X3)?
     
  26. roadkill

    roadkill Super Moderator Staff Member Member

    yes 10.0.0.2 first static dns on the WRT either that or the gateway on the wrt
    but I don't think it's the gateway....
     
  27. losimagic

    losimagic LI Guru Member

    Ok, had the WRT DNS servers set to:
    10.0.0.2
    208.67.222.222
    208.67.222.220

    and the X3 set to:
    208.67.222.222
    194.106.33.42

    still nothing :(
     
  28. roadkill

    roadkill Super Moderator Staff Member Member

    don't have anymore ideas....
    except maybe reset the WRT mac address and access the X3 on a NAT address
    and set a that IP address as DMZ.
    a configuration that is ugly but will work...
     
  29. losimagic

    losimagic LI Guru Member

    I actually already reset the WRTs WAN port MAC a while ago, before trying all this DNS stuff - I'll go back and clone it to a PC again with these DNS settings.

    And for the 2nd part,stick 10.0.0.2 in the DMZ within Tomato and try that?


    If that all fails I'm not sure what else to try either, apart from cry, lol.

    I really really appreciate your help though, you've been fantastic!

    Thank you!!
     
  30. roadkill

    roadkill Super Moderator Staff Member Member

    you can also try to change the adsl line default encapsulation to PPPoE
    and try to use it as a regular modem maybe it will work...
    sure I love this little challenges...
    and I hate Zoom :biggrin:
     
  31. losimagic

    losimagic LI Guru Member

    Sadly my telephone exchange isn't enabled for pppoe, just pppoa... that'd make things too easy :(
     
  32. roadkill

    roadkill Super Moderator Staff Member Member

    DMZ works?
     
  33. roadkill

    roadkill Super Moderator Staff Member Member

  34. losimagic

    losimagic LI Guru Member

    ok... that took a while

    Can't put the X3 into the DMZ, tomato only appears to allow addresses from 192.168 to go into the DMZ.

    Something I just noticed though

    On the attached device page I noticed several IPs listed for Vlan

    83.26.xx.xx
    83.100.xx.xx
    83.128.xx.xx

    plus a few others - I could ping/tracert them!

    Still couldn't access the internet though

    so...what the hell? :(

    I'll take a look at that link and see what I can do but I think being limited to pppoa will stop me getting very far :(
     
  35. roadkill

    roadkill Super Moderator Staff Member Member

    dude you need to set DMZ from the original NAT
    10.0.0.2 - X3
    10.0.0.3 - WRT WAN PORT
    Enable DMZ for 10.0.0.3 from the X3
    you are on internet like you should but you get the netmask wrong for some reason so you can't reach no addresses
    try
    Advanced -> DHCP / DNS -> DHCP Client (WAN) -> DHCP Reduce Packet Size
    only to make sure it isn't changing anything...
     
  36. losimagic

    losimagic LI Guru Member

    Sorry, I don't understand, how do I give the WAN port an IP address of 10.0.0.3?
     
  37. roadkill

    roadkill Super Moderator Staff Member Member

    disable the half-bridge on the X3 configure it for router you'll get a standard NAT and enable DMZ on the WRT NAT address from within the X3.

    before you do that try
    Advanced -> DHCP / DNS -> DHCP Client (WAN) -> DHCP Reduce Packet Size
    it should make no difference but I want to try...
     
  38. losimagic

    losimagic LI Guru Member

    tried the packet size, that didn't work though :(

    Still not quite sure what you're suggestion for the other part:

    though this might be the page I'm after... http://temp.digitalshoebox.net/lan_configuration.JPG


    I'm going to have to head off now but I'll be back tomorrow. who knows, maybe one day this will all work.

    And again, thank you very much for all your help!
     
  39. roadkill

    roadkill Super Moderator Staff Member Member

    your welcome
     
  40. losimagic

    losimagic LI Guru Member

    I think I might start a new thread with a title closer to my issue now - "WRT54GL seeing internet connection but connected systems can't access internet" - something along those lines, might get a few more opinions into the thread
     
  41. roadkill

    roadkill Super Moderator Staff Member Member

    I think you can rename this one...
     
  42. losimagic

    losimagic LI Guru Member

    only edits a new subtitle, not the main one shown on the board as far as I'm aware
     
  43. mstombs

    mstombs Network Guru Member

    Sorry to be following you around losi - but have inadvertently reproduced your problem with my own half bridge modem script.

    It seems Tomato as well as Hyperwrt Thibor (and probably dd-wrt as well from google turned up posts) do not understand how to use the dhcp info from the modem when the gateway is not in the same network as the IP address. Windows XP and my Linux 2.6.20 PC both do understand and I can make Hyperwrt Thibor work with two manual "route" commands detailed here

    http://www.linksysinfo.org/forums/showthread.php?t=52937

    I guess similar commands would work for you in Tomato?

    Note as the IP and Gateway you quote earlier in this thread are completely different there isn't a sensible common 'spoof' mask you can use to patch it.

    To fix this problem correctly a small mod is needed to the router firmware in the equivalent of the udhcpc action scripts, available in Hyperwrt as a Firewall script.
     
  44. paped

    paped LI Guru Member

    Can you not set the modem to full bridge mode this would then mean that it would not get an IP address from your ISP but the WRT would.... The modem would effectively be transparent it would only have an internal Lan address on the WAN Vlan subnet for admin and would basically just be a protocol converter between ethernet from the WRT to DSL. If you have the full bridge option do the following:

    Setup the modem to full bridge mode.

    Once this is configured setup the WRT to use PPPoE and enter your username/password etc in the fields supplied on the WRT network page, click connect on WRT and this should work...

    What you will have is the DHCP address from your ISP on the WRT only as far as the ISP is concerned the WRT is now your modem.

    If it does not connect (but try it a few times) first reboot the whole system modem and WRT, if this still does not work then try entering your PC's MAC address in to the WRT so it is cloned on the WAN port just incase your ISP expects a certain MAC address.

    Once your up and working you can setup admin access to the modem via the WAN port to a local IP address (but not on the same IP subnet that your PC's use i.e if pc's us 192.168.0.x the modem would have to be something like 192.168.1.x ) using this details in this thread that has been referenced above http://www.linksysinfo.org/forums/showthread.php?t=50437.

    Hope this helps......
     
  45. mstombs

    mstombs Network Guru Member

    You can only do PPPOE full bridge if your ISP supports PPPOE [ISPs that route via BT often do work with PPPOE even though not officially documented]. The problem some of us have in the UK is that their ISPs only support PPPOA, LLU TalkTalk for example. For PPPOA the PPP client must exist in the modem, which is why we need a working half-bridge solution.

    I've seen a suggestion that the modem could convert PPPOA to a PPTP connection to the router, but no idea how to do this and no need as my half bridge solution now working fine, including web access to the modem - for me at least!
     
  46. paped

    paped LI Guru Member

    I'm in the UK and as far as I am aware my ISP is PPPoA only but my logon is from the WRT54GL using PPPoE via a Netgear DG632 setup in full bridge mode from my understanding the modem as well a doing the protocol conversion from ethernet to ADSL also does the conversion from PPPoE to PPPoA. This for me at least is the only way I can get it to work, if I use PPPoA on the WRT router the login fails. Not sure about your modem can it be setup as a basic router? Just thinking that the DG632 can be setup as either a modem or basic router, as such if this modem can be put in router mode you could in theory put it on a different subnet have it login then connect the WRT using an internal IP address in the modems subnet as the WRT WAN port IP i.e.

    ISP internet IP on modem --> modem --> modems internal IP e.g. 192.168.2.1 -->WRT WAN port on internal IP e.g. 192.168.2.2 --> WRT router --> LAN in second local subnet e.g. 192.168.1.x

    The only real down side with this config would be that any port forwarding would either need to be replicated on both the modem in router mode and the WRT or all ports could be forwarded to the WAN IP of the WRT then none forwarded ports could be blocked at the WRTs interface.

    Hope this helps.....
     

Share This Page