joelones Posted August 17, 2015 Share Posted August 17, 2015 I'm trying to understand what is causing the delayed IP assignment on boot. If normally take 30 + seconds to acquire an IP despite it being set as static. I have an onboard NIC which I was forced to disable in the BIOS. Now I'm running a e1000 dual Intel NIC. Where eth0 is for unRAID adminstration and eth1 is reserved for a bridge for KVM. Hardware: 5:06.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) (rev 03) 05:06.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) (rev 03) Go file: # unRAID Admin ifconfig eth0 up # bridge for KVM brctl addbr in0 brctl stp in0 on brctl addif in0 eth1 ifconfig eth1 up ifconfig in0 up route add -net 192.168.1.0 netmask 255.255.255.0 dev in0 /boot/config/network.cfg: # Generated settings: USE_DHCP="no" IPADDR="192.168.1.87" NETMASK="255.255.255.0" GATEWAY="192.168.1.1" DHCP_KEEPRESOLV="no" DNS_SERVER1="192.168.1.1" DNS_SERVER2="" DNS_SERVER3="" BONDING="no" BONDING_MODE="1" BRIDGING="no" BRNAME="br0" BRSTP="yes" BRFD="0" Pinging the server on boot I noticed that once it gets to the login screen it's pingable for a brief amount of time and then is not. Then after some 15-30 secs becomes pingable. … ping: sendto: Host is down Request timeout for icmp_seq 66 ping: sendto: Host is down Request timeout for icmp_seq 67 Request timeout for icmp_seq 68 64 bytes from 192.168.1.87: icmp_seq=69 ttl=64 time=0.276 ms 64 bytes from 192.168.1.87: icmp_seq=70 ttl=64 time=0.189 ms Request timeout for icmp_seq 71 Request timeout for icmp_seq 72 Request timeout for icmp_seq 73 Request timeout for icmp_seq 74 Request timeout for icmp_seq 75 Request timeout for icmp_seq 76 Request timeout for icmp_seq 77 Request timeout for icmp_seq 78 Request timeout for icmp_seq 79 Request timeout for icmp_seq 80 Request timeout for icmp_seq 81 Request timeout for icmp_seq 82 Request timeout for icmp_seq 83 Request timeout for icmp_seq 84 Request timeout for icmp_seq 85 Request timeout for icmp_seq 86 Request timeout for icmp_seq 87 Request timeout for icmp_seq 88 Request timeout for icmp_seq 89 Request timeout for icmp_seq 90 Request timeout for icmp_seq 91 Request timeout for icmp_seq 92 Request timeout for icmp_seq 93 Request timeout for icmp_seq 94 Request timeout for icmp_seq 95 Request timeout for icmp_seq 96 Request timeout for icmp_seq 97 Request timeout for icmp_seq 98 Request timeout for icmp_seq 99 Request timeout for icmp_seq 100 64 bytes from 192.168.1.87: icmp_seq=101 ttl=64 time=0.443 ms 64 bytes from 192.168.1.87: icmp_seq=102 ttl=64 time=0.304 ms 64 bytes from 192.168.1.87: icmp_seq=103 ttl=64 time=0.267 ms 64 bytes from 192.168.1.87: icmp_seq=104 ttl=64 time=0.298 ms 64 bytes from 192.168.1.87: icmp_seq=105 ttl=64 time=0.286 ms 64 bytes from 192.168.1.87: icmp_seq=106 ttl=64 time=0.284 ms 64 bytes from 192.168.1.87: icmp_seq=107 ttl=64 time=0.195 ms Link to comment
joelones Posted August 19, 2015 Author Share Posted August 19, 2015 I've managed to temporary solve this by adding a line in the /boot/config/network.cfg IFNAME="eth0" I'm not sure whether this is good practice or not - to manual edit the network.cfg. But now, I'm not experiencing the assignment delay on boot. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.