So I have two networks.

Network one looks like:
Internal bridge w/local DHCP + single external (NAT'ing for internal)
Tunnel up to Network 2 (EOIP atm)
It also has another network (another DHCP) running on a seperate vlan (servers)
I have no spare IP's usable here.


Network two is a router in a DC, I have a /29 allocated of public ip's.

On network 1 for those servers- i'd like a few of them to have public IP's from Network two.
Basically i'm not sure where to go from there.. I have the tunnel up.

I've tried a bunch of things (including putting the tunnel onto the same bridge as my internal traffic.. tried assigning IP's internally and it doesn't work (I suspect due to NAT.. though im not sure how to fix that.) but it also causes major problems with internet connectivity for other clients on the internal bridge (probably half the internet becomes unresponsive.)

Hope that's clear.

Since you have multiple networks, you should start by ensuring you can ping from a server to router 2. Once that is done, ping from router 2 to the same server. This should be resolved mostly by adding routes.

Once the above is resolved, do some port forwarding to expose services to the internet via Filter rules. There are lots of examples on the forum.
Each to their own, but I am not a fan of exposing a complete server to the internet.

My issue is exactly that. Network one can reach the ip's on network two (e.g placing something in the /29 on the eoip) and server can reach the nearside (e.g if .1 is at network 2 and .2 @ network1- assign server .3) .3 can reach .2 but not gw. but .2 can reach .1 (so router is routing it properly in both directions)