Visit Open-E website
Results 1 to 10 of 11

Thread: Target IP Access Not Working Right

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default

    LOL. Actually I was wrong. Entering multiple single addresses appears to work in the deny list. However, it doesn't actually deny any of them. It only works when a single entry is put in there (which doesn't help me).

    Play around with it, and actually check to see if it is allowing or denying what it says. The whole thing is screwed up.

  2. #2

    Default

    You are correct I have the same issue with the following. Not many people use this and researching the database never really came up with anything. Thanks for the research and sorry for the frustration. I checked with engineering and not sure if there will be an update to this - no set time table.

    Does not work to allow 192.168.0.204 access.

    Deny access: 192.168.0.0/24
    Allow access: 192.168.0.204;192.168.0.205


    Does work:

    Deny access: 192.168.0.0/24
    Allow access: 192.168.0.204
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  3. #3

    Default

    The thing is I ditched my swich and removed all the NIC bonding. Basically, I have two NICs per client. So now I am having two targets (one for each NIC) and striping them with software on the client end.

    The problem is my initiator doesn't allow me to pick which NIC to use for which target. The only way to make it work properly is to block the relative IP addresses from the target.

    Thanks for looking into it.

  4. #4

    Default

    I know in MS Initiator you can specify which nic in the advanced setting - at least in 2.02 and above. Not sure about MAC's.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •