Gargoyle Forum

Hi Guys/Girls,

A question for you

I've been using Gargoyle for about a year and loving it, everything that I wanted to do has been fantastic! Particularly the tracking of internal devices on our local network here at home.

My issue....

We've recently changed internet providers and I've been lucky enough here in Australia to get fibre to the home. Loving the 100 mbps down and 40 mbps up.

So the equipment was installed and everything worked perfectly.

Equipment Wise I'm running the Netgear WNDR3800.
Gargoyle Version : 1.5.8

* Internet connectivity via PPPoE (wired).
* LAN setup (DHCP server running with many static IP addresses set...

All perfect so far.

Now the problem... On an intermittent basis the WAN component of the router is shouting itself internally to the network as a DHCP server.

I was working on the mac the other day and suddenly It appears that i'd lost access to the internet.. After stuffing around for a few minutes I realised that the TCP settings in network config had renewed it's LAN DHCP list with the router but instead returned the default gateway to the WAN IP address.... instead of the LAN dhcp server.

Does this make sense????

The WAN component of the router is acting as an internal DHCP server. This shouldn't happen.

To make it super clear let me jot down the details.

Working normally - iMac
----------------------------------
Assigned Static IP address : 192.168.2.195
Subnet Mask : 255.255.255.0
Default Gateway : 192.168.2.195

Lease renews

Not working
------------------------------------
Assigned Static IP address : 192.168.2.195
Subnet Mask : 255.255.255.0
Default Gateway : 192.168.2.46

If I manually set the IP settings on the mac of course everything works.

Right now (having reset the WAN settings about 10 minutes ago, I'm not getting a PING back from *.46 but give it an intermittent time and bang it comes back....

Any help here would be greatly appreciated...

Thanks.
Bennie

You should NOT have your router in the same ip subnet
as your main access point if both of them supply DHCP

If your main AP is in the 192.168.2.* range, you should make your
router IP range as 192.168.3.* or some other range other than *.2.*

Or see if you can login to the main AP and disable DHCP on that

An update for you regarding this matter.

Thanks for replying DoesItMatter but what you suggested wasn't actually what was going on.

The issue was that my internet connection was going directly to the switch first instead of the router... Probably a good idea as well compared to the internet having a straight through pass into my network.

So I now have a physical connection directly to the router and then back into my own network.

Out of interest, the rogue DHCP server was actually the router itself, as in the WAN interface.

Now that everything has been reset and with the re-arranged cabling I haven't seen this issue in two weeks now

Cheers.
bennie