Revolution
Dabbler
- Joined
- Sep 8, 2015
- Messages
- 39
Hey everyone,
I have a rather strange behavior of my c2550d4i motherboard.
First of all, the board has 3 nics,1 for ipmi, one igb0 and one igb1. For the past I just had the igb0 connected on a 192.168.5.0/24 subnet and all is working flawless. Yesterday I thought, since I'm using vlans on my switch and other networks have to go through the firewall to access the Nas, I could just plug the igb1 into one of the other networks to speed up the connection. Well it wasn't that easy.
After I connected the second nic to my 192.168.7.0/24 subnet, the nic wouldn't ask for a ip. So I just went to the cmd and ran dhclient igb1 and got an ip. This is where it gets strange. After doing that, the webgui access to the 5.0/24 subnet was super slow and sporadic, most clicks around the gui would be blank and just very abrupt.So I restarted the machine to see if it fixes it. After doing so nothing changed really. I thought to myself, well then I'll disconnect the link connected to 7.0/24. After doing that, the 5.0/24 nic which worked all the time just wasn't ping able nor did the webgui respond in any way. After a period it would just work again and the sporadic and abrupt webgui was buttersmooth again.
Now my question. What could cause such behavior? These are two separate broadcast domains so and also two separate Mac addresses. My machine from which I connect to the gui is also on the 7.0/24 subnet.
Ultimately I would like to bind only the smb service to the igb1 (7.0/24) nic and the gui and ssh to the management nic. The goal is to get wirespeed smb to the 7.0/24 network without exposing anything else on that subnet.
Maybe someone has an idea how I could debug the behavior
With kind regards
I have a rather strange behavior of my c2550d4i motherboard.
First of all, the board has 3 nics,1 for ipmi, one igb0 and one igb1. For the past I just had the igb0 connected on a 192.168.5.0/24 subnet and all is working flawless. Yesterday I thought, since I'm using vlans on my switch and other networks have to go through the firewall to access the Nas, I could just plug the igb1 into one of the other networks to speed up the connection. Well it wasn't that easy.
After I connected the second nic to my 192.168.7.0/24 subnet, the nic wouldn't ask for a ip. So I just went to the cmd and ran dhclient igb1 and got an ip. This is where it gets strange. After doing that, the webgui access to the 5.0/24 subnet was super slow and sporadic, most clicks around the gui would be blank and just very abrupt.So I restarted the machine to see if it fixes it. After doing so nothing changed really. I thought to myself, well then I'll disconnect the link connected to 7.0/24. After doing that, the 5.0/24 nic which worked all the time just wasn't ping able nor did the webgui respond in any way. After a period it would just work again and the sporadic and abrupt webgui was buttersmooth again.
Now my question. What could cause such behavior? These are two separate broadcast domains so and also two separate Mac addresses. My machine from which I connect to the gui is also on the 7.0/24 subnet.
Ultimately I would like to bind only the smb service to the igb1 (7.0/24) nic and the gui and ssh to the management nic. The goal is to get wirespeed smb to the 7.0/24 network without exposing anything else on that subnet.
Maybe someone has an idea how I could debug the behavior
With kind regards