I experienced a power outage the other night, and I've been going crazy with regard to my server ever since. I was unable to connect to it via samba or putty, so I dug out a keyboard and started poking around. This was the output of ifconfig:

 

eth0      Link encap:Ethernet  HWaddr 00:17:31:15:da:8a  
          inet addr:169.254.8.9  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:6898 (6.7 KiB)
          Interrupt:19 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)

 

I checked my /boot/config/network.cfg file, but it looked fine to me:

 

# Generated network settings
USE_DHCP=yes
IPADDR=
NETMASK=
GATEWAY=

 

I am running 5.0-beta14. I should note that my server is connected to my home network with a powerline ethernet adapter, but I don't think that's the issue; my laptop got an IP address within my range when I plugged it in.

 

The router that my ISP gives out seems pretty restrictive in terms of settings, but it has these values set:

 

Modem IP Address: 192.168.2.1

Modem Subnet Mask: 255.255.255.0

 

DHCP Server: Enable

 

Beginning IP Address: 192.168.2.10

Ending IP Address: 192.168.2.254

Subnet Mask: 255.255.255.0

 

Any insight would be appreciated.

 

Cheers,

Scott

log.txt

I wonder where the 169.254.. address came from?

 

In general, it is not a good idea to you dynamic addresses for servers - set:

 

USE-DHCP=NO
IPADDR=192.168.2.2
NETMASK=255.255.255.0
GATEWAY=192.168.2.1

 

and your network behaviour should be more predictable.

169.254.x.x is auto configuration when a machine is set to use dhcp, but is unable to retrieve an ip address.  Try setting it to use a static IP address in your range but not one of the first few IP addresses as more than likely your router has handed those out.  You can change your router to use a smaller range of ip addresses so that you can assign static IP's to any servers (like unraid) that you have:

http://en.wikipedia.org/wiki/Private_network

 

 

In IPv4, link-local addresses are codified in RFC 5735 and RFC 3927. Their utility is in self-autoconfiguration by network devices when Dynamic Host Configuration Protocol (DHCP) services are not available and manual configuration by a network administrator is not desirable.

 

The block 169.254.0.0/16 is reserved for this purpose, with the exception of the first and the last /24 subnets in the range. If a host on an IEEE 802 (ethernet) network cannot obtain a network address via DHCP, an address from 169.254.1.0 to 169.254.254.255 may be assigned pseudorandomly. The standard prescribes that address collisions must be handled gracefully.

I wonder where the 169.254.. address came from?

 

In general, it is not a good idea to you dynamic addresses for servers - set:

 

USE-DHCP=NO
IPADDR=192.168.2.2
NETMASK=255.255.255.0
GATEWAY=192.168.2.1

 

and your network behaviour should be more predictable.

 

Creating a static DHCP reservation in the router is more flexible.

Creating a static DHCP reservation in the router is more flexible.

 

Of course ... and is what I normally recommend but, in this case, dhcp assignment appears to have failed.

Try setting it to use a static IP address in your range but not one of the first few IP addresses as more than likely your router has handed those out.

 

Errr .... Scottathon told us:

DHCP Server: Enable

Beginning IP Address: 192.168.2.10
Ending IP Address: 192.168.2.254
Subnet Mask: 255.255.255.0

 

Therefore dynamic addresses are only assigned from 192.168.2.10 upwards.  192.168.2.2 - 192.168.2.9 are available for static assignment.

uh, ok.   

 

lost track of the range he told us.  doesn't matter all that much as i doubt very much he has enough hosts to use up from .10 through .254.

 

Thanks guys. Setting the static IP has resolved it.