Thus if in fact the port 0 (first nic) was disabled in the switch, TrueNas might decide it knows a better ip set then I do and reorder the nic's and all of them would be on the wrong vlans talking to the wrong subnets. (now suddenly bge0 is actually bge2) and (bg1 is different and switched to bge3) and (bge 2 is now bge1) and finally (bge3 is bge0) or something similar to that. I later discovered that the reason the web interface would no longer answer was that the ip's that I (the administrator) assigned to specific nic's have been reordered, and therefore the ip's went to different ports. I like to have public ip's accessible to enable if I feel the need. Last thing I had done was change the ip from the 192.168.1.x ip to the true public, add a 3rd ip on port #2 of the 4 available and reboot to make sure all was ok.īefore the lecture starts about not assigning a public ip, if I felt the install was so insecure that it was such a bad thing for the public ip binding, I could easily disable the switch port and only enable it when needed. It is a minimum 4 to 5 hour drive round trip, usually turns in to a much longer trip then that so I most often try to have the majority of setup done in advance. ![]() ![]() I had been preparing a Truenas install for a while and was finally confident the server was ready to take to the data center.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |