Page 1 of 1
Quota on Lan Traffic
Posted: Tue Aug 10, 2010 12:35 am
by snippet
Same story you've probably heard 100 times before, share house quota etc.
But its not a cable/dsl line, so i have a modem (dlink dsl 2740-b) connected to the phone line, then im hoping to use my gargoyled dir-300 router to implement traffic quotas on the people in the house.
But the quota managment only works when the connection is on the WAN port, which wont work in my case, so is it possible to monitor it on the LAN ports insted? We all connect wirelessly to the router.
Thanks
Re: Quota on Lan Traffic
Posted: Tue Aug 10, 2010 2:03 am
by DoesItMatter
You connect wirelessly to the router - you mean the DIR-300?
Or you connect wirelessly to the (dlink dsl 2740-b) ?
Hmm...
Your only option to monitor would probably be disabling wireless
on the DSL router and route all traffic through the DIR-300
But in that case, you would lose wireless-N capability
And currently, gargoyle does not officially support wireless-N
routers yet, so you couldn't just buy another wireless-N router
I'm not sure if you can use this at the moment on your setup
Re: Quota on Lan Traffic
Posted: Tue Aug 10, 2010 4:31 am
by snippet
Yeah, we connect wirelessly to the dir-300.
The loss of the wireless-n traffic isnt that important since g covers the house well enough.
I can get everyone connecting to the dir-300 fine, but i cant monitor the ethernet traffic.
Re: Quota on Lan Traffic
Posted: Fri Aug 20, 2010 6:00 am
by snippet
No idea if anyone else cares, but I managed to find a solution to this problem.
heres my setup
internet<->dsl 2740 b<->dir 300<->clients
The dsl 2740 has the ip 192.168.1.1 with dhcp on, and a static ip reserved for the dir 300, it also has the dir 300 in the DMZ.
The connection from the dsl 2740 goes from LAN to the WAN port of the dir 300
The dir 300 is in gateway mode with a static wan ip of 192.168.1.10 (reserved on the dsl 2740) and a gateway of 192.168.1.1
I also set 192.168.1.1 as a DNS server
The dir 300 has an internal ip of 192.168.2.1, and reserved ip's for clients based on mac addresses.
And with this setup I was able to solve the problem i posed in my original post