Open Chadster766 opened 4 years ago
Take a look for the errors .. journalctl.txt
Before i make a clean install i suggest to find this strange bug..but it is all ready fresh ....
If you have a spare USB Key you could test with that instead of changing your SSD rootfs. Just swap it with the USB key for testing.
Take a look for the errors .. journalctl.txt
There are a lot of differences between yours and mine. The first thing that jumps out is:
Yours:
Jun 10 11:35:52 MCDEBIAN pppd[843]: pppd 2.4.7 started by root, uid 0
Jun 10 11:35:52 MCDEBIAN kernel: NET: Registered protocol family 24
Jun 10 11:35:52 MCDEBIAN ifup[846]: /etc/nftables.conf:2:1-77: Error: Could not process rule: No such file or directory
Jun 10 11:35:52 MCDEBIAN ifup[846]: add flowtable inet x f { hook ingress priority 0; devices = { ppp0, br0 }; }
Jun 10 11:35:52 MCDEBIAN ifup[846]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jun 10 11:35:52 MCDEBIAN ifup[846]: /etc/nftables.conf:4:1-59: Error: Could not process rule: No such file or directory
Jun 10 11:35:52 MCDEBIAN ifup[846]: add rule inet x y ip protocol { udp, tcp } flow offload @f
Jun 10 11:35:52 MCDEBIAN ifup[846]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jun 10 11:35:52 MCDEBIAN ifup[277]: ifup: failed to bring up dsl-provider
Jun 10 11:35:52 MCDEBIAN systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Jun 10 11:35:52 MCDEBIAN pppd[843]: PPP session is 58939
Jun 10 11:35:52 MCDEBIAN pppd[843]: Connected to 00:c1:64:54:dd:a2 via interface wan
Jun 10 11:35:52 MCDEBIAN pppd[843]: Using interface ppp0
Jun 10 11:35:52 MCDEBIAN pppd[843]: Connect: ppp0 <--> wan
Jun 10 11:35:52 MCDEBIAN pppd[843]: Terminating on signal 15
Mine:
Feb 14 10:13:34 MCDEBIAN pppd[860]: pppd 2.4.7 started by root, uid 0
Feb 14 10:13:34 MCDEBIAN kernel: NET: Registered protocol family 24
Feb 14 10:13:34 MCDEBIAN pppd[860]: PPP session is 1
Feb 14 10:13:34 MCDEBIAN pppd[860]: Connected to 00:23:04:31:c6:76 via interface wan
Feb 14 10:13:34 MCDEBIAN pppd[860]: Using interface ppp0
Feb 14 10:13:34 MCDEBIAN pppd[860]: Connect: ppp0 <--> wan
Something is triggering the nft load of config file /etc/nftables.conf in the pre-up stage of the pppoe interface coming up instead of the post-up phase.
Well , i will try a clean installation on usb
Well ,with alot of care ,and your advices,and of course with your own /etc/network/interfaces
The results are the same as e-sata. One more question ,you working virtual machine or live hardware?
root@MCDEBIAN:~# lsusb Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 13fe:1d00 Kingston Technology Company Inc. DataTraveler 2.0 1GB/4GB Flash Drive / Patriot Xporter 4GB Flash Drive Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@MCDEBIAN:~# ping 8.8.8.8 connect: Network is unreachable
root@MCDEBIAN:~# lsmod Module Size Used by nft_flow_offload 16384 0 nf_tables_set 40960 0 nf_flow_table_inet 16384 0 nf_flow_table 32768 2 nft_flow_offload,nf_flow_table_inet pppoe 20480 0 pppox 16384 1 pppoe ppp_generic 32768 2 pppox,pppoe slhc 16384 1 ppp_generic nft_chain_nat 16384 8 xt_MASQUERADE 16384 2 nf_nat 32768 2 xt_MASQUERADE,nft_chain_nat nft_counter 16384 15 xt_state 16384 0 xt_conntrack 16384 3 nf_conntrack 102400 6 xt_state,nf_flow_table,nft_flow_offload,xt_MASQUERADE,xt_conntrack,nf_nat nf_defrag_ipv4 16384 1 nf_conntrack libcrc32c 16384 2 nf_conntrack,nf_nat nft_compat 20480 6 nf_tables 126976 55 nft_compat,nf_tables_set,nft_flow_offload,nf_flow_table_inet,nft_chain_nat,nft_counter nfnetlink 16384 2 nft_compat,nf_tables tag_edsa 16384 1 mv88e6xxx 102400 0 mwifiex_sdio 32768 0 mwifiex 249856 1 mwifiex_sdio mwlwifi 159744 0 dsa_core 45056 2 tag_edsa,mv88e6xxx bridge 159744 1 dsa_core marvell_cesa 36864 0 stp 16384 1 bridge llc 16384 2 bridge,stp libdes 28672 1 marvell_cesa ip_tables 24576 0 ipv6 417792 39 bridge nf_defrag_ipv6 16384 2 nf_conntrack,ipv6
systemctl status networking ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 10:13:32 UTC; 6min ago Docs: man:interfaces(5) Process: 270 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Main PID: 270 (code=exited, status=1/FAILURE)
Feb 14 10:13:32 MCDEBIAN pppd[845]: Connected to 00:c1:64:54:dd:a2 via interface wan Feb 14 10:13:32 MCDEBIAN pppd[845]: Using interface ppp0 Feb 14 10:13:32 MCDEBIAN pppd[845]: Connect: ppp0 <--> wan Feb 14 10:13:32 MCDEBIAN systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE Feb 14 10:13:32 MCDEBIAN pppd[845]: Terminating on signal 15 Feb 14 10:13:32 MCDEBIAN pppd[845]: Connection terminated. Feb 14 10:13:32 MCDEBIAN pppd[845]: Sent PADT Feb 14 10:13:32 MCDEBIAN pppd[845]: Exit. Feb 14 10:13:32 MCDEBIAN systemd[1]: networking.service: Failed with result 'exit-code'. Feb 14 10:13:32 MCDEBIAN systemd[1]: Failed to start Raise network interfaces.
root@MCDEBIAN:~# nft -i nft> -i Error: syntax error, unexpected - -i ^ nft> info Error: syntax error, unexpected newline, expecting string info ^ nft> ^C root@MCDEBIAN:~# nft -info internal:0:0-0: Error: Could not open file "o": No such file or directory
The problem i think is when nftables loading ... Take care that if i remove the line from /etc/network/interfaces
auto dsl-provider iface dsl-provider inet ppp pre-up /bin/ip link set wan up # line maintained by pppoeconf pre-up iptables-restore < /etc/iptables.up.rules pre-up ip6tables-restore < /etc/ip6tables.up.rules (# post-up nft -f /etc/nftables.conf provider dsl-provider
Then Wan is working
ping 8.8.8.8 -c 5 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=53.4 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=53.1 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=53.3 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=53.6 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=119 time=53.3 ms
Any idea? Would you like to send you something else?
One more question ,you working virtual machine or live hardware?
Live hardware
@Mark-GR73 try manually loading the flowtable after a successful ping test.
nft -f /etc/nftables.conf
With this config
auto dsl-provider iface dsl-provider inet ppp pre-up /bin/ip link set wan up # line maintained by pppoeconf pre-up iptables-restore < /etc/iptables.up.rules pre-up ip6tables-restore < /etc/ip6tables.up.rules if-up nft -f /etc/nftables.conf # That is changed NOW<------------ provider dsl-provider
root@MCDEBIAN:~# ping -c 5 8.8.4.4 PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data. 64 bytes from 8.8.4.4: icmp_seq=1 ttl=118 time=53.9 ms 64 bytes from 8.8.4.4: icmp_seq=2 ttl=118 time=53.3 ms 64 bytes from 8.8.4.4: icmp_seq=3 ttl=118 time=53.1 ms 64 bytes from 8.8.4.4: icmp_seq=4 ttl=118 time=53.1 ms 64 bytes from 8.8.4.4: icmp_seq=5 ttl=118 time=53.3 ms
root@MCDEBIAN:~# nft -i nft> nft> ^C root@MCDEBIAN:~# nft -info internal:0:0-0: Error: Could not open file "o": No such file or directory
and with the same config as you advise me
root@MCDEBIAN:~# nft -f /etc/nftables.conf
root@MCDEBIAN:~# ping -c 5 8.8.4.4 PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data. 64 bytes from 8.8.4.4: icmp_seq=1 ttl=118 time=53.4 ms 64 bytes from 8.8.4.4: icmp_seq=2 ttl=118 time=53.1 ms 64 bytes from 8.8.4.4: icmp_seq=3 ttl=118 time=53.2 ms 64 bytes from 8.8.4.4: icmp_seq=4 ttl=118 time=53.5 ms 64 bytes from 8.8.4.4: icmp_seq=5 ttl=118 time=53.6 ms
--- 8.8.4.4 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 10ms rtt min/avg/max/mdev = 53.147/53.370/53.576/0.266 ms
root@MCDEBIAN:~# nft -i nft> nft> ^C
I think this is correct ,just take a look....
and of course it is only nftables.conf The .txt is just for pasting reasons...
The nftables.conf looks good.
When I had you run "nft -i" (nft interactive mode) it was just to see if nftables was installed. The command "nft list table inet x" will show the active flowtable and its updated count.
What is command "nft -info" you keep runnin for?
Ignore it .
@Mark-GR73 please post your whole interfaces file.
/etc/network/interface
auto dsl-provider iface dsl-provider inet ppp pre-up /bin/ip link set wan up # line maintained by pppoeconf pre-up iptables-restore < /etc/iptables.up.rules pre-up ip6tables-restore < /etc/ip6tables.up.rules provider dsl-provider
root@MCDEBIAN:~# ping -c 5 8.8.4.4 PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data. 64 bytes from 8.8.4.4: icmp_seq=1 ttl=119 time=51.3 ms 64 bytes from 8.8.4.4: icmp_seq=2 ttl=119 time=50.10 ms 64 bytes from 8.8.4.4: icmp_seq=3 ttl=119 time=51.3 ms 64 bytes from 8.8.4.4: icmp_seq=4 ttl=119 time=51.0 ms 64 bytes from 8.8.4.4: icmp_seq=5 ttl=119 time=51.6 ms
root@MCDEBIAN:~# nft list table inet x Error: Could not process rule: No such file or directory list table inet x ^
root@MCDEBIAN:~# systemctl status nftables ● nftables.service - nftables Loaded: loaded (/lib/systemd/system/nftables.service; disabled; vendor preset Active: inactive (dead) Docs: man:nft(8)
nft -i
-Inside nft enviroment
with up and down narrows ,gives alot of info..
root@MCDEBIAN:~# nft -i
nft> list table x
Error: Could not process rule: No such file or directory
list table x
^
nft> list table filter table ip filter { chain INPUT { type filter hook input priority 0; policy drop; iifname "lo" counter packets 1 bytes 76 accept iifname "br0" counter packets 695 bytes 52959 accept iifname "ppp0" ct state related,established counter packets 226 bytes 17969 accept iifname "ppp0" meta l4proto icmp counter packets 1 bytes 44 accept }
chain FORWARD {
type filter hook forward priority 0; policy drop;
iifname "br0" counter packets 843 bytes 114256 accept
iifname "ppp0" counter packets 767 bytes 240657 accept
}
chain OUTPUT {
type filter hook output priority 0; policy accept;
}
} nft> nft> ^C
Now with ....
root@MCDEBIAN:~# nft -f /etc/nftables.conf
root@MCDEBIAN:~# ping -c 5 8.8.4.4 PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data. 64 bytes from 8.8.4.4: icmp_seq=1 ttl=119 time=51.4 ms 64 bytes from 8.8.4.4: icmp_seq=2 ttl=119 time=51.0 ms 64 bytes from 8.8.4.4: icmp_seq=3 ttl=119 time=50.9 ms 64 bytes from 8.8.4.4: icmp_seq=4 ttl=119 time=51.4 ms 64 bytes from 8.8.4.4: icmp_seq=5 ttl=119 time=51.4 ms
┌─[✗]─[ote@parrot]─[/] └──╼ $ping google.com PING google.com (172.217.21.206) 56(84) bytes of data. 64 bytes from fra16s12-in-f14.1e100.net (172.217.21.206): icmp_seq=1 ttl=117 time=228 ms 64 bytes from fra16s12-in-f14.1e100.net (172.217.21.206): icmp_seq=2 ttl=117 time=416 ms
oot@MCDEBIAN:~# nft list table inet x table inet x { flowtable f { hook ingress priority 0 devices = { ppp0, br0 } }
chain y {
type filter hook forward priority 0; policy accept;
ip protocol { tcp, udp } flow offload @f
counter packets 1 bytes 76
}
}
root@MCDEBIAN:~# systemctl status nftables ● nftables.service - nftables Loaded: loaded (/lib/systemd/system/nftables.service; disabled; vendor preset Active: inactive (dead) Docs: man:nft(8)
-Is there some reason to be the service disabled ?
This is the whole file from the previous post above
root@MCDEBIAN:~# cat /etc/network/interfaces
source-directory /etc/network/interfaces.d
auto lo iface lo inet loopback
auto eth0 iface eth0 inet manual
auto eth1 iface eth1 inet manual
auto lan1 iface lan1 inet manual
auto lan2 iface lan2 inet manual
auto lan3 iface lan3 inet manual
auto lan4 iface lan4 inet manual
iface wlp1s0 inet manual
iface wlp2s0 inet manual
auto wan iface wan inet dhcp hwaddress ether 02:e0:96:70:5f:c3
iface wan inet6 auto
auto br0 iface br0 inet static bridge_hw 02:2d:50:bd:ca:13 bridge_ports lan1 lan2 lan3 lan4 address 192.168.1.1 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 pre-up /etc/network/mcdebian-model-check
iface br0 inet6 static address fc00::1 netmask 64
auto dsl-provider iface dsl-provider inet ppp pre-up /bin/ip link set wan up # line maintained by pppoeconf pre-up iptables-restore < /etc/iptables.up.rules pre-up ip6tables-restore < /etc/ip6tables.up.rules provider dsl-provider root@MCDEBIAN:~#
And We are in clean install to usb..
Don't enable nftables service since we start it when we load the flowtable config in interfaces
The counter is going up in the flowtable so its working
root@MCDEBIAN:~# nft list table inet x table inet x { flowtable f { hook ingress priority 0 devices = { ppp0, br0 } }
chain y {
type filter hook forward priority 0; policy accept;
ip protocol { tcp, udp } flow offload @f
counter packets 120 bytes 8239
}
}
After while....
root@MCDEBIAN:~# nft list table inet x table inet x { flowtable f { hook ingress priority 0 devices = { ppp0, br0 } }
chain y {
type filter hook forward priority 0; policy accept;
ip protocol { tcp, udp } flow offload @f
counter packets 226 bytes 15892
}
} root@MCDEBIAN:~#
Now it's yours....
Flowtable is working
Remain to start it up on interface as you very well explained before..
@Mark-GR73 thank you very much for help on this pppoe issue. Please continue to work on this because I don't have a similar ISP or test lab capable of simulating this issue.
Thank you too.. Any suggestions how to startup the nftables when interface is up? I will give a try on it.
Would you prefer a classic script? Give me something to go this way..i must how about you want for this solution..
You must know ,Iam from Greece ,my English language is not perfect ,the difficulty is that i think oppossite the words than english ,and if i make some mistake ,forgive or correct me.
Καλημερα Good morning..
Well take a look ,i believe is the simplest way
auto dsl-provider iface dsl-provider inet ppp pre-up /bin/ip link set wan up # line maintained by pppoeconf pre-up iptables-restore < /etc/iptables.up.rules pre-up ip6tables-restore < /etc/ip6tables.up.rules post-up sleep 3 ; nft -f /etc/nftables.conf (# post-up /bin/sh /etc/network/if-up.d/nftables.sh (# post-up nft -f /etc/nftables.conf provider dsl-provider
oot@MCDEBIAN:~# nft list table inet x table inet x { flowtable f { hook ingress priority 0 devices = { ppp0, br0 } }
chain y {
type filter hook forward priority 0; policy accept;
ip protocol { tcp, udp } flow offload @f
counter packets 189 bytes 14402
}
}
root@MCDEBIAN:~# nft list table inet x table inet x { flowtable f { hook ingress priority 0 devices = { ppp0, br0 } }
chain y {
type filter hook forward priority 0; policy accept;
ip protocol { tcp, udp } flow offload @f
counter packets 327 bytes 22867
}
root@MCDEBIAN:~# ping -c2 github.com PING github.com (140.82.118.3) 56(84) bytes of data. 64 bytes from lb-140-82-118-3-ams.github.com (140.82.118.3): icmp_seq=1 ttl=56 time=62.2 ms 64 bytes from lb-140-82-118-3-ams.github.com (140.82.118.3): icmp_seq=2 ttl=56 time=62.8 ms
┌─[ote@parrot]─[~] └──╼ $ping github.com -c2 PING github.com (140.82.118.3) 56(84) bytes of data. 64 bytes from lb-140-82-118-3-ams.github.com (140.82.118.3): icmp_seq=1 ttl=55 time=64.5 ms 64 bytes from lb-140-82-118-3-ams.github.com (140.82.118.3): icmp_seq=2 ttl=55 time=64.4 ms
With the delay seems to be Fine. Any suggestion?
And for the proccesses to be correct without delay
auto dsl-provider iface dsl-provider inet ppp pre-up /bin/ip link set wan up # line maintained by pppoeconf pre-up iptables-restore < /etc/iptables.up.rules pre-up ip6tables-restore < /etc/ip6tables.up.rules provider dsl-provider post-up sleep 3 ; nft -f /etc/nftables.conf
Good idea using a 3 second delay.
Please check that the 3s delay doesn't cause the network service to fail on boot.
systemctl status networking
and even 1 s ....
post-up sleep 1 ; nft -f /etc/nftables.conf
root@MCDEBIAN:~# nft list table inet x table inet x { flowtable f { hook ingress priority 0 devices = { ppp0, br0 } }
chain y {
type filter hook forward priority 0; policy accept;
ip protocol { tcp, udp } flow offload @f
counter packets 375 bytes 25690
}
}
with 1 sec....
● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: active (exited) since Thu 2019-02-14 10:13:33 UTC; 1 years 4 months ago Docs: man:interfaces(5) Process: 270 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS) Main PID: 270 (code=exited, status=0/SUCCESS) Memory: 8.5M CGroup: /system.slice/networking.service ├─527 /sbin/dhclient -4 -v -i -pf /run/dhclient.wan.pid -lf /var/lib/dhcp/dhclient.wan.leases -I -df /var/lib/dhcp/dhclient └─864 /usr/sbin/pppd call dsl-provider
Feb 14 10:13:33 MCDEBIAN systemd[1]: Started Raise network interfaces. Jun 19 13:18:49 MCDEBIAN dhclient[527]: DHCPDISCOVER on wan to 255.255.255.255 port 67 interval 4 Jun 19 13:18:53 MCDEBIAN dhclient[527]: DHCPDISCOVER on wan to 255.255.255.255 port 67 interval 5 Jun 19 13:18:58 MCDEBIAN dhclient[527]: DHCPDISCOVER on wan to 255.255.255.255 port 67 interval 8 Jun 19 13:19:06 MCDEBIAN dhclient[527]: DHCPDISCOVER on wan to 255.255.255.255 port 67 interval 9 Jun 19 13:19:15 MCDEBIAN dhclient[527]: DHCPDISCOVER on wan to 255.255.255.255 port 67 interval 15 Jun 19 13:19:30 MCDEBIAN dhclient[527]: DHCPDISCOVER on wan to 255.255.255.255 port 67 interval 10 Jun 19 13:19:40 MCDEBIAN dhclient[527]: DHCPDISCOVER on wan to 255.255.255.255 port 67 interval 10 Jun 19 13:19:50 MCDEBIAN dhclient[527]: No DHCPOFFERS received. Jun 19 13:19:50 MCDEBIAN dhclient[527]: No working leases in persistent database - sleeping. ~
Great solution I will add this new information to the wiki networking page.
It would be great if we had a script to enable pppoe and make the interfaces file changes for users easier.
It would be great if we had a script to enable pppoe -Thats easy...!
but and make the interfaces file changes for users easier.
What do you mean ,,what are you thinking abbout?
If i understood well, you want a start-up or init.d script to activate the pppoe and the nftables
I would prefer the classic way for many reasons. Somebody needs only as Access point ,or may be as switch ,or many things without routing. There is no reason to run these proccesses. From other hand is more familiar to have all the network config in a file. And of course do not go far away from debian classic way...
I was thinking of having a script that the user could run not a script for init.d. It would only be used for initial setup of pppoe and the interfaces file. Then the user can customize from a know good interfaces file.
Give me a little time, you prefer to be something simple and to run only once with pppoe conf ? Or maybe content and your sed three lines?
Take a look something very simple as first idea
-Please make a test
mkdir /etc/test cp -rf /etc/network/interfaces /etc/test/
cd /etc/test wget --no-check-certificate https://github.com/Chadster766/McDebian/files/4807983/McDebian_pppoe_setup.sh.txt
mv /etc/test/McDebian_pppoe_setup.sh.txt /etc/test/McDebian_pppoe_setup.sh
cd /etc/test cat ./interfaces
chmod +x /etc/test/McDebian_pppoe_setup.sh sh /etc/test/McDebian_pppoe_setup.sh
cat ./interfaces
Any good opinion is welcome. May be this file converted to automate the whole system to McDebians needs...
Something like that ?
mkdir /etc/McDebian cd /etc/McDebian cp -rf /etc/network/interfaces /etc/McDebian/ cp -rf /etc/dhcp/dhclient.conf /etc/McDebian/ cp -rf /etc/default/isc-dhcp-server //etc/McDebian/
cd /etc/McDebian wget --no-check-certificate https://github.com/Chadster766/McDebian/files/4808100/McDebian_pppoe_setup.sh.txt mv /etc/McDebian/McDebian_pppoe_setup.sh.txt /etc/McDebian/McDebian_pppoe_setup.sh
chmod +x /etc/McDebian/McDebian_pppoe_setup.sh
cat ./interfaces cat ./dhclient.conf cat ./isc-dhcp-server
sh /etc/McDebian/McDebian_pppoe_setup.sh
cat ./interfaces cat ./dhclient.conf cat ./isc-dhcp-server
Great, I will test this out shortly.
-Wrong line
cp -rf /etc/default/isc-dhcp-server //etc/McDebian/
Must be
cp -rf /etc/default/isc-dhcp-server /etc/McDebian/
The pppoe setup script shouldn't enable radvd since that specific to a IPv6 setup. We could make a IPv6 setup script separately.
I think the script should use sed to modify the contents of the interfaces file directly with required changes. This could be done since we know what needs to moved where and after pppoeconf there is standard static text we could use a marker for sed text insertion\replacement.
-Wrong line
cp -rf /etc/default/isc-dhcp-server //etc/McDebian/
Must be
cp -rf /etc/default/isc-dhcp-server /etc/McDebian/
Why do you want to move files to a /etc/McDebian folder? Any McDebian scripts regarding networking I keep in the /etc/network folder of which there is only one at this point. Example: /etc/network/mcdebian-model-check
Let your mind to fly .. I agree with you in your notice The simpler and safest way as must..
Just for a safe test.. No other reason..
Just for a safe test.. No other reason..
I see you are making backups for yourself just in case. Makes sense but you don't need to worry about me I have a test usb key.
I like that idea. Maybe the first thing the script does is make a backup copy of the interfaces file (interfaces.bak) in /etc/network. Then if any script validations error it can copy it back to revert any changes.
That's Mcdebian..
Finally,
nftables working. It is time now to work again with e-sata, and of course i have alot of work to build whole the router.
Would you like something more from me?
This version of mcdebian finally is ready?
If you would like a have some general suggestions.
McDebian 5.6.14 Beta
Updates:
Notes:
I recommend that only users that have TTL access to their WRT routers do McDebian beta testing.
In the WRT1900AC V1 make sure you have the below u-boot envars set to to accommodate the increased kernel size.
Firmware:
Root File System Update:
IPv6
To enable IPv6 in this beta release you need to enable radvd:
Then uncomment the IPv6 config lines in:
After that reboot the router.