Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 6 subscribers
  • Views 2762 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Honeywell Redlink Internet Gateway not responding to dhcp offers.

William Moser

We have a few honeywell redlink internet gateways that we have been having nothing but issues with and we are all out of ideas here. Whenever this device sends a dhcprelease it does not respond to any of the offers until about 30 minutes has passed. This process consistently repeats and I have tried contacting honeywell support but they are less than helpful. The strange thing is that we have two versions of these redlinks and all of the older v1's work without issue (they consistently drop the dhcp lease just like the v2's but they immediately request and get the acknowledge) while all of the v2's perform exactly as described. Sadly no configuration can be done on the gateways themselves it is all pre-set from the factory. Thank you in advance if anyone has any ideas.

 

2020:04:15-10:23:11 d5-utm dhcpd: DHCPRELEASE of 10.5.131.1 from 00:d0:2d:eb:f0:de (GatewayEBF0DE) via eth0.131 (found)
2020:04:15-10:23:12 d5-utm dhcpd: DHCPOFFER on 10.5.131.1 to 00:d0:2d:eb:f0:de (GatewayEBF0DE) via eth0.131
2020:04:15-10:23:12 d5-utm dhcpd: DHCPOFFER on 10.5.131.1 to 00:d0:2d:eb:f0:de (GatewayEBF0DE) via eth0.131
2020:04:15-10:23:17 d5-utm dhcpd: DHCPOFFER on 10.5.131.1 to 00:d0:2d:eb:f0:de (GatewayEBF0DE) via eth0.131
................
2020:04:15-10:53:00 d5-utm dhcpd: DHCPOFFER on 10.5.131.1 to 00:d0:2d:eb:f0:de (GatewayEBF0DE) via eth0.131
2020:04:15-10:53:10 d5-utm dhcpd: DHCPOFFER on 10.5.131.1 to 00:d0:2d:eb:f0:de (GatewayEBF0DE) via eth0.131
2020:04:15-10:53:37 d5-utm dhcpd: DHCPOFFER on 10.5.131.1 to 00:d0:2d:eb:f0:de (GatewayEBF0DE) via eth0.131
2020:04:15-10:53:37 d5-utm dhcpd: DHCPREQUEST for 10.5.131.1 (10.5.131.254) from 00:d0:2d:eb:f0:de (GatewayEBF0DE) via eth0.131
2020:04:15-10:53:37 d5-utm dhcpd: DHCPACK on 10.5.131.1 to 00:d0:2d:eb:f0:de (GatewayEBF0DE) via eth0.131
2020:04:15-11:05:52 d5-utm dhcpd: DHCPRELEASE of 10.5.131.1 from 00:d0:2d:eb:f0:de (GatewayEBF0DE) via eth0.131 (found)
 


This thread was automatically locked due to age.
  • 0

    Hi William and welcome to the UTM Community!

    I'm not familiar with those devices, but what happens if youset the lease time to a day?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Actually the lease time is already set to a day. Whats happening is that supposedly it attempts to ping a set list of Honeywell servers and when it doesn't get a response from either a certain amount of them or any of them it will drop the dhcp lease and grab another then try again. We have these devices on their own vlan with full access to the internet and as far as i can see there are no firewall blocks but it still drops the lease. The v1 of these devices do the same but whenever they drop the lease they are able to immediately grab another so they never go offline. The v2 of these devices will sit for exactly 30 minutes for some reason before they will send the dhcprequest so they spend most of their time offline.

  • 0 in reply to William Moser

    This must have caused a dust-up on the Honeywell discussion board.  Or are you the only one with this issue?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    I did try looking for a Honeywell forum first but had no luck and their support was not very supporting. I was able to find a few with the same issue but most of them just resolved it by switching routers. Also I apologize in advance as I am definitely a newbie when it comes to networking but I did also notice that 5 minutes before it drops the dhcp lease the firewall starts logging invalid packets to and from the device. Are these still getting through or could this be the reason why it keeps dropping the lease? We do have block invalid packets disabled. 

    d5-utm ulogd[29663]: id="2000" severity="info" sys="SecureNet" sub="packetfilter" name="Packet logged" action="log" fwrule="0" srcip="199.62.84.152" dstip="10.5.131.1" proto="6" length="44" tos="0x00" prec="0x00" ttl="240" srcport="443" dstport="58074" tcpflags="ACK SYN" info="nf_ct_tcp: invalid packet ignored in state SYN_RECV "

    d5-utm ulogd[29663]: id="2000" severity="info" sys="SecureNet" sub="packetfilter" name="Packet logged" action="log" fwrule="0" srcip="10.5.131.1" dstip="199.62.84.152" proto="6" length="48" tos="0x00" prec="0x00" ttl="128" srcport="58074" dstport="443" tcpflags="SYN" info="nf_ct_tcp: invalid packet ignored in state SYN_RECV "

  • 0 in reply to William Moser

    Interesting, William.  I don't remember a case like this.  If this is a paid license, please get a case open with Sophos Support and let us know what you learn.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to William Moser

    Hey William,

    I'm wondering if you ever figured this out and have a resolution.  I have exactly the same issue:

    Recently installed a new Amana HVAC that came with a Honeywell ComfortLink smart communicating thermostat.  Ya, it's smart but doesn't include WiFi built in these days?!?!  So I bought the Redlink Gateway adapter from Amazon and had it working within 10 minutes of its arrival, but...

    It only stays connected for 3-5 minutes at a time, and then I get the same "defconf offering lease <ip_addr> for <mac_addr> without success, over and over and over.  If I remove and re-apply power to the Redlink Gateway, it successfully reconnects again ... but only for a few minutes.

    I tried downgrading my Mikrotik RB2011 from 6.47.1 (latest) to 6.45.9 because I'd read somewhere that this Mikrotik problem snuck in with 6.47 ... but the downgrade didn't help at all ... same issue.

    I've also tried different ethernet cables and different connect points (through my router, through my switch, through my WiFi modem's eth port), with no change.

    And I've tried temporarily disabling the firewall rule that discards invalid packets, with no change.

    I have no problem with any other device; only this new Redlink Gateway thing gives me grief. 

    Thank you,
         Greg 

Unfiltered HTML