twf85
Dabbler
- Joined
- Apr 18, 2019
- Messages
- 14
Before I screw something else up, I thought I might ask for a little guidance. Similar to this thread.
The motherboard in my FreeNAS build has 3 Gbe ports, one of which I believe is meant to allow access to the BIOS via web portal.
Currently, I have one port connected to a Switch and another connected directly to a nearby Windows 10 PC. The other posts I've read (aside from the link above) seem to want to only have a direct link to their FreeNAS box via connected PC (like this thread).
I've bungled it once already and had to visit the box in person to reset Networking, so I'd like to avoid any more of that if possible (though it was good to go through the motions of "recovering" from the error I introduced).
I've manually set the IP address of the NIC in the PC to "10.0.10.1" and the mask to "255.255.255.0". I also added an "IPv4 Alias" to the `igb0` interface (10.0.10.2/24).
If I try to browse "10.0.10.2" from a File Explorer menu, after a time, it does seem like it is connected, but I take that as a false positive. I also tried "10.0.10.3", and got the same result.
I do plan to mitigate the need for this by adding a Managed Switch and a couple of multi-port NICs to both of the boxes; however, for the time being, I'd like to setup an exclusive connection between the two boxes that is independent of the network (without bringing either box off of the network in the process).
I tried reading the Sticky that was kind of up this alley, but I am more or less lost when it comes to LACP/LAGG. I only understand the broad strokes and have no firsthand experience, but I was able to gleam enough from reading it to know that I needed to make sure this new set of NICs were assigned to a different subnet. From what I can gather, things should just "work" if they are setup properly, so I know I'm not doing something right. I don't have a crossover cable, but I could create one if need be.
Apologies in advance if this is a duplicate of an already answered question...
UPDATE:
I added another Interface, this time using the `em0` NIC, and manually set the IP to "10.0.10.2" and netmask to 24. I also changed the PC's NIC to use "10.0.10.2" as the Gateway. That appears to have done the trick.
Forgot to mention, at the start, I added a Firewall Rule to allow connections to the "10.0.10.0/24" subnet.
The only strange thing was that I wasn't able to browse the available Shares. I could ping both ways, so I decided to try mapping a network drive using the alternate IP address (10.0.10.2). Although it took a minute, it did let me add it and the Share was accessible. I ran tests and confirmed that traffic was going out of the intended NIC when using either IP address to send files.
Did I do this right?
The motherboard in my FreeNAS build has 3 Gbe ports, one of which I believe is meant to allow access to the BIOS via web portal.
Currently, I have one port connected to a Switch and another connected directly to a nearby Windows 10 PC. The other posts I've read (aside from the link above) seem to want to only have a direct link to their FreeNAS box via connected PC (like this thread).
I've bungled it once already and had to visit the box in person to reset Networking, so I'd like to avoid any more of that if possible (though it was good to go through the motions of "recovering" from the error I introduced).
I've manually set the IP address of the NIC in the PC to "10.0.10.1" and the mask to "255.255.255.0". I also added an "IPv4 Alias" to the `igb0` interface (10.0.10.2/24).
If I try to browse "10.0.10.2" from a File Explorer menu, after a time, it does seem like it is connected, but I take that as a false positive. I also tried "10.0.10.3", and got the same result.
I do plan to mitigate the need for this by adding a Managed Switch and a couple of multi-port NICs to both of the boxes; however, for the time being, I'd like to setup an exclusive connection between the two boxes that is independent of the network (without bringing either box off of the network in the process).
I tried reading the Sticky that was kind of up this alley, but I am more or less lost when it comes to LACP/LAGG. I only understand the broad strokes and have no firsthand experience, but I was able to gleam enough from reading it to know that I needed to make sure this new set of NICs were assigned to a different subnet. From what I can gather, things should just "work" if they are setup properly, so I know I'm not doing something right. I don't have a crossover cable, but I could create one if need be.
Apologies in advance if this is a duplicate of an already answered question...
UPDATE:
I added another Interface, this time using the `em0` NIC, and manually set the IP to "10.0.10.2" and netmask to 24. I also changed the PC's NIC to use "10.0.10.2" as the Gateway. That appears to have done the trick.
Forgot to mention, at the start, I added a Firewall Rule to allow connections to the "10.0.10.0/24" subnet.
The only strange thing was that I wasn't able to browse the available Shares. I could ping both ways, so I decided to try mapping a network drive using the alternate IP address (10.0.10.2). Although it took a minute, it did let me add it and the Share was accessible. I ran tests and confirmed that traffic was going out of the intended NIC when using either IP address to send files.
Did I do this right?
Last edited: