EdgeCore-EAP102

Installing and Using OpenWrt
41

On the other end try chaanging port from LAN to WAn the device notices it

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 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
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: miireg: <> mtu 0 qdisc noop state DOWN qlen 1000
    link/generic
3: wan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 14:44:8f:1f:b8:19 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::1644:8fff:fe1f:b819/64 scope link
       valid_lft forever preferred_lft forever
4: lan: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br-lan state DOWN qlen 1000
    link/ether 14:44:8f:1f:b8:1a brd ff:ff:ff:ff:ff:ff
5: br-lan: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN qlen 1000
    link/ether 14:44:8f:1f:b8:1a brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.1/24 brd 192.168.1.255 scope global br-lan
       valid_lft forever preferred_lft forever
    inet6 fdab:cfae:2059::1/60 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::1644:8fff:fe1f:b81a/64 scope link
       valid_lft forever preferred_lft forever
root@OpenWrt:/# [  831.593137] nss-dp 3a001800.dp5 wan: PHY Link is down
[  833.593007] nss-dp 3a001a00.dp6 lan: PHY Link up speed: 1000
[  833.593090] br-lan: port 1(lan) entered blocking state
[  833.597744] br-lan: port 1(lan) entered forwarding state

I tried to connect with a different pc too (a laptop)..but nothing

42

Please try switching wan and lan port in the network config, restart network and try the wan port as lan.

43

Nothing!

root@OpenWrt:/# /etc/init.d/network restart
[ 1843.960310] br-lan: port 1(lan) entered disabled state
[ 1843.961843] device lan left promiscuous mode
[ 1843.964485] br-lan: port 1(lan) entered disabled state
[ 1843.993705] nss-dp 3a001a00.dp6 lan: PHY Link is down
root@OpenWrt:/# [ 1845.904443] br-wan: port 1(wan) entered blocking state
[ 1845.904487] br-wan: port 1(wan) entered disabled state
[ 1845.908720] device wan entered promiscuous mode
[ 1847.993356] nss-dp 3a001a00.dp6 lan: PHY Link up speed: 1000
[ 1847.993429] IPv6: ADDRCONF(NETDEV_CHANGE): lan: link becomes ready
[ 1854.233595] nss-dp 3a001a00.dp6 lan: PHY Link is down
[ 1857.353413] nss-dp 3a001800.dp5 wan: PHY Link up speed: 1000
[ 1857.353505] br-wan: port 1(wan) entered blocking state
[ 1857.358150] br-wan: port 1(wan) entered forwarding state
[ 1857.363413] IPv6: ADDRCONF(NETDEV_CHANGE): br-wan: link becomes ready
ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: seq=0 ttl=64 time=0.218 ms
64 bytes from 192.168.1.1: seq=1 ttl=64 time=0.121 ms
^C
--- 192.168.1.1 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.121/0.169/0.218 ms
root@OpenWrt:/# ping 192.168.1.17
PING 192.168.1.17 (192.168.1.17): 56 data bytes
^C
--- 192.168.1.17 ping statistics ---
107 packets transmitted, 0 packets received, 100% packet loss
root@OpenWrt:/#
44

Just change the config like that:

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'wan'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config interface 'wan'
        option device 'lan'
        option proto 'dhcp'

And try again the wan port as lan

45

ehm...already done as posted above:

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fdab:cfae:2059::/48'

config device
        option name 'br-wan'
        option type 'bridge'
        list ports 'wan'

config interface 'wan'
        option device 'br-wan'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config interface 'lan'
        option device 'lan'
        option proto 'dhcp'

config interface 'wan6'
        option device 'wan'
        option proto 'dhcpv6'
46

I don't think (from your network script) you mean bridge LAN and WAN togheter, only swap LAN with WAN...The thing I done

47

I mean just switching lan and wan port (not the interfaces)

You created a new bridge br-wan....

Anyway, please revert the network config back to default and connect the wan port to a lan port of another router and check if the EAP102 is getting a WAN IP

48

Done, I see the interface connected but I can't see MAC address on the router DHCP server, infact eap102 wan can't get IP

root@OpenWrt:/# ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 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
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: miireg: <> mtu 0 qdisc noop state DOWN qlen 1000
    link/generic
3: wan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 14:44:8f:1f:b8:19 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::1644:8fff:fe1f:b819/64 scope link
       valid_lft forever preferred_lft forever
4: lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UP qlen 1000
    link/ether 14:44:8f:1f:b8:1a brd ff:ff:ff:ff:ff:ff
7: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 14:44:8f:1f:b8:1a brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.1/24 brd 192.168.1.255 scope global br-lan
       valid_lft forever preferred_lft forever
    inet6 fdab:cfae:2059::1/60 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::1644:8fff:fe1f:b81a/64 scope link
       valid_lft forever preferred_lft forever
49

Well, then may be one of the last commits broke the device support, but without having that thing on my table it's hard to debug.

50

I tried all the commit from 23.05...is it possible to have some older working just to use the device , waiting for a late update?

51

Hard to say without knowing the faulty commit.

But if all the 23.05 images aren't working, it could be long time ago...but I can't find any obvious in the ipq807x commit history for that device

52

You can try to ping @clayface , he added support for that device

53

Thank you kirdes

54

Another idea that came in my mind, may be the manufacturer has slightly modified that device but is using the same name.

Can you post the fcc-id of that device?

55
56

Yeah I now, but i wanted to now, if this is actually the same fcc-id @Ringo is using :wink:

57

good thinking!

58

Hi all
FCC ID: YZKEAP102
HW: R01

59

I already tested that version, but same problems

60

Hi, I've create a PR to fix lan/wan on the edgecore EAP102:

Thanks Ringo for testing!