HELP!
I have a system in the cloud that was running Ubuntu 16.04 and ifupdown.
One interface eth0 with two addresses, 0.38.15.82 and 0.38.15.83/29.

After the reboot shorewall will not start:
Adding Providers...
   ERROR: Interface eth0 is not usable -- Provider internet (1) Cannot be
Started

However:
# ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 0.38.15.82  netmask 255.255.255.248  broadcast 0.38.15.87
        inet6 fe80::a00:27ff:fee8:8e43  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:e8:8e:43  txqueuelen 1000  (Ethernet)
        RX packets 7003  bytes 724233 (724.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4856  bytes 774651 (774.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
# ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
group default qlen 1000
    link/ether 08:00:27:e8:8e:43 brd ff:ff:ff:ff:ff:ff
    inet 0.38.15.82/29 brd 0.38.15.87 scope global eth0
       valid_lft forever preferred_lft forever
    inet 0.38.15.83/29 brd 0.38.15.87 scope global secondary eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fee8:8e43/64 scope link
       valid_lft forever preferred_lft forever
# ip link show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
mode DEFAULT group default qlen 1000
    link/ether 08:00:27:e8:8e:43 brd ff:ff:ff:ff:ff:ff
# systemctl status systemd-networkd
● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service;
enabled-runtime; vendor preset: enabled)
   Active: active (running) since Fri 2021-07-09 09:28:34 UTC; 3s ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 6268 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 1108)
   CGroup: /system.slice/systemd-networkd.service
           └─6268 /lib/systemd/systemd-networkd

Jul 09 09:28:34 VM-CEML systemd-networkd[6268]: eth0: Gained IPv6LL
Jul 09 09:28:34 VM-CEML systemd-networkd[6268]: Enumeration completed
Jul 09 09:28:34 VM-CEML systemd[1]: Started Network Service.
Jul 09 09:28:34 VM-CEML systemd-networkd[6268]: eth0: IPv6 successfully
enabled
Jul 09 09:28:34 VM-CEML systemd-networkd[6268]: tun9: Link is not managed
by us
Jul 09 09:28:34 VM-CEML systemd-networkd[6268]: tun0: Link is not managed
by us
Jul 09 09:28:34 VM-CEML systemd-networkd[6268]: tun4: Link is not managed
by us
Jul 09 09:28:34 VM-CEML systemd-networkd[6268]: lo: Link is not managed by
us
Jul 09 09:28:34 VM-CEML systemd-networkd[6268]: tun6: Link is not managed
by us
Jul 09 09:28:34 VM-CEML systemd-networkd[6268]: eth0: Configured

# ip route
default via 0.38.15.81 dev eth0 proto static

Due to stoppedrules, I can ssh to the system and even some of the openvpn
tunnels are up. Why does shorewall think that eth0 is not usable and how to
fix?

# cat interfaces
?FORMAT 2
#ZONE INTERFACE [BROADCAST] OPTIONS
Dirty   eth0    routeback #,routefilter=1

Not sure what other config is relevant but let me know... And this when I
am supposed to be on holiday... ;}

Thanks, Norm Henderson
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to