Just strike… how to prevent NATed access from clients ?
Let say an IP allocated to client X is 192.168.2.0/28 and suppose to add more PC’s, client decide to put NATed into one of an IP allocated. It could be Winroute, Wingate, linux nat, etc.
It’s simple - add mangle rule with action set TTL to 1. But i don’t think you should disallow NAT because many are using wireless routers to connect their laptops.
You can use TTL… but my opinion is to let them work.. behind the nat can be 100 computer but they will share one band wich you are giving to them so it shouldn’t affect… other solution is if traffic will be high from that user.. try to do some Usage limitation… if Data transfer will exeed some value change speed to lower for some period of time.
I have tried to change the TTL value to 1 but it seems not to work, I could not connect to internet.
I have the same problem Prevent NATed access may be try to use conection limit, or packet limit I don’t know
I would be Very glad If somebody solves this problem
Well obviously there are some error in your firewall configuration. Probably you are setting TTL to 1 for outgoing packets and they die at gateway.
Maybe post your config?
You can do set ttl to 1, but any “wise” user with some networking knowledge will pass trough that, by any of several posibilities of routers that can change ttl themselves.
You can use connection limits, but even that won’t help too much.
Changing ttl will stop only casulal “smarties” from sharing your internet connection.
It’s all about what are you selling: bandwidth or number of stations.
In the long-term, you’l see that selling rock stable capacity will get you clients.
You can put an aditional network address on your router, and give them all that network for use, put a queue on the whole network, to limit to whatever you want, and you can see then how many computers they use, if they don’t use any router. If they do, you have your money for what you sell, anyway.
What we do is use the hotspot functionality. If a router connects to the network the user is still caught by the hotspot.
At this point they pay for an account and they’re fine for life, or they can’t register (because their router doesn’t work right with the hotspot) and we take care of them. Either way, the hotspot helps keep unwanted customers under control!
The manual said :
new-ttl (decrement | increment | set:integer) - specify the new TTL field value used in conjunction with action=change-ttldecrement - the value of the TTL field will be decremented for value
increment - the value of the TTL field will be incremented for value
set: - the value of the TTL field will be set to value
IMHO i do not know many routers (SOHO) that will change ttl of a packet in prerouting so, unless your client have router that is same level as yours or better you cannot limit them that way. any other crappy router will not be able to change ttl value in time for packet to survive