1 reputation
1
bio website test
location
age
visits member for 1 year, 11 months
seen Jan 25 '13 at 16:45

Nov
29
comment MAC-Address based routing
i meant it as in layer-2 routing, as in "based on a set of criteria, decide what the destination ethernet-adress of a forwarded ip-packet should be, instead of just checking the arp table".
Nov
29
comment MAC-Address based routing
Nat is not going to work unfortunately, because the services use the bind() socket parameters to propagate the service to third party directories. For instance if i use 192.168.x.x that IP would be propagated to the lookup directory, regardless what kind of NAT-foo i make.
Nov
28
awarded  Editor
Nov
28
comment MAC-Address based routing
yeah ipv6 would obviously be the clean solution, unfortunately that doesnt help me atm because the services cant even use ipv6 yet
Nov
28
revised MAC-Address based routing
added 89 characters in body
Nov
28
comment MAC-Address based routing
i have services i load balance. these services must bind() to a public IP and even establish outgoing connections through this public IP. Due to load balancing the services might end up on different nodes. Due to oforementioned necessity of public IPs, different nodes might have the same ip, for example a service A and B has both bind() to 8.8.8.8 but service B was later migrated to another node.
Nov
28
comment MAC-Address based routing
i am well aware of port forwarding and NAT, but they are no options for me, because the end services have three requirements: 1.) they need to have a public IP and 2.) due to load balancing they may have different mac addreses 3.) due to limited public IPs several machines might have the same ip
Nov
28
asked MAC-Address based routing