[Shibby] Wireless Ethernet Bridge DHCP Forwarding Issue...

Discussion in 'Tomato Firmware' started by ahplk, Oct 14, 2012.

  1. ahplk

    ahplk Serious Server Member

    I'm wondering if anyone might have an explanation for the following issue that popped up for me the other day...

    I've been running an Linksys E4200 (Shibby build -> tomato-E4200USB-NVRAM60K-1.28.RT-N5x-MIPSR2-99-Mega-VPN) as a Wireless Ethernet Bridge connecting to my landlord's Belkin F7D8302 Play N600 router. It's been running in this configuration for about 2 months but the other day I noticed that I was no longer obtaining an IP through the Belkin's DHCP server on any of my devices.

    As far as I know, nothing was changed on the Belkin so I'm kind of stumped as to what happened. I took a look into both router logs and didn't see anything abnormal. I have a refurb E4200 with a slight overclock (480->500) so at first I thought it was something hardware related, but after further investigation I have no idea.

    I've tried clocking back to stock speeds, resetting NVRAM to defaults (thorough), hard 30/30/30 resets, flashing to the latest Shibby build 101, and switching over to a DD-WRT set up. I could still connect fine after manually assigning an IP for each of my machines, but this was a pain in the ass so I switched over to using my E4200 as a repeater on a separate subnet with it's own DHCP server and it's doing the trick.

    Any ideas as to what went wrong?
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice