Yes, it's on the same box, but because the two boxes are on physically different networks, I can configure them both to be 44.0.0.1 without conflict. One of them won't get any packets except those originating on its own physical network, but they won't conflict. That's what I've done; when the 44/8 route next hop is moved from old amprgw to new amprgw, which machine serves 44.0.0.1 to the outside will automatically change. In the meantime, I was able to connect to the currently unreachable 44.0.0.1 box from itself and browse the web, so I'm fairly confident that it will work when we switch routes. - Brian On Sat, May 27, 2017 at 01:40:59AM +0200, Rob Janssen wrote: