Hi, I'm respinning openwrt 19.07 from source (problems with nftables, that I need to get to the bottom of, and problem seems ion source).
Anyway respan a 19.07 upgrade, with much additional enabled in the kernel, and firewall disabled in the main menuconfig. Flashed the new openwrt.
It brings up the LAN fine, but its failing to bring up the ADSL wan, it gives the error:
Fri Jan 24 12:48:59 2020 daemon.err insmod: module is already loaded - slhc
Fri Jan 24 12:48:59 2020 daemon.err insmod: module is already loaded - ppp_generic
Fri Jan 24 12:48:59 2020 daemon.err insmod: module is already loaded - pppox
Fri Jan 24 12:48:59 2020 daemon.err insmod: module is already loaded - pppoatm
Fri Jan 24 12:49:00 2020 daemon.info pppd: Plugin pppoatm.so loaded.
Fri Jan 24 12:49:00 2020 daemon.info pppd: PPPoATM plugin_init
Fri Jan 24 12:49:00 2020 daemon.info pppd: PPPoATM setdevname_pppoatm - SUCCESS:0.38
Fri Jan 24 12:49:00 2020 daemon.notice pppd: pppd 2.4.7 started by root, uid 0
Fri Jan 24 12:49:00 2020 daemon.err pppd: connect(0.38): No such device
Fri Jan 24 12:49:00 2020 daemon.info pppd: Exit.
Fri Jan 24 12:49:00 2020 daemon.notice netifd: Interface 'wan' is now down
Now guess I've made a simple mistake, but will probably take some time for me to dig into it. SO to speed up the process, does anyone know what I did wrong?
Seems that there is no interface (WAN) through which PPP should establish the connection.
Yes I was leaning between that, and it not being able to load the than lantiq firmware.
Just going through another recompile, based on the kernel config in the release 19.07; where only changes have been switching on all nf tables and netfilter options, and enabling usbnet and cdc_ether.
So hopefully I shouldn't touch anything that creates devices. Is it easy to find which device pppd is trying to connect to?
That would the device specified in the network config - whatever the upstream connectivity port is for your device, e.g. eth0 or eth1 or eth2...
Did you try some VLAN ID tag on the interface, just asking because of
0.38 showing - was that meant to be
Well its ADSL that gives the WAN. So I expect it to be a serial port, rather than ethernet. Yes 0.38 is correct - its what I used for the last 15 years or so here in the UK, and was the setting before the reflash.
Ah yes - /etc/config/network says its dsl0 - so I guess /dev/dsl0, which I don't have. Hopefully the recompile will give the missing option. Anyway whilst the compile makes it way, I'll check the original kernel config, and see what it defined along the lines of a lantiq serial connection for ADSL ....
I do not believe ATM or PTM interfaces disguise as serial interfaces, but rather normal network interfaces.
But note that there also is no /dev/ethX... How does /etc/config/network look like?
The relevant section of /etc/config/network is:
config dsl 'dsl'
option tone 'av'
option line_mode 'adsl'
option xfer_mode 'atm'
option firmware '/lib/firmware/lantiq-vrx200-a.bin'
option annex 'a2p'
config interface 'wan'
option ifname 'dsl0'
option proto 'pppoa'
option username 'username'
option password 'password'
option vci '38'
option vpi '0'
config device 'wan_dev'
option macaddr 'e8:de:27:9c:c8:bb'
option name 'dsl0'
and /dev contains:
bus mtd2 network_latency
console mtd2ro network_throughput
cpu_dma_latency mtd3 null
dsl_cpe_api0 mtd3ro port
full mtd4 ppp
gpiochip0 mtd4ro ptmx
gpiochip1 mtd5 pts
gptu mtd5ro random
hwrng mtd6 shm
kmsg mtd6ro tty
log mtdblock0 ttyLTQ0
mei_cpe mtdblock1 ubi_ctrl
memory_bandwidth mtdblock2 urandom
mtd0 mtdblock3 watchdog
mtd0ro mtdblock4 zero
The rebuild is still ongoing, looks like it starting again from scratch almost (probably because I added things like nftables to the image, and the various libraries needed ...)
OK - reflash the released 19.07. What my version wasn't displaying in dmesg is:
[ 41.544002] ATM1.0.26 ATM (A1) firmware version 0.24
[ 41.547977] ifxmips_atm: ATM init succeed
Even though the atm kernel module was loaded. Suspect it may be a problem with the ADSL firmware:
/sbin/vdsl_cpe_control -i00_00_00_00_00_01_00_00 -n /sbin/dsl_notify.sh -f /lib/firmware/lantiq-vrx200-a.bin -l /tmp/lowlevel.cfg -M1 -T1:0x1:0x1_1:0x1:0x1
Anyway now I'm back in released 19.07 I dig some more into the atomic replace problems with nftables. I suspect it some iptable nat kernel still left in the kernel ....