Easyradius1.6 is the most professional billing system for wayos routing. It supports package binding and new package solution analysis.

Easyradius 1.6 was released two weeks ago. The new 1.6 version mainly updates the billing package, supports user package binding and preferential package usage, and adds cabinet binding.

It may be easy to understand how to bind a cabinet. For example, if a user is in area 1-Cabinet 1, you can bind the recharge card to the cabinet so that the recharge card is provided to the landlord, it cannot be sold across landlords. This is the main problem. If there is no bound card, you can recharge your account at will.

Many people asked haige on QQ: the new rate has changed a lot. Why can't I find the package that can be recharged in the past?

Answer: 1.6 introduces a new model called discount package! For example, the monthly package of 1 m is a billing type, so there may be a 1 m package season, 1 m package year, they are at the same speed (mainly a concept of transition to more than 1.7 regions and second-generation routes), so if the customer pays three months at a time, generally, you will give him a cheaper price, mainly 1 m, so 1 m package year will be regarded as 1 m package monthly sub-plan, also called discount package. The user uses a package for recharging, so that he will bind the package to his current main package, that is, he has charged a 1 m package month today. The next time he recharges the package, he can only charge 1 Mbit/s for 1 Mbit/s or 1 Mbit/s. If you want to recharge 2 Mbit/s, the administrator needs to manually change the billing package in the background. In this way, we can avoid the previous problem: the user uses a 1 Mbit/s card to recharge 2 Mbit/s.

How can I set a discount package? Others are quite simple. Different people have different setting methods. Below I will mainly explain the different setting methods of the same package for two users:

1. Take a closer look. The red is the top-level package, and the gray background below is the discount package. When adding a sub-billing package, you need to select its top-level package, they belong to this package. They are a tree-like relationship.

2. The following user sets his parent package to 0, which means the package level is more obvious, but I do not recommend this. Why? Why is the top-level package actually a Zero Package? This is just an action, and the time and date do not increase. Why can this problem be solved? If some workers do not understand it, the error is also returned, which will increase the number of billing items. Although the amount remains the same, unrelated accounts are a pile, which is ugly.

If you have any problems when using easyradius, you can directly add my QQ. I can help him set multiple package modes based on his needs, because the ER Package function can already meet all the discount packages currently on the market.