Device with static IP does not work properly (Unbound problem?)

[AxAn]

I don't know what to make of this and I'm not even sure where to start looking.

I have a audio matrix (the t.racks DSP 408) with a static ip.
If I set a static ip on my computer, and connect directly to the DSP, the provided network software for the matrix works perfectly.
If I connect the computer and matrix together using a switch (Netgear GS108) it also works.
If I connect my router, running Opensense (23.1.1_2-amd64) to the same switch I can ping the DSP but not connect using it's software.

My first thought was that there might be another device with the same ip, but there isn't.
Any thoughts about this or where to start looking?

[simonwoodhall]

You could try running 'arp -a' in a command prompt (on Windows) or 'ip neighbour' on Linux and see if the mac address for the IP of your device is the same one you see when the firewall isn't connected to the switch.

[AxAn]

I tried that. The MAC address remains the same.
I cleared out the arp table on my computer between connecting/disconnecting the router:

Code Select Expand

arp -d *

[AxAn]

An update:
I started to disable services and the problem went away when I disabled Unbound.
The only thing I have in Unbound is a mapping for a subdomain to an ip, but if I disable it the problem is still present so I don't thing it has to do with that.

My Unbound config, from backup:

Code Select Expand

    <unboundplus version="1.0.4">
      <service_enabled/>
      <advanced>
        <hideidentity>0</hideidentity>
        <hideversion>0</hideversion>
        <prefetch>0</prefetch>
        <prefetchkey>0</prefetchkey>
        <dnssecstripped>0</dnssecstripped>
        <serveexpired>0</serveexpired>
        <serveexpiredreplyttl/>
        <serveexpiredttl/>
        <serveexpiredttlreset>0</serveexpiredttlreset>
        <serveexpiredclienttimeout/>
        <qnameminstrict>0</qnameminstrict>
        <extendedstatistics>0</extendedstatistics>
        <logqueries>0</logqueries>
        <logreplies>0</logreplies>
        <logtagqueryreply>0</logtagqueryreply>
        <logverbosity>1</logverbosity>
        <privatedomain/>
        <privateaddress>0.0.0.0/8,10.0.0.0/8,100.64.0.0/10,169.254.0.0/16,172.16.0.0/12,192.0.2.0/24,192.168.0.0/16,198.18.0.0/15,198.51.100.0/24,203.0.113.0/24,233.252.0.0/24,::1/128,2001:db8::/32,fc00::/8,fd00::/8,fe80::/10</privateaddress>
        <insecuredomain/>
        <msgcachesize/>
        <rrsetcachesize/>
        <outgoingnumtcp/>
        <incomingnumtcp/>
        <numqueriesperthread/>
        <outgoingrange/>
        <jostletimeout/>
        <cachemaxttl/>
        <cacheminttl/>
        <infrahostttl/>
        <infracachenumhosts/>
        <unwantedreplythreshold/>
      </advanced>
      <dnsbl>
        <enabled>0</enabled>
        <type/>
        <lists/>
        <whitelists/>
        <address/>
      </dnsbl>
      <forwarding>
        <enabled>0</enabled>
      </forwarding>
      <dots/>
      <hosts>
        <host uuid="xxxxxxxxxxx">
          <enabled>1</enabled>
          <hostname>yyyyyy</hostname>
          <domain>xxxxx.com</domain>
          <rr>A</rr>
          <mxprio/>
          <mx/>
          <server>192.168.0.199</server>
          <description>xxxxxx</description>
        </host>
      </hosts>
      <aliases/>
      <domains/>
    </unboundplus>

[simonwoodhall]

You're using only IP address to connect to the device, not hostnames? Seems odd that Unbound would be involved, if it's just by IP address on a flat L2 network.

[AxAn]

I use only IP address to connect to the device.
Maybe it's not Unbound, but disabling it breaks the chain to the actual problem. But I have no clue what it would be.