找回密码
 立即注册

QQ登录

只需一步,快速开始

搜索
广告投放联系QQ68610888
查看: 5818|回复: 3

求助!PPPOE无法拔号,拔号失败

[复制链接]
发表于 2019-11-27 22:50 | 显示全部楼层 |阅读模式
本帖最后由 microsen 于 2020-1-3 11:07 编辑

近日刷了openwrt X86 64的固件,作为二级路由DHCP方式上网是正常的,但是如果用光猫作桥接软路由拔号,无法拔号拔号失败,并且mac地址消失。请各位大侠帮忙解惑!
有关的截图如下:
DHCP上网截图:

PPPOE拔号失败截图:



下面是日志,是不是少了什么组件?
Tue Nov 26 19:12:22 2019 daemon.notice netifd: Network device 'eth0' link is up
Tue Nov 26 19:12:22 2019 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Nov 26 19:12:22 2019 daemon.notice netifd: Interface 'wan' is setting up now
Tue Nov 26 19:12:22 2019 kern.info kernel: [  607.767712] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Tue Nov 26 19:12:22 2019 daemon.err insmod: module is already loaded - slhc
Tue Nov 26 19:12:22 2019 daemon.err insmod: module is already loaded - ppp_generic
Tue Nov 26 19:12:22 2019 daemon.err insmod: module is already loaded - pppox
Tue Nov 26 19:12:22 2019 daemon.err insmod: module is already loaded - pppoe
Tue Nov 26 19:12:22 2019 daemon.info pppd[629]: Plugin rp-pppoe.so loaded.
Tue Nov 26 19:12:22 2019 daemon.info pppd[629]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Tue Nov 26 19:12:22 2019 daemon.notice pppd[629]: pppd 2.4.7 started by root, uid 0
Tue Nov 26 19:12:32 2019 daemon.info dnscrypt-proxy[10818]: dnscrypt-proxy Refetching server certificates
Tue Nov 26 19:12:42 2019 daemon.warn pppd[629]: Timeout waiting for PADS packets
Tue Nov 26 19:12:42 2019 daemon.err pppd[629]: Unable to complete PPPoE Discovery
Tue Nov 26 19:12:42 2019 daemon.info pppd[629]: Exit.
Tue Nov 26 19:12:42 2019 daemon.notice netifd: Interface 'wan' is now down
Tue Nov 26 19:12:42 2019 daemon.notice netifd: Interface 'wan' is disabled
Tue Nov 26 19:12:42 2019 kern.info kernel: [  628.085120] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Tue Nov 26 19:12:42 2019 kern.info kernel: [  628.085410] 8021q: adding VLAN 0 to HW filter on device eth0
Tue Nov 26 19:12:42 2019 daemon.notice netifd: Interface 'wan' is enabled
Tue Nov 26 19:12:42 2019 daemon.notice netifd: Interface 'wan' is setting up now
Tue Nov 26 19:12:42 2019 daemon.notice netifd: Network device 'eth0' link is down
Tue Nov 26 19:12:42 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Nov 26 19:12:42 2019 daemon.notice netifd: Interface 'wan' is now down
Tue Nov 26 19:12:42 2019 daemon.notice netifd: Interface 'wan' is disabled
Tue Nov 26 19:12:42 2019 daemon.notice netifd: Interface 'wan' is enabled
Tue Nov 26 19:12:42 2019 kern.info kernel: [  628.160121] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Tue Nov 26 19:12:42 2019 kern.info kernel: [  628.160410] 8021q: adding VLAN 0 to HW filter on device eth0
Tue Nov 26 19:12:43 2019 user.notice mwan3[1013]: Execute ifdown event on interface wan (unknown)
Tue Nov 26 19:12:43 2019 user.info mwan3track[19686]: Detect ifdown event on interface wan (eth0)
Tue Nov 26 19:12:43 2019 user.info mwan3[1013]: connection tracking not flushed on interface wan (ifdown)
Tue Nov 26 19:12:44 2019 user.notice unbound: default root hints (built in rootservers.net)
Tue Nov 26 19:12:44 2019 user.notice unbound: default protocol configuration
Tue Nov 26 19:12:44 2019 user.notice unbound: default memory configuration
Tue Nov 26 19:12:44 2019 user.notice unbound: default recursion configuration
Tue Nov 26 19:12:45 2019 daemon.info procd: Instance unbound::unbound s in a crash loop 26 crashes, 0 seconds since last crash
Tue Nov 26 19:12:46 2019 daemon.notice netifd: Network device 'eth0' link is up
Tue Nov 26 19:12:46 2019 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Nov 26 19:12:46 2019 daemon.notice netifd: Interface 'wan' is setting up now
Tue Nov 26 19:12:46 2019 kern.info kernel: [  631.617548] igb 0000:01:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Contro轩l: RX/TX
Tue Nov 26 19:12:46 2019 kern.info kernel: [  631.618284] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Tue Nov 26 19:12:46 2019 daemon.err insmod: module is already loaded - slhc
Tue Nov 26 19:12:46 2019 daemon.err insmod: module is already loaded - ppp_generic
Tue Nov 26 19:12:46 2019 daemon.err insmod: module is already loaded - pppox
Tue Nov 26 19:12:46 2019 daemon.err insmod: module is already loaded - pppoe
Tue Nov 26 19:12:46 2019 daemon.info pppd[1592]: Plugin rp-pppoe.so loaded.
Tue Nov 26 19:12:46 2019 daemon.info pppd[1592]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Tue Nov 26 19:12:46 2019 daemon.notice pppd[1592]: pppd 2.4.7 started by root, uid 0
Tue Nov 26 19:12:47 2019 daemon.err dnscrypt-proxy[10818]: dnscrypt-proxy Unable to retrieve server certificates
问题已解决,应该是固件网络配置的问题。我是这样解决的,找一个能正常拔号的固件,备份配置。把能正常拔号的配置和不能拔号的配置,逐一比对相同的文件的部分,用能拔号的配置文件代替不能拔号的,再恢复回去重启,就可以拔号上网了。试了几个不能拔号的固件,都是这样的解决的。




本帖子中包含更多资源

您需要 登录 才可以下载或查看,没有账号?立即注册

×
只谈技术、莫论政事!(点击见详情) | 恩山无线论坛欢迎您的来访,请互相尊重、友善交流,建议保持一颗平常心看待网友的评论,切勿过度反应。
 楼主| 发表于 2019-12-5 10:28 | 显示全部楼层
没办法,用各种各样的方法不断试错,恩山论坛的固件有一个就可以,其他的就不行。用隔壁K论坛的固件就一次设置就成功PPPOE拔号,然后再想办法安装心知肚明的工具软件。有空自己再折腾编译openwrt,看看是什么原因造成的。
只谈技术、莫论政事!(点击见详情) | 恩山无线论坛欢迎您的来访,请互相尊重、友善交流,建议保持一颗平常心看待网友的评论,切勿过度反应。
回复 支持 反对

使用道具 举报

发表于 2019-12-5 11:49 | 显示全部楼层
看看是不是驱动问题?
只谈技术、莫论政事!(点击见详情) | 恩山无线论坛欢迎您的来访,请互相尊重、友善交流,建议保持一颗平常心看待网友的评论,切勿过度反应。
回复 支持 反对

使用道具 举报

发表于 2019-12-5 14:37 来自手机 | 显示全部楼层
首先要分清楚你的X86的OP固件的网口有没有搞错Lan和wan口;其次还要看看拨号的账号密码有没有搞错了,最后是安装其他固件试试是不是固件问题。
只谈技术、莫论政事!(点击见详情) | 恩山无线论坛欢迎您的来访,请互相尊重、友善交流,建议保持一颗平常心看待网友的评论,切勿过度反应。
回复 支持 反对

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

关闭

欢迎大家光临恩山无线论坛上一条 /1 下一条

有疑问请添加管理员QQ86788181|手机版|小黑屋|Archiver|恩山无线论坛(常州市恩山计算机开发有限公司版权所有) ( 苏ICP备05084872号 )

GMT+8, 2024-9-23 06:30

Powered by Discuz! X3.5

© 2001-2024 Discuz! Team.

| 江苏省互联网有害信息举报中心 举报信箱:js12377 | @jischina.com.cn 举报电话:025-88802724 本站不良内容举报信箱:68610888@qq.com

快速回复 返回顶部 返回列表