Can't get RED interface up

pppoe
v7

(Matthieu Gaillet) #1

NethServer Version: 7.3

Hi,

Yesterday I fiddled with my network settings trying to create a pppoe red interface and it look like I managed to completely break my configuration.

I tried to restore my old configuration, a double-nat with the red interface getting an address from my ISP’s router.

Since then, the interface is getting an IP adress but don’t goes up anymore. Here are the logs after a reboot (filtered on enp3s6f0) :

Sep  7 10:21:56 serveur dhclient[24854]: DHCPDISCOVER on enp3s6f0 to 255.255.255.255 port 67 interval 5 (xid=0x15013b9c)
Sep  7 10:21:56 serveur dhclient[24854]: DHCPREQUEST on enp3s6f0 to 255.255.255.255 port 67 (xid=0x15013b9c)
Sep  7 10:21:58 serveur avahi-daemon[2835]: Joining mDNS multicast group on interface enp3s6f0.IPv4 with address 192.168.178.23.
Sep  7 10:21:58 serveur avahi-daemon[2835]: New relevant interface enp3s6f0.IPv4 for mDNS.
Sep  7 10:21:58 serveur avahi-daemon[2835]: Registering new address record for 192.168.178.23 on enp3s6f0.IPv4.
Sep  7 10:24:42 serveur network: Bringing up interface enp3s6f0:
Sep  7 10:24:43 serveur kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s6f0: link is not ready
Sep  7 10:24:43 serveur kernel: e1000: enp3s6f0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
Sep  7 10:24:43 serveur kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s6f0: link becomes ready
Sep  7 10:24:43 serveur dhclient[1122]: DHCPREQUEST on enp3s6f0 to 255.255.255.255 port 67 (xid=0x1497f630)
Sep  7 10:24:44 serveur avahi-daemon[796]: Registering new address record for fe80::21b:21ff:feae:4232 on enp3s6f0.*.
Sep  7 10:24:45 serveur avahi-daemon[796]: Joining mDNS multicast group on interface enp3s6f0.IPv4 with address 192.168.178.23.
Sep  7 10:24:45 serveur avahi-daemon[796]: New relevant interface enp3s6f0.IPv4 for mDNS.
Sep  7 10:24:45 serveur avahi-daemon[796]: Registering new address record for 192.168.178.23 on enp3s6f0.IPv4.
Sep  7 10:24:45 serveur network: Determining IP information for enp3s6f0... done.
Sep  7 10:25:05 serveur shorewall: WARNING: Interface enp3s6f0 is not usable -- Provider EDPNT (1) not Started
Sep  7 10:25:58 serveur Shorewall[3896]: Disabling device enp3s6f0

Here is the output of fconfig -a

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.10.1.1  netmask 255.255.0.0  broadcast 10.10.255.255
        inet6 fe80::21b:21ff:feae:4230  prefixlen 64  scopeid 0x20<link>
        ether 00:1b:21:ae:42:30  txqueuelen 1000  (Ethernet)
        RX packets 64741  bytes 14773903 (14.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 59684  bytes 66471444 (63.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp3s4f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::21b:21ff:feae:4230  prefixlen 64  scopeid 0x20<link>
        ether 00:1b:21:ae:42:30  txqueuelen 1000  (Ethernet)
        RX packets 65604  bytes 15761917 (15.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 67429  bytes 70963585 (67.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp3s4f1: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 00:1b:21:ae:42:31  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp3s6f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.178.23  netmask 255.255.255.0  broadcast 192.168.178.255
        inet6 fe80::21b:21ff:feae:4232  prefixlen 64  scopeid 0x20<link>
        ether 00:1b:21:ae:42:32  txqueuelen 1000  (Ethernet)
        RX packets 472  bytes 39689 (38.7 KiB)
        RX errors 0  dropped 130  overruns 0  frame 0
        TX packets 536  bytes 41150 (40.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp3s6f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.3.210  netmask 255.255.255.0  broadcast 192.168.3.255
        inet6 fe80::21b:21ff:feae:4233  prefixlen 64  scopeid 0x20<link>
        ether 00:1b:21:ae:42:33  txqueuelen 1000  (Ethernet)
        RX packets 66171  bytes 61351800 (58.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 53298  bytes 13751258 (13.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 3537  bytes 295791 (288.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3537  bytes 295791 (288.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tap0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::18c6:bbff:fe0d:503c  prefixlen 64  scopeid 0x20<link>
        ether 1a:c6:bb:0d:50:3c  txqueuelen 100  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1499  bytes 334426 (326.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vb-nsdc: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::d06f:aff:fea5:6902  prefixlen 64  scopeid 0x20<link>
        ether d2:6f:0a:a5:69:02  txqueuelen 1000  (Ethernet)
        RX packets 1444  bytes 448986 (438.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3103  bytes 629589 (614.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

And here is the output of shorewall restart -T

Compiling using Shorewall 5.0.14.1...
Processing /etc/shorewall/params ...
Processing /etc/shorewall/shorewall.conf...
Loading Modules...
Compiling /etc/shorewall/zones...
Compiling /etc/shorewall/interfaces...
Determining Hosts in Zones...
Locating Action Files...
Compiling /etc/shorewall/policy...
Running /etc/shorewall/initdone...
Adding Anti-smurf Rules
Adding rules for DHCP
Compiling TCP Flags filtering...
Compiling Kernel Route Filtering...
Compiling Martian Logging...
Compiling /etc/shorewall/tcinterfaces...
Compiling /etc/shorewall/providers...
Compiling /etc/shorewall/rtrules...
Compiling /etc/shorewall/masq...
Compiling MAC Filtration -- Phase 1...
Compiling /etc/shorewall/rules...
Compiling /etc/shorewall/conntrack...
Compiling MAC Filtration -- Phase 2...
Applying Policies...
Compiling /usr/share/shorewall/action.Reject for chain Reject...
Compiling /usr/share/shorewall/action.Broadcast for chain Broadcast...
Compiling /usr/share/shorewall/action.Drop for chain Drop...
Compiling /etc/shorewall/tcpri...
Generating Rule Matrix...
Creating iptables-restore input...
Compiling /etc/shorewall/stoppedrules...
Shorewall configuration compiled to /var/lib/shorewall/.restart
Reloading Shorewall....
Initializing...
Processing /etc/shorewall/init ...
Processing /etc/shorewall/tcclear ...
Setting up Route Filtering...
Setting up Martian Logging...
Setting up Proxy ARP...
Adding Providers...
   WARNING: Interface enp3s6f0 is not usable -- Provider EDPNT (1) not Started
Setting up Traffic Control...
Preparing iptables-restore input...
Running /sbin/iptables-restore ...
IPv4 Forwarding Enabled
Processing /etc/shorewall/start ...
Processing /etc/shorewall/started ...
done.

Since this configuration worked perfectly for months before I suspect something went wrong when I tried to add the pppoe interface. I restored a configuration backup without result.

Thanks for helping :grimacing:


(Matthieu Gaillet) #2

UPDATE - SOLVED

I completely deleted the red interfaces and recreated them (exchanging ports to be sure). Everything is UP again.

I guess there is something wrong with the PPPoE module which seems to break things.

Txs