Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[yodamin]

Hi,

I have an old 10/100 dir-632 8 port wired/wireless.

My network setup does not involve the default 192.168.0.* ip addresses.
I do not use the wan port at all - it is connected internally through a lan port to a linksys router.
My internet router is a netgear with wireless on.
I use the dlink as a switch basically (although I known that's not a true switch, it has served fine until now)

Recently, the past 3 months or so, the dlink sporadically and frequently (maybe 2-3 times weekly) starts sending arp requests out for the whole 192.168.0.* subnet.
this is curious since I have turned off all "router" functionality, meaning disabling everything right down to firewall, wireless, dhcp server everything turned off. no port forwards, no port triggering, no QoS nothing.

I have manually configured a "fictional" static WAN side ip/subnet/gateway so on and so forth. I have also tried leaving the wan side set to dhcp.

I have three PC's attached to this router and when the arp requests start they all slow down. Eventually the whole network will get noticeably slower. I reboot all the routers and everything goes back to normal for a day or three.


Wanting to get to the bottom of this I installed wireshark on my server and monitored the situation. That is how I found out that the dlink router is the cause of my network woes.

My one and only question is this: If the dlink is not configured to use 192.168.0.* for it's ip schema and is in fact configured to use 192.168.124.* (statically) then why, oh someone please tell me why is the darn thing constantly sending arp request's wanting to know who is 192.168.0.1 and so on through to .254 with a please tell "ip" of the dlink?

The ip's 192.168.0.1-254 is not used anywhere on my network, nor have they been for quite some time, so why is the router repeatedly asking for the identity of these IP's? Where is it getting the idea that these IP's even exist on the network?

Is it broken or do ALL consumer grade dlink routers do this. The reason I ask is because a friend of mine also has a dlink router, much newer version, with only one PC connected to it. That dlink and the PC are both NOT configured to use 192.168.0.* IP's but when we install wireshark on my buddy's PC sure enough the same activity is going on?

Is the firmware stupidly hard-coded for this type of behavior and I just didn't notice until my recent expansion of network devices in my home?

I await, anxiously for anyone who can shed some light on this issue for me.

Thank You.

[yodamin]

One more thing. I realize I am not sing the router as it is meant to be used. I do not blame dlink for this, in fact I think the router is a sweet piece of gear. However, rather than go through all the normal B.S. of people telling me it couldn't possibly be the router when I KNOW it is, I would like someone to:

1>0 offer a usable solution that woudl enable me to continue using the router as it is being used OR

2> give me a reson why the router cannot be used for this purpose and I will go buy a switch that CAn be used for this purpose.

I just don't want to do weeks of troubleshooting on the off chance we'll get it working. I'd rather buy a new switch if it MUST come to that.

Thanks.

John

[yodamin]

Ok New switch it is. Imma donate the dlink to the mission.

Cheers.

[FurryNutz]

This would have probably resolved this: Turning a router into an AP.

This is a end user configuration problem.