Y
Y
YujiTFD2013-05-15 07:45:04
Iron
YujiTFD, 2013-05-15 07:45:04

Routing to the subnet of the second provider

Hello.

To offload the main Internet channel, it was decided to transfer some users in test mode to a cable from another provider, for this they purchased Trendnet TW100-BRF114 (at first glance, its capabilities were enough). Inside their subnet, these users work fine, there are no questions, but there is no connection with another subnet (main) connected to one of the TW100-BRF114 LAN ports (specifically, the fourth one).

The network settings are as follows:
- the main subnet is 192.168.62.0/24, the gateway is 192.168.62.1 - you can’t touch it, everything is set up and working, configuration changes are highly undesirable,
- WAN of the router of the second provider - static IP,
- NAT of the router of the second provider - 192.168 .65.0/24, gateway - 192.168.65.1
- prescribed routes TW100-BRF114 of the second provider - 192.168.62.0/24 with a gateway 192.168.65.1.

The router, in theory, has the ability to provide such a connection (there is an opportunity to register static routes to other networks), but there is no de facto packet forwarding. After a long, long wait, I finally managed to get through to Trendnet technical support, where, with 80% confidence in my voice, they told me that there was no such support.

Question: did I formulate the variant of the solution of the issue correctly and how can the task be solved at the lowest cost? Thanks in advance.

PS The described router was returned to the seller, so any working solution is generally welcome; preferably, of course, available at minimal cost.

Answer the question

In order to leave comments, you need to log in

5 answer(s)
S
Sergey Petrikov, 2013-05-15
@YujiTFD

The cheapest option I know to solve such a problem is something like MikroTik RB750. On any Unix, such a task is solved quite simply.

I
Ilya Evseev, 2013-05-15
@IlyaEvseev

+1 for Mikrotik, but keep in mind that their performance is _relatively_ low.
wiki.mikrotik.com/wiki/Load_Balancing_over_Multiple_Gateways

P
PooFF, 2013-05-15
@PooFF

And what kind of route is this: “192.168.62.0/24 with a gateway 192.168.65.1” if 192.168.65.1 is an address on the same router?
In general, on the second router, you need to register ip from 192.168.62.0/24. And do the route on the first router to the network 192.168.65.0/24

L
lmaxximl, 2013-05-15
@lmaxximl

I did everything on this post simply and it works, the main script at startup once, the verification script is constantly in operation.

Y
YujiTFD, 2013-05-15
@YujiTFD

And what kind of route is this: "192.168.62.0/24 with a gateway 192.168.65.1" if 192.168.65.1 is an address on the same router?
This is such a system for writing routing in Trendnet routers - to route to 192.168.62.0/24 through 192.168.65.1, in the webmord help it says directly, translation: “In the GATEWAY field, indicate the IP address of the current router ( not the one that serves the network where routing in progress )
In general, on the second router, you need to register ip from 192.168.62.0/24. And do the route on the first router to the network 192.168.65.0/24
On which interface of the 2nd to register IP from xx62.0/24? The first "router" is FreeBSD, do you have to configure something there? As I understand it, х.х.62.0/24 comes by cable to the second router, as in a regular switch, FreeBSD should not care who exactly on that side the request came from - it is the switch that processes it on the spot (otherwise network branching would not work regular switches). That is, to be able to forward packets to a third-party network and forward responses back - this, in my case, is entirely the task of the second router. I am wrong?

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question