Hi everyone. First of all, I do realize this is most likely incredibly stupid. I do it mostly for fun and learning.
I have two servers, A and B. A has two NICs, one connected to my LAN and one connected to the internet, B has one NIC connected to my LAN.
ServA gets it's public ip address from my ISP using DHCP.
My goal here is to give ServB a public ip address on a virtual/whatever interface. To do this, I must create some form of tunnel between ServA and ServB. Ideally something like epair, but with the two virtual nics on different computers. Like this:
So when I would run
on ServB, it would ask the dhcp server connected to rl0 on ServA.
Is this possible, and if so, how?
I have two servers, A and B. A has two NICs, one connected to my LAN and one connected to the internet, B has one NIC connected to my LAN.
Code:
ServA
rl0: 89.*.*.* (public)
rl1: 192.168.0.100 (lan)
ServB
em0: 192.168.0.128 (lan)
ServA gets it's public ip address from my ISP using DHCP.
My goal here is to give ServB a public ip address on a virtual/whatever interface. To do this, I must create some form of tunnel between ServA and ServB. Ideally something like epair, but with the two virtual nics on different computers. Like this:
Code:
ServA
rl0: 89.*.*.*
rl1: 192.168.0.100
epair0a: (not sure an ip address is needed)
bridge0: members rl0 and epair0a
ServB
em0: 192.168.0.128
epair0b: dhcp
So when I would run
$ dhclient epair0b
on ServB, it would ask the dhcp server connected to rl0 on ServA.
Is this possible, and if so, how?