captfrito

Okay -- looks like I got caught by a bad batch of network scripts during a routine upgrade: [I] sys-apps/corenetwork Available versions: 1.5.5 1.5.6 1.5.6-r1 1.6.0 1.6.1 Installed versions: 1.6.1(10:43:07 AM 02/04/2017) Homepage: http://www.funtoo.org/Networking Description: Funtoo's networking scripts. I masked 1.6.1 and downgraded (via /etc/portage/mask/misc) [ebuild UD ] sys-apps/corenetwork-1.6.0::gentoo [1.6.1::gentoo] 0 KiB Total: 1 package (1 downgrade), Size of downloads: 0 KiB >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-apps/corenetwork-1.6.0::gentoo >>> Installing (1 of 1) sys-apps/corenetwork-1.6.0::gentoo >>> Jobs: 1 of 1 complete Load avg: 0.41, 0.11, 0.04 >>> Auto-cleaning packages... Then a trusty rc command, and viola! Started right up, just like a '62 Ford: joeperry conf.d # rc * Network interface eth1.1500 up ... [ ok ] * Network interface eth1.2 up ... [ ok ] joeperry conf.d # rc-status Runlevel: default lvm [ started ] syslog-ng [ started ] sshd [ started ] iptables [ started ] in.tftpd [ started ] cronie [ started ] net.eth0 [ started ] net.eth1 [ started ] net.eth1.1500 [ started ] net.eth1.2 [ started ] netmount [ started ] postfix [ started ] vsftpd [ started ] local [ started ] Dynamic Runlevel: hotplugged Dynamic Runlevel: needed lvmetad [ started ] Dynamic Runlevel: manual

Hi All, I had a perfectly working system, rebooted, network scripts suddenly began failing. Not sure why. This is actually a server, not a desktop, so there are no complicated networking GUIs and whatnot, and no wireless. eth0 is a standard L3 interface and works fine: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 0c:c4:7a:6e:a5:04 brd ff:ff:ff:ff:ff:ff inet 172.16.3.213/25 brd 172.16.3.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::332:b96c:8e58:cccb/64 scope link valid_lft forever preferred_lft forever /etc/init.d/net.eth0 -> netif.tmpl /etc/conf.d/net.eth0 template=dhcpcd eth1 is a trunked vlan interface -- this is the one that quit working: 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 0c:c4:7a:6e:a5:05 brd ff:ff:ff:ff:ff:ff inet6 fe80::ec4:7aff:fe6e:a505/64 scope link /etc/init.d/net.eth1 -> netif.tmpl /etc/init.d/net.eth1.1500 -> netif.tmpl /etc/init.d/net.eth1.2 -> netif.tmpl /etc/conf.d/net.eth1 template="interface-noip" /etc/conf.d/net.eth1.1500 template="interface" trunk="net.eth1" vlan="1500" ipaddr="172.16.5.1/25" nameservers="172.16.3.1" domain="whatever.org" /etc/conf.d/net.eth1.2 template="interface" trunk="net.eth1" vlan="2" ipaddr="172.16.6.1/25" nameservers="8.8.8.8" domain="whatever.org" net.eth1 starts like it should. But the vlan interfaces are now complaining about this. I guess I don't understand what the service is that it's looking for: service net.eth1.2 start * ERROR: net.eth1.2 needs service(s) netif.net.eth1 service net.eth1.1500 start * ERROR: net.eth1.1500 needs service(s) netif.net.eth1 even though the eth1 interface is started: service net.eth1 start * WARNING: net.eth1 has already been started As I mentioned this had been working and survived a number of reboots. I am not sure why this is happening, I haven't done anything to the networking for quite a while. Any help is greatly appreciated (-:

I built a PXE server system as described at http://www.funtoo.org/PXE_network_boot_server There were a few things I needed to do differently to get things to work even partially. For example, I needed to add these additional files to my /tftproot: ldlinux.c32 libcom32.c32 libutil.c32 There is another quirk in that the initial menu displayed on the system that is trying to boot via PXE is allowing a 1,000sec timeout versus the 10sec I was expecting via the pxelinux.cfg/default file. The issue I am having now is that I get all the way through the loading of the initrd=srcd/isolinux/initram.igz loading, but then the system trying to boot can never find the netboot=http://172.16.3.213/sysrcd.datfile. What happens instead is that the system booting completes the network configuration via the initrd but then reports Searching for device with /sysrcd.dat It fails to find it, then tries to mount all the SATA partitions (3 disks with a total of 22 partitions among them), then reports again !! Cannot find a device with /sysrcd.dat. Retrying... It does this several times, then gives up dumping me to a "mini shell". I searched the at-large internet, and can't really find anything that helps. I have tried offering the sysrcd.dat and the sysrcd.md5 files via apache and vsftp. Here is the output from tcpdump: bolan tftproot # tcpdump -n port 80 or port 69 dropped privs to tcpdump tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 18:58:46.837984 IP 172.16.3.229.2070 > 172.16.3.213.69: 27 RRQ "pxelinux.0" octet tsize 0 18:58:46.841925 IP 172.16.3.229.2071 > 172.16.3.213.69: 32 RRQ "pxelinux.0" octet blksize 1456 18:58:47.004463 IP 172.16.3.229.49152 > 172.16.3.213.69: 41 RRQ "ldlinux.c32" octet tsize 0 blksize 1408 18:58:47.018249 IP 172.16.3.229.49153 > 172.16.3.213.69: 63 RRQ "pxelinux.cfg/01-00-24-1d-27-ec-7f" octet tsize 0 blksize 1408 18:58:47.018995 IP 172.16.3.229.49154 > 172.16.3.213.69: 51 RRQ "pxelinux.cfg/AC1003E5" octet tsize 0 blksize 1408 18:58:47.019703 IP 172.16.3.229.49155 > 172.16.3.213.69: 50 RRQ "pxelinux.cfg/AC1003E" octet tsize 0 blksize 1408 18:58:47.020374 IP 172.16.3.229.49156 > 172.16.3.213.69: 49 RRQ "pxelinux.cfg/AC1003" octet tsize 0 blksize 1408 18:58:47.021047 IP 172.16.3.229.49157 > 172.16.3.213.69: 48 RRQ "pxelinux.cfg/AC100" octet tsize 0 blksize 1408 18:58:47.021758 IP 172.16.3.229.49158 > 172.16.3.213.69: 47 RRQ "pxelinux.cfg/AC10" octet tsize 0 blksize 1408 18:58:47.022460 IP 172.16.3.229.49159 > 172.16.3.213.69: 46 RRQ "pxelinux.cfg/AC1" octet tsize 0 blksize 1408 18:58:47.023147 IP 172.16.3.229.49160 > 172.16.3.213.69: 45 RRQ "pxelinux.cfg/AC" octet tsize 0 blksize 1408 18:58:47.023822 IP 172.16.3.229.49161 > 172.16.3.213.69: 44 RRQ "pxelinux.cfg/A" octet tsize 0 blksize 1408 18:58:47.024459 IP 172.16.3.229.49162 > 172.16.3.213.69: 50 RRQ "pxelinux.cfg/default" octet tsize 0 blksize 1408 18:58:47.025334 IP 172.16.3.229.49163 > 172.16.3.213.69: 42 RRQ "vesamenu.c32" octet tsize 0 blksize 1408 18:58:47.028685 IP 172.16.3.229.49164 > 172.16.3.213.69: 42 RRQ "libcom32.c32" octet tsize 0 blksize 1408 18:58:47.047745 IP 172.16.3.229.49165 > 172.16.3.213.69: 41 RRQ "libutil.c32" octet tsize 0 blksize 1408 18:58:47.053732 IP 172.16.3.229.49166 > 172.16.3.213.69: 50 RRQ "pxelinux.cfg/default" octet tsize 0 blksize 1408 18:58:47.283029 IP 172.16.3.229.49167 > 172.16.3.213.69: 43 RRQ "netboot-1.png" octet tsize 0 blksize 1408 And here's what happens when I wget the files directly: vaughan ~ # wget 172.16.3.213/sysrcd.md5 . --2017-01-05 23:44:04-- http://172.16.3.213/sysrcd.md5 Connecting to 172.16.3.213:80... connected. HTTP request sent, awaiting response... 200 OK Length: 45 [application/x-md5] Saving to: 'sysrcd.md5' sysrcd.md5 100%[=======================================================================================================================================================>] 45 --.-KB/s in 0s 2017-01-05 23:44:04 (11.8 MB/s) - 'sysrcd.md5' saved [45/45] --2017-01-05 23:44:04-- http://./ Resolving .... failed: No address associated with hostname. wget: unable to resolve host address '.' FINISHED --2017-01-05 23:44:04-- Total wall clock time: 0.02s Downloaded: 1 files, 45 in 0s (11.8 MB/s) Not sure what is happening here, any help is gratefully accepted (-: