Results 1 to 2 of 2

Thread: Double intrface name in ifup calls

Hybrid View

  1. #1

    Double intrface name in ifup calls

    Hi,

    I've noticed some strange output in syslog according to the ifup script functioning:

    Code:
    Dec 29 08:15:36 linux-s2kv ifup:     eth0
    Dec 29 08:15:36 linux-s2kv ifup: IP address: ********
    Dec 29 08:15:36 linux-s2kv ifup:  
    Dec 29 08:15:36 linux-s2kv ifup: Handling Index <>:
    Dec 29 08:15:36 linux-s2kv ifup:      IPADDR             = ************
    Dec 29 08:15:36 linux-s2kv ifup:      PREFIXLEN          = 23
    Dec 29 08:15:36 linux-s2kv ifup:      CHECK_DUPLICATE_IP = no
    Dec 29 08:15:36 linux-s2kv ifup-route: eth0 eth0 -o rc onboot
    Dec 29 08:15:36 linux-s2kv ifup-route: calling: ip route replace to default via ********  ---> OK
    Dec 29 08:15:36 linux-s2kv ifup-route: calling: ip -4 route replace to ******* dev eth0  ---> OK
    Dec 29 08:15:36 linux-s2kv ifup-services: eth0 eth0 -o rc onboot
    Dec 29 08:15:36 linux-s2kv ifup-services: unknown option rc
    Dec 29 08:15:36 linux-s2kv ifup-services: No services to handle for 'eth0 eth0'
    I got this using the DEBUG="yes" option in the /etc/sysconfig/network/config file. From this, there are inrorretly called scripts:

    Code:
    Dec 29 08:15:36 linux-s2kv ifup-route: eth0 eth0 -o rc onboot
    Dec 29 08:15:36 linux-s2kv ifup-services: eth0 eth0 -o rc onboot
    I suppose, this is because of this code in the /sbin/ifup script:

    Code:
    if [ -n "$1" -a "$1" != "-o" ] ; then
            CONFIG=$INTERFACE
            INTERFACE=$1
    fi
    
    and then
    
    ...
    ${SCRIPTNAME}-route $CONFIG $INTERFACE ${OPTIONS:+-o $OPTIONS}
    ...
    scripts/${SCRIPTNAME}-services $CONFIG $INTERFACE ${OPTIONS:+-o $OPTIONS}
    Looks like a bug for me, but I can't figure out how to report this to developers?
    Last edited by ivryakhov; 29-Dec-2016 at 14:57.

  2. #2

    Re: Double intrface name in ifup calls

    Quote Originally Posted by ivryakhov View Post
    Looks like a bug for me, but I can't figure out how to report this to developers?
    If you have active maintenance you can open a Service Request. SUSE Support will have a look and, if it is truly a bug, they will create a bug report. If it is not a bug, they may have a solution for you.

    If you don't have maintenance, you can try to file a bug report using Bugzilla.

    A bug report backed by a Service Request that identifies a specific Customer is usually the more effective approach.
    Kevin Boyle - Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below this post. Thanks.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •