FVG318 DHCP Reservation STILL not working v2.1.2-67N

[Daedalus01]

Originally Posted by wireman121

Before checking back I reset both routers to factory settings, both had crashed out today at different times. After the reset it seems like everything is working a LOT more smoothly, and reservations are even working (within the DHCP range too!) so I'm wondering if the firmware upgrade had some sort of weird effect on the router that I needed to reset it to factory settings before it would start functioning properly again. I'll update if anything changes again...

That's good to hear. Not only do I reccomend resetting to factory defaults with firmware upgrades on net gear routers, but all routers. It seems everything works out more smoothly.

[wireman121]

Everythings been working fine since that reset until this afternoon where 1 of the 2 routers froze up again. A power cycle made no difference and I again had to reset to factory defaults and reconfigure.. I have no idea what is causing this, but it would be great to hear from other people with this same router to know if I'm the only one or not. Seems odd that I've had problems with 2 of these routers. Already considering returning them and getting the non-wireless version, which I assume is more stable?

Anyone know if Netgear is planning any future firmware updates that might make these routers more stable?

[jmizoguchi]

Anyone know if Netgear is planning any future firmware updates that might make these routers more stable?

forum is use to user.

Ask support directly with the issues. sometime they will produce beta firmware if need it. my.netgear.com

[wireman121]

Both routers locked up AGAIN last night/this AM. A power cycle seems to have fixed it this time, on at least 1. I need to physically go to the other one still...

[Daedalus01]

Is it locking up with the VPN established? have you tried to have one box running with no vpn to see if it locks up and if the DHCP reservation works? Im wondering if the VPN is somehow throwing a wrench in it.

[wireman121]

Thats going to be my next try. Everything has been working great for a while and then i rebooted 1 PC which has DHCP reservation and it pulled a different IP again. And back to I cant get it to pull the reserved IP no matter what I do. This is just dumb now. It seems like the router thinks the MAC is still attached to the IP and it throwing out a different IP because of it....wtf

[wireman121]

Heres the DHCP log:
JUL 10 14:31:59 FVG318 tDhcpsTask: DHCPDISCOVER from d4:be:d9:a7:28:69 via mirror0
JUL 10 14:31:59 FVG318 tDhcpsTask: DHCPOFFER on 192.168.0.120 to d4:be:d9:a7:28:69 via mirror0
JUL 10 14:31:59 FVG318 tDhcpsTask: DHCPREQUEST from d4:be:d9:a7:28:69 via mirror0
JUL 10 14:31:59 FVG318 tDhcpsTask: DHCPACK on 192.168.0.120 to d4:be:d9:a7:28:69 via mirror0
JUL 10 14:32:15 FVG318 tDhcpsTask: DHCPDISCOVER from d4:be:d9:a7:28:69 via mirror0
JUL 10 14:32:15 FVG318 tDhcpsTask: DHCPOFFER on 192.168.0.120 to d4:be:d9:a7:28:69 via mirror0
JUL 10 14:32:15 FVG318 tDhcpsTask: DHCPREQUEST from d4:be:d9:a7:28:69 via mirror0
JUL 10 14:32:15 FVG318 tDhcpsTask: DHCPACK on 192.168.0.120 to d4:be:d9:a7:28:69 via mirror0


router is not even looking to see if theres a reservation before dishing out an IP address.

There HAS to be something wrong in the firmware for these units...this cant be just me having this problem!!

[jbhelmnet]

I am having similar issues where I have certain IP addresses reserved, but the router (FVS318G) keeps giving out them out to other systems. I never had any issues when I was using my previous routers. As mentioned, it seems the router doesn't even check for a reservation.

[jbhelmnet]

I found one of the devices that kept improperly coming up on another devices reserved IP. I reserved an IP for this device, but it kept coming up on the other IP. I forced it over to another IP by turning it off and getting the correct device up on the IP it kept getting. I then brought that device back onto the network. In the logs, I then saw where the DHCP service on the router, kept pinging IP address starting from the beginning of the pool until it found the first non-used IP. It seems the router does not consult the reservation list, but instead simply pings for the first available even when a reservation is set for the requesting device.