| 1 |
> |
| 2 |
> I have two questions: |
| 3 |
> |
| 4 |
> |
| 5 |
> |
| 6 |
> 1. Is it feasible to have both Ethernets connect, directly or indirectly, |
| 7 |
> to the same DSL modem/router? (Adam seemed to imply that he operates this |
| 8 |
> way). The device is a Billion Bipac 8900AX R2, which can segregate LAN |
| 9 |
> ports, but as far as I can see it can't assign different IP addresses to |
| 10 |
> them. |
| 11 |
> |
| 12 |
|
| 13 |
What are you trying to achieve with that setup? In the general case, you |
| 14 |
wouldn't do that. |
| 15 |
|
| 16 |
> |
| 17 |
> |
| 18 |
> 2. How should I set up routing on the web server so that outgoing traffic |
| 19 |
> from itself is routed as follows: |
| 20 |
> |
| 21 |
> |
| 22 |
> |
| 23 |
> (i) if the destination is in the 192.168.1.0/24 subnet, the packet should |
| 24 |
> go out through enp2s0, and |
| 25 |
> |
| 26 |
> (ii) traffic to all other destinations goes out through enp1s0? |
| 27 |
> |
| 28 |
|
| 29 |
|
| 30 |
If server has an address on 192.168.1.0/24, then it has a "connected" route |
| 31 |
automatically created by the OS, and that will be preferred over other |
| 32 |
routes. No change required. |
| 33 |
|
| 34 |
If the server is not directly connected to 192.168.1.0/24, then you will |
| 35 |
need a static route to get to it. The gateway for that route will be an IP |
| 36 |
address on a subnet that both the server and the router have an address on. |
| 37 |
The router will also have an address on 192.168.1.0/24. |
| 38 |
|
| 39 |
|
| 40 |
For (ii) you set the default route out that interface. |
Archives