Julian Hagenauer wrote:
Hi
If you packet would make it to the router and the router had this configuration:
- eth0: 192.168.1.0/24
- eth1: 192.168.1.0/24
the router cannot distinguish the subnets.
Why so complicated.
eth0: 192.168.1.4
eth1: 192.168.1.4
(Hostbased routing) would be enough. Sure the router can not distinguish between the IPs, but he could distinguish between the MACs, so would it be possible to do Masquerading based on MAC-Adresses?
But you'd not even get that far.
When you send a packet from a client to the server and this server has same IP
as the client (thus src and dst IP are the same), then the packet wouldn't
even make it to the router: it would be sent to itself.
Mhm, i don't understand that. Let me explain my setup in greater detail:
Server1---------|
|
|
|
Server2-------Router-------Client
|
|
DB
I want that Server 1 and Server2 have the same IP, although only Server1 should be accessible for clients.
The reason for that is, that i want do some kind of load-balancing.
The problem is, that both Servers need permanent access to the db, so the router should somehow translate/masquerade the ip of the server2, so that both servers can access the db at the same time.
Give both servers their own IP. Give one of the servers also the IP the
clients use to access the server. When that server fails, assign that IP
to the second server (also as secondary!) instead.
M4
