February 6, 201313 yr Hello, Iam new to unraid, but so far it goes pretty wel. The array is build and running fine. But when adding plugins its needed to have internet on the machine. I have manually changed the network.cfg to the following: # Generated settings: USE_DHCP="no" IPADDR="192.168.0.50" NETMASK="255.255.255.0" GATEWAY="192.168.0.1" DHCP_KEEPRESOLV="no" DNS_SERVER1="192.168.0.1" DNS_SERVER2="8.8.8.8" DNS_SERVER3="8.8.4.4" then i restarted the machine and all goes well. exept it will not use my dns server settings. in the webgui i see 169.254.233.207 insted of the dns i have manually put in. What is going wrong. This way i cant install much plugins, like crashplan. pls help, i already restarted the machine a dozen times and tried to set dhcp but that also doesnt work anymore. at least not for dns.
February 6, 201313 yr Replace the network.cfg with the distribution default. Add the static settings using the webGUI.
February 8, 201313 yr Author Well i did a total reinstall with the latest unraid 5.0-rc11. And it did work after using dhcp. then i set the ip to static with the webgui. that worked. But now i have shutdown the machin last night and put it on again this morning and the dns value is back to: 169.254.233.207 its so weird. i have totally no idea whats happening. when i have a look in the network.cfg its looking like this: # Generated settings:^M USE_DHCP="no"^M IPADDR="192.168.0.50"^M NETMASK="255.255.255.0"^M GATEWAY="192.168.0.1"^M DHCP_KEEPRESOLV="no"^M DNS_SERVER1="62.179.104.196"^M DNS_SERVER2="213.46.228.196"^M DNS_SERVER3=""^M When i edit the network settings in the web gui it is saving the network.cfg. But in the interface its not showing the new settings. It keeps showing: 169.254.233.207 Enyone has an idea whats going on? the only plugins i have installed are: Crashplan-0.2-i468-1atv.plg opensshd-0.6-i486-rj.plg simpleFeatures.core.webGUI-1.0.5-noarch-1.plg simpleFeatures.system.stats-1.0.5-noarch-1.plg i tried to install only the most nessesary plugins. btw it also happend to me before on another usb stick. I bought a new cruzer and installed it fresh and added the plus.key i bought. So i don tthink its the usb key. But somehting is interfering i guess. Any ideas are welcome! Cause its really annoying there is not internet connection available on the machine.
February 8, 201313 yr Does your router allow you to set the IP to be used for specific Mac addresses? If so then a workaround is to use that facility and leave the unRAID server set to use DHCP. That is what I do on my own network.
February 8, 201313 yr Author smart idea, i have already looked into it aswell, but my router from my isp is not so smart
February 9, 201313 yr Author Well i did rename the plugin folder and restarted the machine up, but its still showing: 169.254.233.207 I also checked the network.cfg and it is still showing this: # Generated settings:^M USE_DHCP="no"^M IPADDR="192.168.0.50"^M NETMASK="255.255.255.0"^M GATEWAY="192.168.0.1"^M DHCP_KEEPRESOLV="no"^M DNS_SERVER1="62.179.104.196"^M DNS_SERVER2="213.46.228.196"^M DNS_SERVER3=""^M the stupid thing is i tried to change the static ip adres and that is working. the ip is no 192.168.0.15. it is really driving me crazy. the machine does save the new config throught the webinterface and any other way. But the webinterface is not using the dns config and not showing it right. --edit 1-- Now tried to set all to dhcp and reboot the machine. this is now the outcome: # Generated settings:^M USE_DHCP="yes"^M IPADDR="192.168.0.15"^M NETMASK="255.255.255.0"^M GATEWAY="192.168.0.1"^M DHCP_KEEPRESOLV="no"^M DNS_SERVER1="169.254.233.207"^M DNS_SERVER2=""^M DNS_SERVER3=""^M what is really strange. because the webinterface is showing the attachment. so it looks like the machine is not using the network.cfg anymore. but somehow knowing that it should get an dhcp address --edit2-- this time i copied the code from the default network.cfg showing like this: # Generated network settings USE_DHCP=yes IPADDR= NETMASK= GATEWAY= i reboot the machine and the outcome is the same. the webinterface is still showing the same as the attachment. --edit3-- oke i have taken a look into the syslog and i saw this related to dns. emhttp: Start AVAHI... Feb 9 04:34:18 Tower emhttp: shcmd (9): /etc/rc.d/rc.avahidaemon start |& logger Feb 9 04:34:18 Tower logger: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Feb 9 04:34:18 Tower avahi-daemon[6723]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Feb 9 04:34:18 Tower avahi-daemon[6723]: Successfully dropped root privileges. Feb 9 04:34:18 Tower avahi-daemon[6723]: avahi-daemon 0.6.31 starting up. Feb 9 04:34:18 Tower avahi-daemon[6723]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Feb 9 04:34:18 Tower avahi-daemon[6723]: Successfully called chroot(). Feb 9 04:34:18 Tower avahi-daemon[6723]: Successfully dropped remaining capabilities. Feb 9 04:34:18 Tower avahi-daemon[6723]: No service file found in /etc/avahi/services. Feb 9 04:34:18 Tower avahi-daemon[6723]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.50. Feb 9 04:34:18 Tower avahi-daemon[6723]: New relevant interface eth0.IPv4 for mDNS. Feb 9 04:34:18 Tower avahi-daemon[6723]: Network interface enumeration completed. Feb 9 04:34:18 Tower avahi-daemon[6723]: Registering new address record for 192.168.0.50 on eth0.IPv4. Feb 9 04:34:18 Tower avahi-daemon[6723]: Registering HINFO record with values 'I686'/'LINUX'. Feb 9 04:34:18 Tower emhttp: shcmd (10): /etc/rc.d/rc.avahidnsconfd start |& logger Feb 9 04:34:18 Tower logger: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Feb 9 04:34:18 Tower avahi-dnsconfd[6733]: Successfully connected to Avahi daemon. Feb 9 04:34:18 Tower emhttp: shcmd (11): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Feb 9 04:34:18 Tower avahi-daemon[6723]: Files changed, reloading. Feb 9 04:34:18 Tower avahi-daemon[6723]: Loading service file /services/smb.service. Feb 9 04:34:18 Tower emhttp: auto start disabled Feb 9 04:34:18 Tower avahi-dnsconfd[6733]: New DNS Server 169.254.233.207 (interface: 2.IPv4) Feb 9 04:34:19 Tower avahi-daemon[6723]: Server startup complete. Host name is Tower.local. Local service cookie is 949352064. Feb 9 04:34:19 Tower avahi-daemon[6723]: Service "Tower-SMB" (/services/smb.service) successfully established. Feb 9 04:34:19 Tower avahi-dnsconfd[6733]: New DNS Server 169.254.233.207 (interface: 2.IPv4) Feb 9 04:34:30 Tower emhttp: shcmd (12): rmmod md-mod |& logger Feb 9 04:34:30 Tower emhttp: shcmd (13): modprobe md-mod super=/boot/config/super.dat slots=6 |& logger Feb 9 04:34:30 Tower kernel: md: unRAID driver removed Feb 9 04:34:30 Tower emhttp: shcmd (14): udevadm settle Feb 9 04:34:30 Tower kernel: md: unRAID driver 2.1.5 installed Feb 9 04:34:30 Tower emhttp: Device inventory: does anyone see something weird?
February 9, 201313 yr Those screen shots show the system set to use DHCP! If you want to set the address manually, then the options to get the address automatically should be set to No.
February 9, 201313 yr Author Well i tried manual, and dhcp. and dhcp seems even more a pain.. i have no idea why its not working. it did work for a little on dhcp bu then it was back to: 169.254.233.207
February 9, 201313 yr Well i tried manual, and dhcp. and dhcp seems even more a pain.. i have no idea why its not working. it did work for a little on dhcp bu then it was back to: 169.254.233.207 Looking at my setup, I am doing what you're trying to do ... static IPs all around. My network.cfg hasn't been modified since May of 2012, and I've rebooted dozens of times since then. Here's what I suggest: 1) Set the static IP the way you want, and note the date/timestamp on network.cfg. 2) Do a fresh reboot, such that it changes things to 169.x.x.x. 3) Post a full syslog from that boot session. 4) Post the old and new date/timestamp on network.cfg. 5) Post your 'go' file as well, might be interesting if things are changing upon boot.
February 9, 201313 yr Author Atm it is working with dhcp. i did a reboot on my modem and switch and unraid machine. This is how it looks right now. (see attchment) but the network.cfg looks like this atm: # Generated settings:^M USE_DHCP="yes"^M IPADDR="192.168.0.37"^M NETMASK="255.255.255.0"^M GATEWAY="192.168.0.1"^M DHCP_KEEPRESOLV="no"^M DNS_SERVER1="169.254.233.207"^M DNS_SERVER2=""^M DNS_SERVER3=""^M so it seems its not using it. since i had to do a hard reboot their is now a parity sync in progress. iam not sure i should stop this. i will try your suggestions when parity is clear again.
February 16, 201313 yr Author Oke this is what i did. I set the static info in the webgui and checked the network.cfg. the network.cfg changed at: 17:48 to: # Generated settings: USE_DHCP="no" IPADDR="192.168.0.37" NETMASK="255.255.255.0" GATEWAY="192.168.0.1" DHCP_KEEPRESOLV="no" DNS_SERVER1="8.8.8.8" DNS_SERVER2="8.8.4.4" DNS_SERVER3="" then i did reboot and the config has the same timestamp of : 17:48 so there is nothing changed to it. so the code in network.cfg is still: # Generated settings: USE_DHCP="no" IPADDR="192.168.0.37" NETMASK="255.255.255.0" GATEWAY="192.168.0.1" DHCP_KEEPRESOLV="no" DNS_SERVER1="8.8.8.8" DNS_SERVER2="8.8.4.4" DNS_SERVER3="" but the webinterface is showing the attachment with the ip; 169.254.233.207 the syslog is attached. why is it not setting up the fixed dns records and uses some stupid weird ip. syslog.txt
February 16, 201313 yr Author Oke i did rename: plugins -> plugins.bak extra -> extra.bak packages ->packages.bak and i put back the stock go file now its rebooting. attached in the attachment is the new syslog the network.cfg says this: # Generated settings: USE_DHCP="no" IPADDR="192.168.0.37" NETMASK="255.255.255.0" GATEWAY="192.168.0.1" DHCP_KEEPRESOLV="no" DNS_SERVER1="8.8.8.8" DNS_SERVER2="8.8.4.4" DNS_SERVER3="" and the web gui says 192.168.0.31 so its just not taking over the network.cfg dns setting syslog.txt
February 16, 201313 yr Author oke this is what i did next. i have a isp modem router a gig ethernet switch and a airport extreme. this extreme is setup to act as bridge and has a ipv6 tunnel connection and was connected to the switch. what i did was remove the export extreme for now from the network. so only the modem and the switch are active. then i setup the network config static again and did a reboot and now it is keeping the adress: 8.8.4.4 so i think the airport extreme is somehow messing with the network.
Archived
This topic is now archived and is closed to further replies.