Why I can't get ip adress in openwrt in Phicomm N1 Router?

I had Phicomm N1 Router and no user 2 years, today I want to make it as Secondary Router, because I am in China mainland can't visit some foregine website , only can throught VPN to visit.
Frist I connect N1 to main Router LAN port and visit it with 192.168.123.200 but can't ping with my windows pc, then I connect N1 with a Portable Screen in CLI,I enter ifconfig showing IP address is 192.168.123.200 and gateway is 192.168.123.1 but can't ping with 192.168.123.1, so I change /etc/config/network like this:

 config interface 'lan' 

option ifname 'eth0'
option proto 'dhcp'
##option ipaddr '192.168.123.200'
##option netmask '255.255.255.0'
##option gateway '192.168.123.1'
##option dns '114.114.114.114 8.8.8.8
option type 'brige'
option _org_ifname 'eth0 wlan0'
option _org_bridge 'true'

But whether I using static or dhcp the os can't get IP address, I reboot and /etc/init.d/network restart many times is invalid,my screenshot and Network topology diagram is below , someone can help me ,thanks a lot!

why not simply run it as a router ?

This configuration can work with the default configuration. Do a reset to defaults and plug the wan port of N1 to the uplink router's lan port.

Because I want to make it as Secondary Router

how can I config? can you give me detail configuartion, thanks

That's usually how they come configured, even if you run Openwrt.

Connect the wan port, and you're all set ?

Go to System-Backup-Reset to defaults in Luci.

I had solved it,
first edit etc/config/network:

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


config interface 'lan'
        option ifname 'eth0'
        option proto 'static'
        option ipaddr '192.168.3.99'
        option netmask '255.255.255.0'
        option gateway '192.168.3.1'
        option dns '114.114.114.114 8.8.8.8'

then set the ip as below

you don't show us anything about the wan port, but if it's still on the 192.168.123 subnet, you're good to go, and you're running it as a router, as suggested 10 days ago.