(1). My clients sometimes experience slow browsing and I make attempts to troubleshoot in order to see where the problem is from. Whenever I go to Interface > Ethernet > Traffic, I observe that Tx is far way higher than Rx, which I believe is an indication that something is wrong somewhere.
I try to check if one of the LAN PCs is broadcasting by pulling off Ethernet cables from the Switch one after the other. But most times I do not succeed in solving the problem.
From experience, what do u think is responsible for such situation, and how can I resolve it?
(2). Sometimes situations arise whereby I need to restart my MT Router (RB1000 powerpc). Whenever I do so, the clock in the Router resets. This action invalidates the tickets which are created for Hotspot users.
How do I prevent the clock from resetting if I have to restart my Router?
(3). I have the ffg configured on my MikroTik RB1000 powerpc for my Hotspot users:
HOTSPOT:
Hotspot Network Address 192.168.182.1/24
Address Pool of Network 192.168.182.2 - 192.168.182.254
DHCP:
DHCP Network Address 192.168.182.0/24
Gateway for DHCP Network 192.168.182.1
Address Pool for DHCP 192.168.182.2 - 192.168.182.254
I do not like to keep things the way they are presently configured because the IP range is too small to serve a campus environment where u may have hundreds of edge users who may be willing to connect to the network simultenously. I see it as a subnetting problem.
I am considering using a /16 address scheme, but I do not know how to go about it. Can someone help me?
How do I prevent the clock from resetting if I have to restart my Router?
With NTP. Configure it.
that Tx is far way higher than Rx
virus? P2P leechers?
I am considering using a /16 address scheme, but I do not know how to go about it. Can someone help me?
This is easy, when you configure the hotspot, with the wizard, you can select ip 172.26.0.1/ for hotspot and the /16 pool.. all will be automatically configured : P It’s the same configuration like the /24 but using a /16 network.
What’s NTP? Is it a feature on RouterOS? How do I locate and configure it?
Virus, p2p leechers …What’s the best way around if it’s either one or both of them?
If the issue is not an external one (e.g Virus attack, & p2p leechers) as u pointed out, what other internal network factor could be responsible for such occurence?
I was using the ip 192.168.182.0/16 for hotspot initially, so I thought something was wrong ..maybe the ip range is incompatible with the /16 pool (what I see as a subnetting issue). Do u agree with me?
If so, will 172.26.0.1/16 solve the problem?
It’s not necessarily malicious traffic at all. TX/RX is reported from the point of view of the router - RX means receiving traffic from the network (users sending data out to the internet), TX is traffic sent into the network (users receiving data from the internet). For many legitimate use cases, seeing a higher TX than RX is completely expected. It doesn’t take much data for a client to request a web page, for example. The data that makes up the website is much bigger than the request.
192.168.182.0/16 is not a valid network address (it’s a host address on 192.168.0.0/16). If you’re not completely sure on subnetting, using 172.16.0.1/16 instead would work.
My worry about Tx & Rx (Tx being far way higher than Rx), is being expressed from my customer’s/client’s point of view. I manage a network for a WISP and it beholds on me to look for any possible means to address the problem.
I am looking at the problem, from the customer’s side (i.e when I logged-in to the customer’s MT radio).
If I have to go by your points, then what explanation will I have to give to my client/customer that what he/she is receiving from me (Rx) is expected to be less than what he/she is sending out (Tx)?
I hope I make myself clear enough.
Could you pls be more explicit on the point you are trying to make here.
Thanks you guys all along for your logical contributions.
When you’re talking about RX/TX, are you talking about the counters on the router, as they read in the terminal or Winbox? If so, RX means data that the customer sends to the internet, and TX means data sent from the internet to the customer. The router displays the values that way because the interface receives data from the network when the customer sends stuff out and transmits data into the network when the customer is receiving data. It may seem a little counter-intuitive at first, but that’s how most routers display traffic statistics.
The same goes for a wireless interface. When the customer sends a request for a webpage to the internet, that request is received by the wireless interface and the RX counter increases. The website is then served to the customer, and the wireless interface transmits that data to the customer and the TX counter increases.
Requesting google.com takes doesn’t take much: “GET / HTTP/1.0”, for example, with some bytes added for the layers around it. The site itself, though (the HTML that makes up the Google homepage) is obviously much larger. So the TX value is usually larger than the RX value on the router interface when you’re browsing the net.