Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 2 subscribers
  • Views 9995 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

Default Drop Issue

DaMaN841
Hi Folks,

Noticed some traffic that was being blocked and I'm trying to determine what obvious rule I'm missing.

Default DROP: TCP  
146.148.44.137: 56700 
  • Internet IPv4 --> 56700→1:65535 --> Internal Host (that I expect it to go to)
  • Internet IPv4 --> Any --> Internal Host (that I expect it to go to)
  • Internet IPv4 --> 56700→1:65535 --> External WAN (Address)
  • Internet IPv4 --> Any --> External WAN (Address)
[/LIST]
The TCP packet that is dropped is the WAN IP, which is why I added the last two rules, however, it confuses me to swap out Internal Host with External WAN. Reading it seems circular since Internet IPv4 is External WAN (Network); External WAN (Network) --> 56700→1:65535 --> External WAN (Address). Seems strange to me.

With that in mind, I then considered using 146.148.44.137 --> 56700→1:65535 --> External WAN (Address), however, I'd prefer not to lock it down to that IP.

Any clarification from an abstract perspective would really help. I haven't had to deal with this direction before, less port forwarding. I even looked at Automatic Rules, however, nothing really mirrored what it seems like I'm attempting [:S]

Cheers,
Kyle


This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to darrellr_01
    That makes sense, Bob. Thank you.

    I have not, darrellr. The only thing that they claim is required is opening TCP 56700. I see plenty of traffic under Network Usage (outbound).

    I'm really not convinced that the Firewall Configuration is the problem, however, I noticed the drops so I thought I'd bring it to the attention of the community to rule it out. Based on what Bob pointed out, I have a feeling that it is on their end...perhaps closing the conversation too early or not early enough. It certainly seems to be a LIFX Cloud problem. 

    I'll be contacting LIFX to determine if they can determine what's going on. Thanks guys!

    Cheers,
    Kyle