Results 1 to 6 of 6

Thread: unable to add default route

  1. #1

    Default unable to add default route

    Hi, i am new here

    currently running leap on my lenovo T410, it runs well except sometimes i got blank screen follow by shutdown.
    well not big issue for me...

    I want to build home server using leap, no problem with installing.

    i setup dhcp via YasT. i plugged on LAN cable then i got nothing from dhcp server.
    i tried to reboot pc, re setup dhcp server on router, still pc didn't receive IP from server.

    at first i disable NM, use wickedd, then i switch to NM, still dont get Ip

    i tried to add default route manual from konsole

    # route add default gw 192.168.2.1 eth0

    and voila i got ip, default route and have internet access
    but when pc reboot, the default route went missing, it went back to default with no ip and default gateway

    btw i bought 1 new motherboard, i thought its hardware issue, now i think its not related to motherboard

    here networkmanager status before i manual add default route

    Code:
    ruko:/etc/NetworkManager # systemctl status NetworkManager
    ● NetworkManager.service - Network Manager
       Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
       Active: active (running) since Thu 2018-02-01 22:34:10 WIB; 4min 47s ago
     Main PID: 943 (NetworkManager)
        Tasks: 4 (limit: 512)
       CGroup: /system.slice/NetworkManager.service
               ├─ 943 /usr/sbin/NetworkManager --no-daemon
               └─1083 /sbin/dhclient -d -q -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-eth0.pid -lf /var/lib/NetworkManager/dhclient-5b94c7f2-1cd7-419e-9e3c-660cc9d27b7c-eth0.lease -cf /...
    
    Feb 01 22:34:18 ruko NetworkManager[943]: <warn>  platform-linux: do-add-ip4-route: failure adding ip4-route '2: 0.0.0.0/0 100': Invalid input data or parameter (7)
    Feb 01 22:34:18 ruko NetworkManager[943]: <warn>  default-route: failed to add default route 0.0.0.0/0 via 192.168.2.0 dev 2 metric 100 mss 0 src user with effective metric 100
    Feb 01 22:34:18 ruko NetworkManager[943]: <info>  (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    Feb 01 22:34:18 ruko NetworkManager[943]: <info>  (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    Feb 01 22:34:18 ruko NetworkManager[943]: <info>  (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    Feb 01 22:34:18 ruko NetworkManager[943]: <info>  NetworkManager state is now CONNECTED_LOCAL
    Feb 01 22:34:19 ruko NetworkManager[943]: <info>  (eth0): Activation: successful, device activated.
    Feb 01 22:34:19 ruko NetworkManager[943]: <info>  startup complete
    Feb 01 22:34:19 ruko NetworkManager[943]: <info>  connectivity: check for uri 'http://conncheck.opensuse.org' failed with 'Error resolving 'conncheck.opensuse.org': Name or service not known'
    Feb 01 22:34:44 ruko NetworkManager[943]: <info>  connectivity: check for uri 'http://conncheck.opensuse.org' failed with 'Error resolving 'conncheck.opensuse.org': Name or service not known'
    Hint: Some lines were ellipsized, use -l to show in full.
    this is after i add default route
    Code:
    ● NetworkManager.service - Network Manager
       Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
       Active: active (running) since Thu 2018-02-01 22:39:11 WIB; 3s ago
     Main PID: 1761 (NetworkManager)
        Tasks: 5 (limit: 512)
       CGroup: /system.slice/NetworkManager.service
               ├─1761 /usr/sbin/NetworkManager --no-daemon
                └─1768 /sbin/dhclient -d -q -sf /usr/lib/nm-dhcp-helper -pf  /var/run/dhclient-eth0.pid -lf  /var/lib/NetworkManager/dhclient-2e6c926f-f803-42f3-94eb-8fa184074d63-eth0.lease  -cf /...
    
    Feb 01 22:39:11 ruko NetworkManager[1761]:  <info>  (eth0): device state change: config -> ip-config  (reason 'none') [50 70 0]
    Feb 01 22:39:11 ruko NetworkManager[1761]: <info>  Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
    Feb 01 22:39:11 ruko NetworkManager[1761]: <info>  dhclient started with pid 1768
    Feb  01 22:39:11 ruko NetworkManager[1761]: <info>  (eth0): device  state change: ip-config -> ip-check (reason 'none') [70 80 0]
    Feb 01 22:39:11 ruko NetworkManager[1761]: <info>  ModemManager available in the bus
    Feb  01 22:39:11 ruko NetworkManager[1761]: <info>  (eth0): device  state change: ip-check -> secondaries (reason 'none') [80 90 0]
    Feb  01 22:39:11 ruko NetworkManager[1761]: <info>  (eth0): device  state change: secondaries -> activated (reason 'none') [90 100 0]
    Feb 01 22:39:11 ruko NetworkManager[1761]: <info>  NetworkManager state is now CONNECTED_SITE
    Feb 01 22:39:11 ruko NetworkManager[1761]: <info>  (eth0): Activation: successful, device activated.
    Feb 01 22:39:13 ruko NetworkManager[1761]: <info>  NetworkManager state is now CONNECTED_GLOBAL
    [/CODE]

  2. #2

    Default Re: unable to add default route

    this is journalctl log
    Code:
    Feb 01 03:15:26 ruko wickedd-dhcp4[1053]: eth0: Request to release DHCPv4 lease with UUID a21d725a-effb-0500-2104-00000a000000: releasing...
    Feb 01 03:16:02 ruko wickedd-dhcp4[1046]: eth0: Request to acquire DHCPv4 lease with UUID 0024725a-268d-0500-1d04-000005000000
    Feb 01 03:16:02 ruko wickedd[1053]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/24 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 03:16:02 ruko wickedd[1053]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 03:16:08 ruko wickedd-dhcp4[1046]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 03:16:08 ruko wickedd[1053]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 03:23:54 ruko wickedd-dhcp4[1046]: eth0: Request to release DHCPv4 lease with UUID 0024725a-268d-0500-1d04-000005000000: releasing...
    Feb 01 03:24:30 ruko wickedd-dhcp4[933]: eth0: Request to acquire DHCPv4 lease with UUID fc25725a-5039-0100-d203-000005000000
    Feb 01 03:24:30 ruko wickedd[978]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/24 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 03:24:30 ruko wickedd[978]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 03:24:34 ruko wickedd-dhcp4[933]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 03:24:35 ruko wickedd[978]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 03:31:50 ruko wickedd-dhcp4[933]: eth0: Request to acquire DHCPv4 lease with UUID fc25725a-5039-0100-d203-000005000000
    Feb 01 03:31:54 ruko wickedd-dhcp4[933]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 03:31:55 ruko wickedd[978]: route ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease
    Feb 01 03:32:46 ruko wickedd-dhcp4[933]: eth0: Request to release DHCPv4 lease with UUID fc25725a-5039-0100-d203-000005000000: releasing...
    Feb 01 03:33:18 ruko wickedd[991]: ni_process_reap: process 1014 has not exited yet; now doing a blocking waitpid()
    Feb 01 03:33:21 ruko wickedd-dhcp4[959]: eth0: Request to acquire DHCPv4 lease with UUID 0e28725a-9004-0f00-df03-000005000000
    Feb 01 03:33:21 ruko wickedd[991]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/24 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 03:33:21 ruko wickedd[991]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 03:33:31 ruko wickedd-dhcp4[959]: unable to confirm lease
    Feb 01 03:33:36 ruko wickedd-dhcp4[959]: eth0: defer timeout 15 reached (state INIT)
    Feb 01 03:33:41 ruko wickedd-dhcp4[959]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 03:33:42 ruko wickedd[991]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 03:41:56 ruko wickedd-dhcp4[959]: eth0: Request to acquire DHCPv4 lease with UUID 0e28725a-9004-0f00-df03-000005000000
    Feb 01 03:42:02 ruko wickedd-dhcp4[959]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 03:42:02 ruko wickedd[991]: route ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease
    Feb 01 03:42:56 ruko wickedd-dhcp4[959]: eth0: Request to release DHCPv4 lease with UUID 0e28725a-9004-0f00-df03-000005000000: releasing...
    Feb 01 03:43:04 ruko wickedd-dhcp4[959]: eth0: Request to acquire DHCPv4 lease with UUID 0e28725a-9004-0f00-df03-00000c000000
    Feb 01 03:43:04 ruko wickedd[991]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/24 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 03:43:08 ruko wickedd-dhcp4[959]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 03:43:09 ruko wickedd[991]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 03:43:49 ruko wickedd-dhcp4[959]: eth0: Request to acquire DHCPv4 lease with UUID 0e28725a-9004-0f00-df03-00000c000000
    Feb 01 03:43:54 ruko wickedd-dhcp4[959]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 03:43:54 ruko wickedd[991]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 03:45:26 ruko wickedd-dhcp4[959]: eth0: Request to release DHCPv4 lease with UUID 0e28725a-9004-0f00-df03-00000c000000: releasing...
    Feb 01 03:45:34 ruko wickedd-dhcp4[959]: eth0: Request to acquire DHCPv4 lease with UUID 0e28725a-9004-0f00-df03-000013000000
    Feb 01 03:45:34 ruko wickedd[991]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 03:45:40 ruko wickedd-dhcp4[959]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 03:45:40 ruko wickedd[991]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 03:46:27 ruko wickedd-dhcp4[959]: eth0: Request to acquire DHCPv4 lease with UUID 0e28725a-9004-0f00-df03-000013000000
    Feb 01 03:46:31 ruko wickedd-dhcp4[959]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 03:46:31 ruko wickedd[991]: route ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease
    Feb 01 03:55:32 ruko wickedd-dhcp4[959]: eth0: Request to release DHCPv4 lease with UUID 0e28725a-9004-0f00-df03-000013000000: releasing...
    Feb 01 03:56:08 ruko wickedd-dhcp4[947]: eth0: Request to acquire DHCPv4 lease with UUID 662d725a-4b2c-0300-db03-000005000000
    Feb 01 03:56:08 ruko wickedd[987]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 03:56:13 ruko wickedd-dhcp4[947]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 03:56:14 ruko wickedd[987]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 04:00:58 ruko wickedd-dhcp4[947]: eth0: Request to release DHCPv4 lease with UUID 662d725a-4b2c-0300-db03-000005000000: releasing...
    Feb 01 04:01:39 ruko wickedd-dhcp4[915]: eth0: Request to acquire DHCPv4 lease with UUID b12e725a-b3dd-0500-bb03-000005000000
    Feb 01 04:01:39 ruko wickedd[955]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 04:01:44 ruko wickedd-dhcp4[915]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 04:01:45 ruko wickedd[955]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 05:31:45 ruko wickedd-dhcp4[915]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 05:31:45 ruko wickedd[955]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 07:01:45 ruko wickedd-dhcp4[915]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 07:01:45 ruko wickedd[955]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 07:41:01 ruko wickedd-dhcp4[915]: eth0: Request to release DHCPv4 lease with UUID b12e725a-b3dd-0500-bb03-000005000000: releasing...
    Feb 01 13:20:34 ruko wickedd-dhcp4[901]: eth0: Request to acquire DHCPv4 lease with UUID afb1725a-cc8a-0e00-8d03-000005000000
    Feb 01 13:20:34 ruko wickedd[909]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 13:20:38 ruko wickedd-dhcp4[901]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 13:20:39 ruko wickedd[909]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 13:44:59 ruko wickedd-dhcp4[901]: eth0: Request to acquire DHCPv4 lease with UUID afb1725a-cc8a-0e00-8d03-000005000000
    Feb 01 13:45:04 ruko wickedd-dhcp4[901]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 13:45:04 ruko wickedd[909]: route ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease
    Feb 01 15:15:04 ruko wickedd-dhcp4[901]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 15:15:04 ruko wickedd[909]: route ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease
    Feb 01 16:45:04 ruko wickedd-dhcp4[901]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 16:45:04 ruko wickedd[909]: route ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease
    Feb 01 18:02:33 ruko wickedd-dhcp4[901]: eth0: Request to release DHCPv4 lease with UUID afb1725a-cc8a-0e00-8d03-000005000000: releasing...
    Feb 01 20:16:19 ruko wickedd-dhcp4[968]: eth0: Request to acquire DHCPv4 lease with UUID 2213735a-cbdd-0200-e603-000005000000
    Feb 01 20:16:19 ruko wickedd[998]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 20:16:20 ruko wickedd-dhcp4[968]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 20:16:21 ruko wickedd[998]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 21:46:21 ruko wickedd-dhcp4[968]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 21:46:22 ruko wickedd[998]: route ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease
    Feb 01 21:50:38 ruko wickedd-dhcp4[968]: eth0: Request to release DHCPv4 lease with UUID 2213735a-cbdd-0200-e603-000005000000: releasing...
    Feb 01 21:51:18 ruko wickedd-dhcp4[945]: eth0: Request to acquire DHCPv4 lease with UUID 6529735a-ef17-0200-dc03-000005000000
    Feb 01 21:51:18 ruko wickedd[988]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 21:51:23 ruko wickedd-dhcp4[945]: eth0: Committed DHCPv4 lease with address 192.168.2.254 (lease time 10800 sec, renew in 5400 sec, rebind in 9450 sec)
    Feb 01 21:51:23 ruko wickedd[988]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 22:07:31 ruko wickedd-dhcp4[945]: eth0: Request to release DHCPv4 lease with UUID 6529735a-ef17-0200-dc03-000005000000: releasing...
    Feb 01 22:08:09 ruko wickedd-dhcp4[978]: eth0: Request to acquire DHCPv4 lease with UUID 572d735a-607c-0b00-dd03-000005000000
    Feb 01 22:08:09 ruko wickedd[989]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0 type unicast table main scope universe protocol boot): ni_nl_talk failed [Unspecific failure]
    Feb 01 22:08:15 ruko wickedd-dhcp4[978]: eth0: Committed DHCPv4 lease with address 192.168.2.20 (lease time 86400 sec, renew in 43200 sec, rebind in 75600 sec)
    Feb 01 22:08:15 ruko wickedd[989]: __ni_rtnl_send_newroute(ipv4 0.0.0.0/0 via 192.168.2.0 dev eth0 type unicast table main scope universe protocol dhcp): ni_nl_talk failed [Invalid input data or parameter]
    Feb 01 22:31:51 ruko wickedd-dhcp4[978]: eth0: Request to acquire DHCPv4 lease with UUID 572d735a-607c-0b00-dd03-000005000000
    Feb 01 22:31:51 ruko wickedd[989]: route ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease
    Feb 01 22:31:52 ruko wickedd-dhcp4[978]: eth0: Committed DHCPv4 lease with address 192.168.2.20 (lease time 86400 sec, renew in 43200 sec, rebind in 75600 sec)
    Feb 01 22:31:52 ruko wickedd[989]: route ipv4 0.0.0.0/0 via 192.168.2.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease
    Feb 01 22:33:04 ruko wickedd-dhcp4[978]: eth0: Request to release DHCPv4 lease with UUID 572d735a-607c-0b00-dd03-000005000000: releasing...
    i am using asus motherboard A58 ME
    i hope someone here can help me to resolve this problem, cause it costs me 1 new motherboard....

  3. #3

    Default Re: unable to add default route

    This, as well as your journalctl output, seems to indicate that the
    correct gateway IP is 192.168.2.1, and while that sounds fine, I also see
    attempts to add 192.168.1.0 as your gateway address, which is definitely
    wrong if you are using a /24 netmask as that is the network address.

    The question is, "Why is anything trying to use 192.168.2.0?" To me, the
    most-obvious answer is that your DHCP service is misconfigured and trying
    to send out that address, though that is really odd since most home setup
    (maybe this is not your home) have the router and DHCP service in one, and
    they know how to advertise their one internal IPv4 address as a gateway
    via DHCP, so unless you manually tweaked something, or you have a separate
    DHCP service that you setup, this should not be the case. Perhaps you can
    shed some light on that, though.

    Another way to verify this may be to use tcpdump to show what the DHCP
    service is offering:

    Code:
    sudo zypper in tcpdump
    sudo /usr/sbin/tcpdump -n -s 0 -i any -v port 67 or port 68
    Let it run for a bit as you restart Network Manager and hopefully we'll
    get some useful information. We are looking for a Reply, kind of like this:

    Code:
    06:21:44.842142 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
    (17), length 343)
    192.168.1.20.67 > 192.168.1.3.68: BOOTP/DHCP, Reply, length 315, xid
    0xe7d8c547, Flags [none]
    Client-IP 192.168.1.3
    Your-IP 192.168.1.3
    Client-Ethernet-Address 00:90:f5:d3:b1:43
    Vendor-rfc1048 Extensions
    Magic Cookie 0x63825363
    DHCP-Message Option 53, length 1: ACK
    Server-ID Option 54, length 4: 192.168.1.20
    Lease-Time Option 51, length 4: 600
    Subnet-Mask Option 1, length 4: 255.255.255.0
    Default-Gateway Option 3, length 4: 192.168.1.1
    Domain-Name Option 15, length 17: "my.domain.here"
    Domain-Name-Server Option 6, length 8: 192.168.1.20,192.168.1.1
    NTP Option 42, length 16:
    162.210.110.4,45.76.244.193,204.2.134.163,208.75.88.4
    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below.

    If you want to send me a private message, please let me know in the
    forum as I do not use the web interface often.

  4. #4
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,578

    Exclamation Re: unable to add default route

    Quote Originally Posted by momod View Post
    this is journalctl log
    From the systemd Journal, you have "Wicked" enabled -- which is IMHO a correct decision for the case of a Desktop and/or Server system.

    "Network Manager" on the other hand is, IMHO, the correct decision for Laptops and other mobile/portable machines.

    Be aware that, "Wicked" and "Network Manager" are mutually exclusive -- use one or the other but, not both . . .
    For example, on this Desktop machine:
    Code:
     > systemctl list-unit-files | grep -E 'Network|icked'
    dbus-org.opensuse.Network.AUTO4.service enabled
    dbus-org.opensuse.Network.DHCP4.service enabled
    dbus-org.opensuse.Network.DHCP6.service enabled
    dbus-org.opensuse.Network.Nanny.service enabled
    NetworkManager-dispatcher.service       masked
    NetworkManager-wait-online.service      masked
    NetworkManager.service                  masked
    wicked.service                          enabled
    wickedd-auto4.service                   enabled
    wickedd-dhcp4.service                   enabled
    wickedd-dhcp6.service                   enabled
    wickedd-nanny.service                   enabled
    wickedd-pppd@.service                   static
    wickedd.service                         indirect
     >
    For Laptops the systemd enabled/disabled is the other way around: "Network Manager" is enabled and "Wicked" is disabled.

  5. #5

    Default Re: unable to add default route [SOLVED]

    appreciate the reply ab
    it turns out, i put wrong gateway ip like you said "why is anything trying to use 192.168.2.0?"
    so i re-check closely on my router dhcp setup, i put 192.168.2.0 on gateway box, feel so stupid cause i have check this setup couples time, i did not see anything wrong with the setup.

    so now dhcp is working, i change from static ip to dhcp at my desktop pc.
    i am able to remote via ssh.

    thanks again ab
    Quote Originally Posted by ab View Post
    This, as well as your journalctl output, seems to indicate that the
    correct gateway IP is 192.168.2.1, and while that sounds fine, I also see
    attempts to add 192.168.1.0 as your gateway address, which is definitely
    wrong if you are using a /24 netmask as that is the network address.

    The question is, "Why is anything trying to use 192.168.2.0?" To me, the
    most-obvious answer is that your DHCP service is misconfigured and trying
    to send out that address, though that is really odd since most home setup
    (maybe this is not your home) have the router and DHCP service in one, and
    they know how to advertise their one internal IPv4 address as a gateway
    via DHCP, so unless you manually tweaked something, or you have a separate
    DHCP service that you setup, this should not be the case. Perhaps you can
    shed some light on that, though.

    Another way to verify this may be to use tcpdump to show what the DHCP
    service is offering:

    Code:
    sudo zypper in tcpdump
    sudo /usr/sbin/tcpdump -n -s 0 -i any -v port 67 or port 68
    Let it run for a bit as you restart Network Manager and hopefully we'll
    get some useful information. We are looking for a Reply, kind of like this:

    Code:
    06:21:44.842142 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
    (17), length 343)
    192.168.1.20.67 > 192.168.1.3.68: BOOTP/DHCP, Reply, length 315, xid
    0xe7d8c547, Flags [none]
    Client-IP 192.168.1.3
    Your-IP 192.168.1.3
    Client-Ethernet-Address 00:90:f5:d3:b1:43
    Vendor-rfc1048 Extensions
    Magic Cookie 0x63825363
    DHCP-Message Option 53, length 1: ACK
    Server-ID Option 54, length 4: 192.168.1.20
    Lease-Time Option 51, length 4: 600
    Subnet-Mask Option 1, length 4: 255.255.255.0
    Default-Gateway Option 3, length 4: 192.168.1.1
    Domain-Name Option 15, length 17: "my.domain.here"
    Domain-Name-Server Option 6, length 8: 192.168.1.20,192.168.1.1
    NTP Option 42, length 16:
    162.210.110.4,45.76.244.193,204.2.134.163,208.75.88.4
    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below.

    If you want to send me a private message, please let me know in the
    forum as I do not use the web interface often.
    i am aware with this condition, everyone suggest to use wickedd over NetworkManager...
    thanks anyway.
    Quote Originally Posted by dcurtisfra View Post
    From the systemd Journal, you have "Wicked" enabled -- which is IMHO a correct decision for the case of a Desktop and/or Server system.

    "Network Manager" on the other hand is, IMHO, the correct decision for Laptops and other mobile/portable machines.

    Be aware that, "Wicked" and "Network Manager" are mutually exclusive -- use one or the other but, not both . . .
    For example, on this Desktop machine:
    Code:
     > systemctl list-unit-files | grep -E 'Network|icked'
    dbus-org.opensuse.Network.AUTO4.service enabled
    dbus-org.opensuse.Network.DHCP4.service enabled
    dbus-org.opensuse.Network.DHCP6.service enabled
    dbus-org.opensuse.Network.Nanny.service enabled
    NetworkManager-dispatcher.service       masked
    NetworkManager-wait-online.service      masked
    NetworkManager.service                  masked
    wicked.service                          enabled
    wickedd-auto4.service                   enabled
    wickedd-dhcp4.service                   enabled
    wickedd-dhcp6.service                   enabled
    wickedd-nanny.service                   enabled
    wickedd-pppd@.service                   static
    wickedd.service                         indirect
     >
    For Laptops the systemd enabled/disabled is the other way around: "Network Manager" is enabled and "Wicked" is disabled.

  6. #6

    Default Re: unable to add default route

    Glad to hear it; thank-you for posting back confirmation.


    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below.

    If you want to send me a private message, please let me know in the
    forum as I do not use the web interface often.

Posting Permissions

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