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

BUG: Unable to connect to modem IP if WAN down

Discussion in 'Tomato Firmware' started by Kevin Darbyshire-Bryant, Jun 24, 2013.

  1. Kevin Darbyshire-Bryant

    Kevin Darbyshire-Bryant Networkin' Nut Member

    Please can someone fix this bug:

    Tested with Toastman or Shibby. When using the 'Route Modem IP' option to be able to connect to an ADSL/VDSL modem connected to WAN port, I'm unable to connect to the modem (ping it even) *IF* the WAN interface has never successfully connected. It looks like vlan2 doesn't get a modem subnet IP address unless the WAN is brought up.

    WAN type is either DHCP or PPPoE.

  2. Elfew

    Elfew Network Guru Member

    Can you debug it, or just test it with Victek latest beta? I cannot confirm it, but I will test it later... no time now, I go sleep
  3. M_ars

    M_ars Network Guru Member

    can confirm that problem/bug. But this behaviour has been around for a while... donĀ“t know if it ever worked "right". If WAN is up, everything is working :)
  4. szpunk

    szpunk Addicted to LI Member

    Confirm that bug too. And this behaviour has been around for a while...
  5. mstombs

    mstombs Network Guru Member

    I don't have this bug with tomato and dhcp- because modems operate in a half-bridge type mode, when they are not connected they still connect to router with a local IP/ short lease.
  6. Kevin Darbyshire-Bryant

    Kevin Darbyshire-Bryant Networkin' Nut Member

    My modem operates in full bridge mode, encapsulating Ethernet frames in RFC1483(IIRC) AAL5. It maintains a fixed IP address for configuration via a web interface for which it doesn't forward those frames. Tomato says 'Route Modem IP' which is great. Unfortunately it is dependent upon Tomato's WAN connection being established. If it's not established then I can't communicate with the modem, to fix what may be a configuration issue (Encapsulation Style (VCMUX/LLC) & VCI for example) which is preventing me from getting a WAN connection....see catch 22 :)

Share This Page