Re: Bridged vether interfaces can't talk to each other (multiple routing tables)

In case someone finds this thread in the future, I would like to add that I have now received a possible solution to the problem out-of-band. The solution is to use pair(4): The following setup works for me, although it is a bit too convoluted: # cat /etc/hostname.pair0 up # cat

Re: Bridged vether interfaces can't talk to each other (multiple routing tables)

On 22 April 2017 at 04:22, Edgar Pettijohn wrote: > On 04/21/17 20:49, Anders Andersson wrote: >> >> Now to my problem: I have no connection between vether0<->vether1. >> >> # traceroute -nvq1 10.0.0.3 >> traceroute to 10.0.0.3 (10.0.0.3), 64 hops max, 40

Re: Bridged vether interfaces can't talk to each other (multiple routing tables)

On 04/21/17 20:49, Anders Andersson wrote: === BACKGROUND === I'm trying to set up an OpenBSD 6.1 server having two externally visible IP numbers through one physical network port, each IP mapping to a unique MAC address[1]. I have it mostly working, but my interfaces can't talk to each

Bridged vether interfaces can't talk to each other (multiple routing tables)

=== BACKGROUND === I'm trying to set up an OpenBSD 6.1 server having two externally visible IP numbers through one physical network port, each IP mapping to a unique MAC address[1]. I have it mostly working, but my interfaces can't talk to each other. All traffic should use the primary IP, and