ISP, DNS or what?

Comments

3 comments

  • Avatar
    Bdeboer

    I think this is solved.  When I setup the NAT rule, I set it for the device name, which I believe is derived from the MAC address.  When the device was upgraded and rebooted, it changed it's MAC address, and thus turning off the NAT rule, which is why it wasn't showing up in external port scans.  I have changed the NAT rule to be pointing to the IP address now, which seems to have solved my problems.

     

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    Can you turn off MAC randomization on your device? with that on, even the IP address assigned to it may change (unless you configure static IP)

     

    0
    Comment actions Permalink
  • Avatar
    Bdeboer

    I am not so sure how to do it, or even if I need to do it. It is my server that is running Unraid, which I just updated to 6.12.3 version last night, which is what changed the MAC address.  I think this might have something to do with the latest problems that they were having with macvlan/ipvlan.  Before now, this wasn't an issue.  I have searched MAC randomization on Unraid and got nothing back.  I already have the server on a static IP, so I am fine using the firewall rule linked to that static IP.  

    0
    Comment actions Permalink

Please sign in to leave a comment.