NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Struggling to set up port forwarding for my BBQ Guru CyberQ
I have a Netgear Model C7000 router. I also have a BBQGuru wifi Temperature controller for my outdoor grill. My controller pairs perfectly with my router, but I need to set up port forwarding to op...
> [...] BBQGuru wifi Temperature controller [...]
Any particular model? Is a User Manual available in some already
known location?
> [...] I need to set up port forwarding to operate my temperature
> controller remotely.
Perhaps. Many remotely controlled gizmos don't need it.
> I have tried to set up this connection a couple of times but I keep
> getting the same error...
What, exactly, are you specifying in this troublesome port-forwarding
rule?
> I have tried a couple different things.
Not a very detailed (or useful) description of anything.
> BBQ guru1.png
Is this a Web interface of the gizmo itself? This would seem to be
consistent with a need for port forwarding. How were all those
"192.168.101.x" addresses determined? I would not expect to see any
"Static" addresses with "DHCP Client On", unless the gizmo itself fills
in the values. The "Static DNS Address" looks particularly unlikely.
What's the LAN address of your router?
> HTTP Port 800
Are you specifying that port in your Web browser URL (":800") when
you talk to this thing, or is that port used only by the app?
Sorry yes that is a web interface of the device itself
> What, exactly, are you specifying in this troublesome port-forwarding
> rule?
Still wondering.
> They have a video instruction
> [...]
No, thanks. I'm willing to look at a manual, but not sit through
some movie which I can't skim. Unless I get seriously bored someday.I guess my problem is that no matter what port I use it says that it is in use.
> I guess my problem is that no matter what port I use it says that it is
> in use.
My problem is that I can't guess what you're actually doing which
fails.
> > What, exactly, are you specifying in this troublesome port-forwarding
> > rule?
>
> Still wondering.
Still true.