Good afternoon,
I try to replace my R1 by a R2
I use armbian with kernel 4.19.1-mt7623
I have configure interface
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether aa:f0:f0:7a:4b:08 brd ff:ff:ff:ff:ff:ff
3: wan@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether aa:f0:f0:7a:4b:08 brd ff:ff:ff:ff:ff:ff
4: lan0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 02:19:04:d6:b8:3d brd ff:ff:ff:ff:ff:ff
inet 192.168.101.254/24 brd 192.168.101.255 scope global lan0
valid_lft forever preferred_lft forever
5: lan1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 02:19:04:e7:c9:4e brd ff:ff:ff:ff:ff:ff
inet 192.168.97.254/24 brd 192.168.97.255 scope global lan1
valid_lft forever preferred_lft forever
6: lan2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 02:19:04:f8:d0:5f brd ff:ff:ff:ff:ff:ff
inet 192.168.19.254/24 brd 192.168.19.255 scope global lan2
valid_lft forever preferred_lft forever
7: lan3@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 02:19:04:09:e1:60 brd ff:ff:ff:ff:ff:ff
inet 192.168.57.2/24 brd 192.168.57.255 scope global lan3
valid_lft forever preferred_lft forever
I have a laptop connect to lan1, I have acces to laptop connect to:
lan2
lan3
It’s possible for a laptop connect to lan0 to get an IP by DHCP server on R2.
But not possible for a latpop on lan0 to connect to R2 or communicated to a laptop on lan1 or lan2, or lan3.
I have delete all iptables rules.
I don’t know if it’s an hardware issue or configuration.
Do you have any suggestion for solved my issue.
Thank you for your help
frank-w
(Frank W.)
March 4, 2019, 4:24pm
2
It will be interesring if your client gets an ip on lan0 in lan0-ip-subnet. If not look if your dhcp listens on lan0
client on lan0 get an IP from lan0-ip-subnet, and dhcp listens on lan0.
After new test,
a dhcp client connect on lan0 don’t receive an IP.
Mar 5 11:00:50 srvprotect2 dhcpd[1075]: DHCPDISCOVER from 6c:62:6d:c8:f0:50 via lan0
Mar 5 11:00:50 srvprotect2 dhcpd[1075]: DHCPOFFER on 192.168.101.49 to 6c:62:6d:c8:f0:50 via lan0
Mar 5 11:00:59 srvprotect2 dhcpd[1075]: DHCPDISCOVER from 6c:62:6d:c8:f0:50 via lan0
Mar 5 11:00:59 srvprotect2 dhcpd[1075]: DHCPOFFER on 192.168.101.49 to 6c:62:6d:c8:f0:50 via lan0
I don’t understand this issue.
Because on BPI R1 is functionnal.
Thank you for your help
When I configure lan2 with same parameters that lan0 and lan0 with same parameters that lan2.
I have issue on lan2.
Maybe on a armbian file lan0 do a specific config ?
frank-w
(Frank W.)
March 5, 2019, 4:16pm
6
Can you try to configure static ip on client connected to lan0 in same subnet and try to access r2 (lan0,lanx by routing)
I have make this test and I don’t have access to R2.
Information about armbian
http://ix.io/1CEs
frank-w
(Frank W.)
March 5, 2019, 9:09pm
9
Have you tried putting eth0 and lan0 to down and then eth0 to up and then lan0 to up?
Maybe eth0 is not full up when putting lan0 to up…lan1+ gets a link-up message in dmesg but not lan0
No, I try with theses commands ?
ip link set eth0 down
ip link set lan0 down
ip link set eth0 up
ip link set lan0 up
frank-w
(Frank W.)
March 5, 2019, 9:14pm
11
Right (wait a bit between eth0 up and lan0 up), imho armbian uses a strange trick (configure dhcp on eth0) to get eth0 up on boot
I have trying, same issue.
Not possible to connect to R2 from a laptop on lan0
Not possible to ping a laptop on lan0
frank-w
(Frank W.)
March 5, 2019, 9:27pm
13
You can try another image like my debian to test for config-issue
I download it and I try.
But I have always issue with WAN interface : state LOWERLAYERDOWN
For test I use debian image and add kernel 4.19 ?
frank-w
(Frank W.)
March 6, 2019, 6:03am
16
you have set eth1 also up…like it’s done in default /etc/network/interfaces…do not remove eth0/eth1 block
andarius40
(andarius40)
March 11, 2019, 10:24pm
17
Hello,
I have try with your image, now it’s ok.
I have a message when I add IPTABLE rules
libkmod: ERROR ../libkmod/libkmod-config.c:635 kmod_config_parse: /etc/modprobe.d/mtk_pmic_keys.conf line 1: ignoring bad line starting with '“blacklist'
Thank you for your help.
frank-w
(Frank W.)
March 12, 2019, 10:27am
18
hi,
this line is for users who have soldered their power-switch (to boot r2 on powersupply). i wonder about this error (especially the second quote)…can you look in this file and remove quotes if there is any present? it should only contain this:
blacklist mtk_pmic_keys
andarius40
(andarius40)
March 13, 2019, 10:05pm
19
Hello,
Thank you issue is solved.
I have replace my R1 by my R2.
Thank you yet.