jasonwang 发表于 2016-5-30 07:48

烽火AP2400硬改WAN后识别不到的原因?

本帖最后由 jasonwang 于 2016-5-30 08:03 编辑

机器是烽火AP2400-20AN, AR7161主控, 交换机AR8316, 国外机原型是JA76PF2, 国外机型有WAN口, 国内机没WAN口, 现人工增加了网变,电阻,电容, 开机瞬间网口灯都复位亮一下, 现故障情况:
1. LAN灯显示正常
2. WAN口插线,物理灯都不亮,电脑上提示未插网线

现在不知道是硬改的不对,还是固件刷的不对, 希望各位大神们给指点下

TTL截取的信息如下:
[    1.460000] ar8316: Using port 4 as switch port
[    1.490000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00
[    1.500000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RGMII(LAN?)
[    1.830000] ar8316: Using port 4 as PHY
[    2.870000] ag71xx ag71xx.1: connected to PHY at ag71xx-mdio.0:04
[    2.880000] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:RGMII(WAN?)


root@OpenWrt:/# ifconfig
br-lan    Link encap:EthernetHWaddr 00:26:7A:20:4D:A7
          inet addr:192.168.1.1Bcast:192.168.1.255Mask:255.255.255.0
          inet6 addr: fe80::226:7aff:fe20:4da7/64 Scopeink
          inet6 addr: fd26:f41c:6526::1/60 Scope:Global
          UP BROADCAST RUNNING MULTICASTMTU:1500Metric:1
          RX packets:207 errors:0 dropped:0 overruns:0 frame:0
          TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:16914 (16.5 KiB)TX bytes:5464 (5.3 KiB)

eth0      Link encap:EthernetHWaddr 00:26:7A:20:4D:A7
          UP BROADCAST RUNNING MULTICASTMTU:1500Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:179 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)TX bytes:16722 (16.3 KiB)
          Interrupt:4

eth1      Link encap:EthernetHWaddr 00:26:7A:20:4D:A8
          UP BROADCAST MULTICASTMTU:1500Metric:1
          RX packets:251 errors:0 dropped:0 overruns:0 frame:0
          TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:34953 (34.1 KiB)TX bytes:3034 (2.9 KiB)
          Interrupt:5 (这里有WAN啊,LUCI界面中只有一个ETH0)

lo      Link encapocal Loopback
          inet addr:127.0.0.1Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNINGMTU:65536Metric:1
          RX packets:432 errors:0 dropped:0 overruns:0 frame:0
          TX packets:432 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:29376 (28.6 KiB)TX bytes:29376 (28.6 KiB)

root@OpenWrt:/# eth1: link up (100Mbps/Full duplex)
br-lan: port 2(eth1) entered forwarding state
br-lan: port 2(eth1) entered forwarding state
br-lan: port 2(eth1) entered forwarding state
br-lan: port 2(eth1) entered disabled state
br-lan: port 1(eth0) entered disabled state
device eth0 left promiscuous mode
br-lan: port 1(eth0) entered disabled state
eth0: link down
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
device eth1 left promiscuous mode
br-lan: port 2(eth1) entered disabled state
eth1: link down
IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
br-lan: port 2(eth1) entered forwarding state
br-lan: port 2(eth1) entered forwarding state
br-lan: port 1(eth0) entered forwarding state
br-lan: port 1(eth0) entered forwarding state
eth1: link up (100Mbps/Full duplex)开机复位吧?
br-lan: port 1(eth0) entered disabled state
eth0: link up (1000Mbps/Full duplex) 开机复位吧?
br-lan: port 1(eth0) entered forwarding state
br-lan: port 1(eth0) entered forwarding state
br-lan: port 2(eth1) entered forwarding state
br-lan: port 1(eth0) entered forwarding state
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
device wlan0 entered promiscuous mode
br-lan: port 3(wlan0) entered forwarding state
br-lan: port 3(wlan0) entered forwarding state
IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
br-lan: port 3(wlan0) entered forwarding state
device wlan0 left promiscuous mode
br-lan: port 3(wlan0) entered disabled state
IPv6: ADDRCONF(NETDEV_UP): wlan0-1: link is not ready
device wlan0-1 entered promiscuous mode
br-lan: port 3(wlan0-1) entered forwarding state
br-lan: port 3(wlan0-1) entered forwarding state
br-lan: port 3(wlan0-1) entered disabled state
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: authenticate with a8:57:4e:83:a6:b8
wlan0: send auth to a8:57:4e:83:a6:b8 (try 1/3)
wlan0: authenticated
wlan0: associate with a8:57:4e:83:a6:b8 (try 1/3)
wlan0: RX AssocResp from a8:57:4e:83:a6:b8 (capab=0x431 status=0 aid=2)
wlan0: associated
IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
br-lan: port 3(wlan0-1) entered forwarding state
br-lan: port 3(wlan0-1) entered forwarding state
IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready
br-lan: port 3(wlan0-1) entered forwarding state


http://img.mydigit.net/Mon_1605/147_18116_ccd54eb608258af.jpg

硬改增加的WAN口4个电容,8个电阻,下面那组是我加的,测量过焊接没问题
http://img.mydigit.net/Mon_1605/147_18116_ecca12231572262.jpg

正面可见增加的网变和网口,以及两个小电阻(负责两个网灯的,开机复位网灯亮,说明电阻焊接没问题)
http://img.mydigit.net/Mon_1605/147_18116_043c56ae4a583b7.jpg


何十二 发表于 2016-5-30 12:20

原版系统可能不支持,人家刷OP都支持有用的

cloudq 发表于 2016-5-30 13:45

论坛不是有改成功的么?

jasonwang 发表于 2016-5-31 18:15

cloudq 发表于 2016-5-30 13:45
论坛不是有改成功的么?

问题是改成功的大神们都不出来,也没成功时的照片,只是说成功了

cloudq 发表于 2016-5-31 18:16

jasonwang 发表于 2016-5-31 18:15
问题是改成功的大神们都不出来,也没成功时的照片,只是说成功了

你飞的线是改成12V了还是5V了

jasonwang 发表于 2016-5-31 22:06

cloudq 发表于 2016-5-31 18:16
你飞的线是改成12V了还是5V了

5V

cloudq 发表于 2016-6-1 09:32

论坛里那个改成功的帖子,你看看,还有你不认识蚊子么?蚊子 QQ53416855
页: [1]
查看完整版本: 烽火AP2400硬改WAN后识别不到的原因?