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

WRT54GL , Tomato 1.13 , HUAWEI MT800

Discussion in 'Tomato Firmware' started by baldrickturnip, Dec 29, 2007.

  1. baldrickturnip

    baldrickturnip LI Guru Member

    Hi,
    I am trying to get running an Huawei MT800 ADSL modem and a WRT54GL with Tomato 1.13 firmware.

    my Huawei I have configured as RFC2684 Bridged , pure bridge - LLC encapsulation and it has a LAN config as 192.168.1.1
    ADSL is multimode and DHCP and DNS are disabled.

    my WRT54GL has the WAN/Internet port set as PPPoE , the isp username and password and service name , manual MTU 1492
    LAN has the router IP as 192.168.1.2 , and subnet 255.255.255.0 - 2 static DNS entries - DHCP server enabled serving 1.50 to 1.100

    NAT loopback is disabled
    use internal caching DNS forwarder is checked
    use recieved DNS with static DNS is checked
    reduce packet size is unchecked

    the Huawei connects to the ISP and displays the correct LEDs and the WRT54GL under status gets assigned an IP , subnet ,gateway and additional DNS server addresses from the ISP.

    I can use the ping utility on the WRT54GL to resolve and ping google

    on the computer connected to a LAN port on the WRT54GL , ipconfig /all gives me an IP and subnet and the gateway and DNS server are both 192.168.1.2.
    when I ping www.google.com it resolves the IP but no ping results - it times out.
    the browser resolves google but times out waiting.

    I cannot access the Huawei config page at 192.168.1.1 when the modem is connected to the router WAN port , but it is fine when I plug it into a LAN port on the router.I also cannot ping 192.168.1.1 when the modem is pluged into the WAN port - it times out - though it works fine when in a LAN port

    and my question - :) - what simple thing am I doing incorrectly ?
     
  2. u3gyxap

    u3gyxap Network Guru Member

    Start with changing the LAN ip address to 192.168.0.1
     
  3. baldrickturnip

    baldrickturnip LI Guru Member

    ok
    change the LAN address on the router or the Modem ?
    and does it have to be 192.168.0.1 , or could it be 192.168.x.1 ?
     
  4. LLigetfa

    LLigetfa LI Guru Member

    Either, as long as the x isn't 1.

    Personally, I would put the modem into the 169.254.0.0 scope. That way, you don't need to hard code the PC when you direct connect for troubleshooting purposes.
     
  5. maxzerker

    maxzerker LI Guru Member

    I think you may missed configured your WRT54GL as "Router mode" instead of "Gateway mode".

    In this mode WRT54GL will not enabled NAT and act as Router only,
    You can change to "Gateway Mode" via tomato's web interface by enter the menu

    Advanced -> Routing -> Mode

    PS.as you mentioned DNS was resloved fine it's because you're using WRT54GL DNS caching (it's local service)
    also your WRT54GL ping fine because it's directly connect to the internet.
    The client behind WRT54GL can't connect to the internet because of NAT is not enabled.

    PS2. if you're THAI PP you can directy contact me via www.adslthailand.com/forum
     
  6. FRiC

    FRiC LI Guru Member

    Try checking the gateway/router mode as the previous poster suggested... I just want to add that it shouldn't matter what you set the IP of the modem to if you're using PPPoE. I usually set it to some unused IP in my LAN, so when I need to configure the modem, I just move it from the WAN port to a LAN port and go to that IP.
     
  7. LLigetfa

    LLigetfa LI Guru Member

    I added a couple of scripts. One to give the WAN port a 169.254.1.x IP, and another script an IPTables rule.

    I can access the 169.254.0.0 network through the WAN port, or I can plug the laptop directly into the modem and get both a PPPoE connection while also a 169.254.y.z IP through APIPA. Sometimes when dealing with tech support, they will look at the ARP table on the modem and know that you have a router attached and will insist that you direct connect. Using APIPA, it saves having to hand-job the IP. I don't know how much time I wasted because I either fat fingered a setting or forgot to put it back to DHCP afterwards.
     
  8. Toxic

    Toxic Administrator Staff Member

    if your Modems LAN IP is 192.168.1.1 then the LAN on the router cannot be in the same IP range. so set the Routers LAN to something different 192.168.5.1 for instance. this way you wont get mixed up with what LAN you are on and the WAN IP address of the router should then be in the same IP range as the LAN of the Modem.

    Modem LAN: 192.168.1.1
    WRT54GL WAN: 192.168.1.2
    WRT54GL LAN: 192.168.5.1

    hope this helps.
     
  9. baldrickturnip

    baldrickturnip LI Guru Member

    yes did have the modem set to router and not gateway
    I have separated the modem LAN and the router LAN

    thanks for the help

    and Max I will check out your forums - which I think was where I found the password for the true firmware on the Huawei ( Username คือ admin Password คือ "ทรูคอร์ปอเรชั่น" เป็นภาษาอังกฤษ หรือ mi^8viNxvgi=yjo ) - But I cannot read Thai so I am a bit limited , I can only guess from the english words interspersed.
     
  10. paped

    paped LI Guru Member

    I know this may be going back to basics from some of the previous posts but have you spoken to your ISP about this. As it sound like there is a problem with DNS so the issue could be at your ISP not your home equipment. I had an identical issue a few weeks ago (after upgrading to 1.13 could this be a bug?) and it turned out to be my ISP's Kerberos server at fault. My account had locked or become corrupted so it was showing as connected in my router but not allowing me full access to my ISP's network/the internet/DNS. It was fixed in 5 minutes by my ISP's 2nd line support, by them running checks against my account and resetting it....
     

Share This Page