Odd problem with interfaces

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Odd problem with interfaces

Rupert Gallagher
I ran out of ideas on the following problem.

An obsd server has tree ethernet interfaces, each with its own IP address:
> cat /etc/hostname.*
inet 192.168.1.2 255.255.255.0 192.168.1.255 mtu 9014 description "em0: MODEM/ROUTER"
inet 192.168.1.3 255.255.255.0 192.168.1.255 mtu 9014 description "em1: CISCO SG110D-08"
inet 192.168.1.4 255.255.255.0 192.168.1.255 mtu 9014 description "em2: NAS"

When all three interfaces are connected, the clients loose NFS services, and scp fails from server to any client (but ssh keeps working). Functionality is recovered by unplugging em0 and em2.
Reply | Threaded
Open this post in threaded view
|

Re: Odd problem with interfaces

Jiri B-2
On Wed, Nov 29, 2017 at 09:56:38AM -0500, Rupert Gallagher wrote:
> I ran out of ideas on the following problem.
>
> An obsd server has tree ethernet interfaces, each with its own IP address:
> > cat /etc/hostname.*
> inet 192.168.1.2 255.255.255.0 192.168.1.255 mtu 9014 description "em0: MODEM/ROUTER"
> inet 192.168.1.3 255.255.255.0 192.168.1.255 mtu 9014 description "em1: CISCO SG110D-08"
> inet 192.168.1.4 255.255.255.0 192.168.1.255 mtu 9014 description "em2: NAS"

^^ using same IP network on 3 ifaces? This is no-go by default.
(If you need that, check rdomains.)

> When all three interfaces are connected, the clients loose NFS
> services, and scp fails from server to any client (but ssh keeps
> working). Functionality is recovered by unplugging em0 and em2.

j.

Reply | Threaded
Open this post in threaded view
|

Re: Odd problem with interfaces

Rupert Gallagher
https://goo.gl/images/eEeb6

Sent from ProtonMail Mobile

On Wed, Nov 29, 2017 at 16:13, Jiri B <[hidden email]> wrote:

> On Wed, Nov 29, 2017 at 09:56:38AM -0500, Rupert Gallagher wrote: > I ran out of ideas on the following problem. > > An obsd server has tree ethernet interfaces, each with its own IP address: > > cat /etc/hostname.* > inet 192.168.1.2 255.255.255.0 192.168.1.255 mtu 9014 description "em0: MODEM/ROUTER" > inet 192.168.1.3 255.255.255.0 192.168.1.255 mtu 9014 description "em1: CISCO SG110D-08" > inet 192.168.1.4 255.255.255.0 192.168.1.255 mtu 9014 description "em2: NAS" ^^ using same IP network on 3 ifaces? This is no-go by default. (If you need that, check rdomains.) > When all three interfaces are connected, the clients loose NFS > services, and scp fails from server to any client (but ssh keeps > working). Functionality is recovered by unplugging em0 and em2. j.
Reply | Threaded
Open this post in threaded view
|

Re: Odd problem with interfaces

Rupert Gallagher
In reply to this post by Jiri B-2
Aaaaaargh! What a day....

https://media.giphy.com/media/AYcqmj0cUar9S/giphy.gif

Sent from ProtonMail Mobile

On Wed, Nov 29, 2017 at 16:13, Jiri B <[hidden email]> wrote:

> On Wed, Nov 29, 2017 at 09:56:38AM -0500, Rupert Gallagher wrote: > I ran out of ideas on the following problem. > > An obsd server has tree ethernet interfaces, each with its own IP address: > > cat /etc/hostname.* > inet 192.168.1.2 255.255.255.0 192.168.1.255 mtu 9014 description "em0: MODEM/ROUTER" > inet 192.168.1.3 255.255.255.0 192.168.1.255 mtu 9014 description "em1: CISCO SG110D-08" > inet 192.168.1.4 255.255.255.0 192.168.1.255 mtu 9014 description "em2: NAS" ^^ using same IP network on 3 ifaces? This is no-go by default. (If you need that, check rdomains.) > When all three interfaces are connected, the clients loose NFS > services, and scp fails from server to any client (but ssh keeps > working). Functionality is recovered by unplugging em0 and em2. j.