i have inherited the wifi here and we have changed our internet line which means it has a different IP
since then The Dude is not reporting properly as it just seems as if the access points are down
i believe the dude to be installed to an access point at each site. how do i access the dude and where to change the IP, that is if i am correct?
i have the dude 3.6 installed to my pc where i can monitor the access points , in the agent section it shows the dude servers. i just need to know where to change the external IP so the dude servers know how to get to me.
the dude servers don’t need to get to you, the Dude windows client program connects to them, not vice versa. basically it should work if you can ping the dude servers from the windows pc. make sure there is no firewall or windows permission problem stopping it.
As far as i know we have the dude installed to a config on an AP at this site. The monitoring works fine for this site
let me try and explain how things are setup here
Site 1 - there is a dude installed to an AP next to the router (we recently changed the internet lines IP)
The dude which is installed to my PC monitors and reports this site no problems
Site 2 - (uses a different internet line to site 1 and 3) everything is still the same as before however we no longer see if the access points are up as everything is down since changing the IP on site 1
Site 3 - (uses a different internet line to site 2 and 1 )everything is still the same as before however we no longer see if the access points are up as everything is down since changing the IP on site 1
so you can see the pattern here, i was thinking that there must be a dude server installed to an access point at site 2 and site 3? and this cannot report back as it is trying to get back to the old IP at site 1?
am i incorrect with the above?
We have a firewall with rules setup for the Dude etc and all the policies are being used as before but just with the IP change
I cannot ping the APs on site 2 and 3 (don’t think we have ever been able to) they are using the same IP config as site 1 however they are using different internet lines with different external IPs
I can connect to these external IPs and APs from winbox.
The new internet line at site 1 (which now has a different IP) is the only change in this factor
thanks
so the dude servers can be installed to an access point? correct?
the dude server on an access point does not connect back to anywhere but instead the dude client installed to a machine connects to them through the agent setup?
in the agent on the due client i have the ip address of the 3 sites
site 1 is the local IP
site 2 is an external IP
site 3 is an external IP
all using the same port
if i cannot connect to them anymore then it is down to a routing issue from my client to those IPs? is that correct?
yes, all correct. from the windows machine, you should be able to ping those agents. make sure that in the agent settings the IPs match the actual IPs on those APs. Make sure they are reachable. Agents don’t “communicate back”, the server connects TO them, like you already wrote in the last post.
I have a similar issue but nothing has been changed as far as I know
this is the same setup as before and all working fine.
I have the dude installed on my local network and have 3 sites that it monitors.
2 of the sites is working fine however the 3rd site is showing as down.
if I go to the site I can actually ping between the devices and I can also winbox onto the AP on this site from my local network however the dude reports it as down.