Jump to content

Photo

Network scripts suddenly failing

- - - - -

Best Answer captfrito , 05 February 2017 - 03:37 AM

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

 

Go to the full post »


2 replies to this topic

#1
captfrito

captfrito

    Newbie

  • Members
  • Pip
  • 3 posts

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 (-:

 

 

 



#2
captfrito

captfrito

    Newbie

  • Members
  • Pip
  • 3 posts
✓  Best Answer

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

 



#3
drobbins

drobbins

    Administrator

  • Administrators
  • 136 posts

This should be fixed in corenetwork 1.6.2, hitting the Portage tree soon. Thanks for the report.





Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users