May 20, 200818 yr Quoting from a previous topic. I would like to reiterate something I said in a post a while ago. I think this is such an important thing for unraid network performance, it should be included in the next version of the web interface. Until I made this change, I was seriously regretting my decision to go with Unraid as my network server. And I'm not sure the nameserver line is important. In my testing, just having the echo 192.168.0.50 tower >> /etc/hosts (substituting my settings of course) line made all the difference in the world. If the nameserver line made any difference, it was in my opinion negligible. Two points here. When setting the network up manually, There should be a field for nameserver (actually two). Also, Update the /etc/hosts file when the interface is enabled and an ip address is acquired (or set manually). I have a small script do this for me now. But it should be a standard update done during the system boot process. root@unraid:/boot/config/rc.local# more S80-update_hosts #!/bin/bash # Fixes /etc/hosts with proper hostname information HOSTNAME=`hostname` if grep $HOSTNAME /etc/hosts >/dev/null then echo "hostname: '$HOSTNAME' already in hosts. skipping" exit fi # Remove this crappy entry. grep -v 'darkstar.example.net' < /etc/hosts > /tmp/hosts # Get current ifconfig information and use it to get address ifconfig | awk -vhostname="$HOSTNAME" ' { # inet addr:192.168.1.178 Bcast:192.168.1.255 Mask:255.255.255.0 # $1 $2 $3 $4 if ( /inet addr:/ && /Bcast:/ && /Mask:/ ) { addr=$2 gsub("addr:","",addr); printf("%s\t%s\n",addr,hostname); } } ' >> /tmp/hosts if ! grep $HOSTNAME /tmp/hosts > /dev/null then printf "127.0.0.1\t%s\n" $HOSTNAME >> /tmp/hosts fi cat /tmp/hosts > /etc/hosts rm -f /tmp/hosts
Archived
This topic is now archived and is closed to further replies.