How to turn 46 internet lines into 46 different wi-fi?

Question

C++ / C#

Hello dear experts and lovers of delights!
Task: 46 lines (different wires) of the Internet from the provider (ip speaker, each line has its own ip) need to be distributed to 46 different wi-fi devices (for example, on iPhones). It is important that 1 SP strictly receives 1 iPhone, that is, you need 46 Wi-Fi at the same time.
What piece of iron will pull this? I am looking towards buying 2 MikroTik CRS125-24G-1S-2HND-IN 802.11n. But I heard this fighter can not cope with the load of multiple wifi connections. It is also interesting to scale up to 100 or more simultaneous Wi-Fi.
Any advice please)

Answer 1

1. Start reading Roy's book about "Art of Unit testing" there is already a 2nd edition
2. Read the comment on ru_SO
now regarding your methods. For example, I saw the following test execution log:

AddData_ShouldReturnError() - Failed
AddData_ShouldReturnException() - Failed

What is to be concluded from these errors?
I'm trying to read the title of the test: "The AddData method must return an error."
What happened is not clear to me. Some questions:
* What test data is being served?
* What is the initial state?
* What is considered a mistake? Maybe an entry in the error log, or maybe an incorrect value returned by the method? Or maybe the method should return False in case of an error?
Here's an example of what to aim for:
InvalidAdminToken_UsersRequest_ListIsEmpty
The name of the test follows the naming scheme:
[When]_[Act]_[Then]
Having agreed with the team or yourself about the naming scheme for the tests, you can read the name like this:
Test: Wrong token supplied in request to get users and should get an empty list.
If it suddenly fell, then you will immediately understand that the list is not empty! Because the test method contains only and only asserts, so your test code running in the Act part is wrong!
*UPD*
Any unit test should work according to the AAA design pattern - Arrange -> Act -> Assert. Those. Preparation for testing - Execution of the tested code - Checking the results.
Technically, the work of a unit test is organized like this:
setUp() is preparation for testing, i.e. Arrange
test() - Here Act and Assert
Yes, in a unit test, preparation is written only and only in the setUp() method! An error in preparing the test environment should not affect the test method itself.
A test method is not a preparation of the result, it is a test of the WORK of your COMBAT code.
It is important. Very often I see when small pieces of code preparing test data are shoved into test methods. It is not right!!!
The test method is:
Run the combat code first. For the sake of it, the test method is written.
The second thing is one assert . Yes, the test method should contain ONLY and only one test!
In other words, it shouldn't be like this:

assertTrue(usersList is not None)
assertTrue(usersList.isEmpty)

Answer 2

46 wifi?! Kill the whole broadcast, you won’t be able to sniff. In principle, a good option would be something like this:
- 48-port L2 switch, 46 ports for the Internet, port 47 for a router with a trunk network card
- another switch for ONE Wi-Fi and the internal network of the router
- some kind of iPhone authorization system on Wi-Fi so that each iPhone receives its own personal address
- 46 SNAT rules on the router, each IP address of the internal network to a specific IP connection on the router
- 46 vlans are cut on the external interface of the router, each virtual network interface is configured for a specific line of a specific provider

Answer 3

What piece of iron will pull this?

Yes, anyone who can create more than one access point.

But I heard this fighter can not cope with the load of multiple wifi connections.

Not true.
You can not cope with a lot of connections for two reasons -

• The most popular - a lot of connections tritely pollute the air to the point of impossibility to work. Here it does not depend on the piece of iron at all, any one cannot cope.
  
• The processor cannot cope with processing packets, in particular with encryption - well, this is clearly not the case.
  

It is also interesting to scale up to 100 or more simultaneous Wi-Fi.

Yes, don't care, in principle. There are not so many overhead costs for creating an access point - well, there will be more beacons to send out, more to spoil on the air. Therefore, scale to health. Only it is not clear why it is such happiness?
In general, there is no difference in terms of load between the case when you have 1 access point and 5 clients and the case when you have 5 access points and 5 clients.

Answer 4

Yeah) In general, I decided to do it according to the old-fashioned way and start small, 20 routers. Here is a screenshot from colleagues:
And everything works great.