KongPro (OpenWRT) - 2019 / 08 / 28

Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3 ... 13, 14, 15 ... 17, 18, 19  Next
Author Message
jasonkruys
DD-WRT User


Joined: 13 Dec 2013
Posts: 90

PostPosted: Sat Jul 27, 2019 13:02    Post subject: Reply with quote
slidermike wrote:
Jason, I've found the same issue when googling for guides.
Almost everything is written for command line.

If you find a nice gui guide, please share.


Hi Slidermike. I found this https://openwrt.org/docs/guide-user/network/wifi/guestwifi/guest-wlan-webinterface

I now have another problem - I cannot turn the router into a dumb AP.

I'm trying to use this methods with the GUI:

Use the web interface to go to Network → Interfaces and select the LAN interface.
Enter an IP address “next to” your main router on the field “IPv4 address”. (If your main router has IP 192.168.1.1, enter 192.168.1.2). Set DNS and gateway to point into your main router to enable internet access for the dumb AP itself
Then scroll down and select the checkbox “Ignore interface: Disable DHCP for this interface.”
Click “IPv6 Settings” tab and set everything to “disabled”.
In the top menu go to System → Startup, and disable firewall, dnsmasq and odhcpd in the list of startup scripts.
Click the Save and Apply button.

No matter what I do, it will not save/change the settings. Everything else works fine, just not this - it remains on the original/default IP with DHCP set to on. Any Clues? I believe you are using yours an an AP with Kongs OpenWRT?
Sponsor
05dyna
DD-WRT Guru


Joined: 25 Jan 2008
Posts: 968

PostPosted: Sat Jul 27, 2019 13:29    Post subject: Reply with quote
jasonkruys wrote:
I now have another problem - I cannot turn the router into a dumb AP.


Rest assured if you are using the 19.07 version its not you, I have the same issue. I too noticed when I configure it and put it in service it will not accept a static IP, it keeps the 192.168.1.1 address which creates an IP conflict. AP mode worked perfect in the past 18.06 builds but not in 19.07, at least not for me so I gave up on it Sad
jasonkruys
DD-WRT User


Joined: 13 Dec 2013
Posts: 90

PostPosted: Sat Jul 27, 2019 13:35    Post subject: Reply with quote
05dyna wrote:
jasonkruys wrote:
I now have another problem - I cannot turn the router into a dumb AP.


Rest assured if you are using the 19.07 version its not you, I have the same issue. I too noticed when I configure it and put it in service it will not accept a static IP, it keeps the 192.168.1.1 address which creates an IP conflict. AP mode worked perfect in the past 18.06 builds but not in 19.07, at least not for me so I gave up on it Sad


Thanks - I am indeed trying to use that version. @<Kong> do you see the issue described above?

EDIT: The fix is simple. Edit the LAN address directly in the Network.conf file using SCP or something. Once you have made that single change, you can then use the GUI to make other changes like disabling DHCP and they will stick.
05dyna
DD-WRT Guru


Joined: 25 Jan 2008
Posts: 968

PostPosted: Sat Jul 27, 2019 23:24    Post subject: Reply with quote
@ jasonkruys , just removed the Netgear stock FW and flashed with the 19.07 Kong build and applied your hack and up and working again. Hopefully Kong will fix it otherwise I'm thinking upgrading from here *may* set it back to 192.168.1.1
labrok
DD-WRT User


Joined: 11 Feb 2011
Posts: 297
Location: Greece

PostPosted: Mon Jul 29, 2019 11:48    Post subject: Linksys EA-8500 Reply with quote
Guys can someone explain this its in my kernel log , is it something serious?

11.797405] mount_root: loading kmods from internal overlay
[ 11.836219] kmodloader: loading kernel modules from //etc/modules-boot.d/*
[ 11.839092] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
[ 11.848791] print_req_error: I/O error, dev mtdblock0, sector 0
[ 11.853950] print_req_error: I/O error, dev mtdblock0, sector 8
[ 11.864028] print_req_error: I/O error, dev mtdblock0, sector 16
[ 11.864486] print_req_error: I/O error, dev mtdblock0, sector 24
[ 11.869755] print_req_error: I/O error, dev mtdblock0, sector 0
[ 11.875081] Buffer I/O error on dev mtdblock0, logical block 0, async page read
[ 11.885324] print_req_error: I/O error, dev mtdblock1, sector 0
[ 11.888470] print_req_error: I/O error, dev mtdblock1, sector 8
[ 11.894447] print_req_error: I/O error, dev mtdblock1, sector 16
[ 11.900285] print_req_error: I/O error, dev mtdblock1, sector 24
[ 11.906768] print_req_error: I/O error, dev mtdblock1, sector 0
[ 11.912063] Buffer I/O error on dev mtdblock1, logical block 0, async page read
[ 12.041364] Buffer I/O error on dev mtdblock2, logical block 0, async page read
[ 12.044231] Buffer I/O error on dev mtdblock3, logical block 0, async page read
[ 12.051321] Buffer I/O error on dev mtdblock4, logical block 0, async page read
[ 12.065369] Buffer I/O error on dev mtdblock5, logical block 3, async page read
[ 12.068226] Buffer I/O error on dev mtdblock6, logical block 0, async page read
[ 12.074373] Buffer I/O error on dev mtdblock7, logical block 0, async page read
[ 12.097009] Buffer I/O error on dev mtdblock9, logical block 0, async page read
[ 12.119870] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 159
[ 12.182873] UBIFS (ubi0:1): recovery needed
[ 12.335817] UBIFS (ubi0:1): recovery completed
[ 12.335899] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[ 12.339148] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 12.347127] UBIFS (ubi0:1): FS size: 12824576 bytes (12 MiB, 101 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
[ 12.357015] UBIFS (ubi0:1): reserved for root: 605735 bytes (591 KiB)
[ 12.367233] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID E53B2E64-AD55-41BD-9059-A5645AB6D3A4, small LPT model
[ 12.385800] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[ 12.395309] block: extroot: not configured
jerrytouille
DD-WRT Guru


Joined: 11 Dec 2015
Posts: 1304

PostPosted: Mon Jul 29, 2019 16:48    Post subject: Reply with quote
same here. r7800

kern.warn kernel: [ 35.271102] print_req_error: 10 callbacks suppressed
kern.err kernel: [ 35.271108] print_req_error: I/O error, dev mtdblock0, sector 0
kern.err kernel: [ 35.271617] print_req_error: I/O error, dev mtdblock0, sector 8
kern.err kernel: [ 35.276511] print_req_error: I/O error, dev mtdblock0, sector 16
kern.err kernel: [ 35.284288] print_req_error: I/O error, dev mtdblock0, sector 24
kern.err kernel: [ 35.290039] print_req_error: I/O error, dev mtdblock0, sector 0
kern.err kernel: [ 35.293979] Buffer I/O error on dev mtdblock0, logical block 0, async page read
kern.err kernel: [ 35.300649] print_req_error: I/O error, dev mtdblock1, sector 0
kern.err kernel: [ 35.307507] print_req_error: I/O error, dev mtdblock1, sector 8
kern.err kernel: [ 35.313293] print_req_error: I/O error, dev mtdblock1, sector 16
kern.err kernel: [ 35.322234] print_req_error: I/O error, dev mtdblock1, sector 24
kern.err kernel: [ 35.325637] print_req_error: I/O error, dev mtdblock1, sector 0
kern.err kernel: [ 35.330954] Buffer I/O error on dev mtdblock1, logical block 0, async page read
labrok
DD-WRT User


Joined: 11 Feb 2011
Posts: 297
Location: Greece

PostPosted: Mon Jul 29, 2019 17:28    Post subject: Reply with quote
jerrytouille wrote:
same here. r7800

kern.warn kernel: [ 35.271102] print_req_error: 10 callbacks suppressed
kern.err kernel: [ 35.271108] print_req_error: I/O error, dev mtdblock0, sector 0
kern.err kernel: [ 35.271617] print_req_error: I/O error, dev mtdblock0, sector 8
kern.err kernel: [ 35.276511] print_req_error: I/O error, dev mtdblock0, sector 16
kern.err kernel: [ 35.284288] print_req_error: I/O error, dev mtdblock0, sector 24
kern.err kernel: [ 35.290039] print_req_error: I/O error, dev mtdblock0, sector 0
kern.err kernel: [ 35.293979] Buffer I/O error on dev mtdblock0, logical block 0, async page read
kern.err kernel: [ 35.300649] print_req_error: I/O error, dev mtdblock1, sector 0
kern.err kernel: [ 35.307507] print_req_error: I/O error, dev mtdblock1, sector 8
kern.err kernel: [ 35.313293] print_req_error: I/O error, dev mtdblock1, sector 16
kern.err kernel: [ 35.322234] print_req_error: I/O error, dev mtdblock1, sector 24
kern.err kernel: [ 35.325637] print_req_error: I/O error, dev mtdblock1, sector 0
kern.err kernel: [ 35.330954] Buffer I/O error on dev mtdblock1, logical block 0, async page read


Then its the old good bug https://forum.openwrt.org/t/blk-update-request-i-o-errors/7865 following the block-mount on IPQ806x Routers the last 2 years, seems that it still hasnt been fixed in 19.07.
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany

PostPosted: Mon Jul 29, 2019 18:13    Post subject: Reply with quote
labrok wrote:
jerrytouille wrote:
same here. r7800

kern.warn kernel: [ 35.271102] print_req_error: 10 callbacks suppressed
kern.err kernel: [ 35.271108] print_req_error: I/O error, dev mtdblock0, sector 0
kern.err kernel: [ 35.271617] print_req_error: I/O error, dev mtdblock0, sector 8
kern.err kernel: [ 35.276511] print_req_error: I/O error, dev mtdblock0, sector 16
kern.err kernel: [ 35.284288] print_req_error: I/O error, dev mtdblock0, sector 24
kern.err kernel: [ 35.290039] print_req_error: I/O error, dev mtdblock0, sector 0
kern.err kernel: [ 35.293979] Buffer I/O error on dev mtdblock0, logical block 0, async page read
kern.err kernel: [ 35.300649] print_req_error: I/O error, dev mtdblock1, sector 0
kern.err kernel: [ 35.307507] print_req_error: I/O error, dev mtdblock1, sector 8
kern.err kernel: [ 35.313293] print_req_error: I/O error, dev mtdblock1, sector 16
kern.err kernel: [ 35.322234] print_req_error: I/O error, dev mtdblock1, sector 24
kern.err kernel: [ 35.325637] print_req_error: I/O error, dev mtdblock1, sector 0
kern.err kernel: [ 35.330954] Buffer I/O error on dev mtdblock1, logical block 0, async page read


Then its the old good bug https://forum.openwrt.org/t/blk-update-request-i-o-errors/7865 following the block-mount on IPQ806x Routers the last 2 years, seems that it still hasnt been fixed in 19.07.


Because it is no bug. It just says, that you can't read this part.

_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
jerrytouille
DD-WRT Guru


Joined: 11 Dec 2015
Posts: 1304

PostPosted: Mon Jul 29, 2019 18:53    Post subject: Reply with quote
jerrytouille wrote:
same here. r7800

kern.warn kernel: [ 35.271102] print_req_error: 10 callbacks suppressed
kern.err kernel: [ 35.271108] print_req_error: I/O error, dev mtdblock0, sector 0
kern.err kernel: [ 35.271617] print_req_error: I/O error, dev mtdblock0, sector 8
kern.err kernel: [ 35.276511] print_req_error: I/O error, dev mtdblock0, sector 16
kern.err kernel: [ 35.284288] print_req_error: I/O error, dev mtdblock0, sector 24
kern.err kernel: [ 35.290039] print_req_error: I/O error, dev mtdblock0, sector 0
kern.err kernel: [ 35.293979] Buffer I/O error on dev mtdblock0, logical block 0, async page read
kern.err kernel: [ 35.300649] print_req_error: I/O error, dev mtdblock1, sector 0
kern.err kernel: [ 35.307507] print_req_error: I/O error, dev mtdblock1, sector 8
kern.err kernel: [ 35.313293] print_req_error: I/O error, dev mtdblock1, sector 16
kern.err kernel: [ 35.322234] print_req_error: I/O error, dev mtdblock1, sector 24
kern.err kernel: [ 35.325637] print_req_error: I/O error, dev mtdblock1, sector 0
kern.err kernel: [ 35.330954] Buffer I/O error on dev mtdblock1, logical block 0, async page read


seems resolved in latest 07/29 build today. solid so far

changelog 07/29/19:
-kernel update 4.14.133
-e2guardian update 5.3.3
-network throughput optimization e.g. cake can now shape up to 450Mbps (depends on type of wan)
-fix override notification display not being able to change routers ip address
labrok
DD-WRT User


Joined: 11 Feb 2011
Posts: 297
Location: Greece

PostPosted: Mon Jul 29, 2019 19:20    Post subject: Reply with quote
jerrytouille wrote:
jerrytouille wrote:
same here. r7800

kern.warn kernel: [ 35.271102] print_req_error: 10 callbacks suppressed
kern.err kernel: [ 35.271108] print_req_error: I/O error, dev mtdblock0, sector 0
kern.err kernel: [ 35.271617] print_req_error: I/O error, dev mtdblock0, sector 8
kern.err kernel: [ 35.276511] print_req_error: I/O error, dev mtdblock0, sector 16
kern.err kernel: [ 35.284288] print_req_error: I/O error, dev mtdblock0, sector 24
kern.err kernel: [ 35.290039] print_req_error: I/O error, dev mtdblock0, sector 0
kern.err kernel: [ 35.293979] Buffer I/O error on dev mtdblock0, logical block 0, async page read
kern.err kernel: [ 35.300649] print_req_error: I/O error, dev mtdblock1, sector 0
kern.err kernel: [ 35.307507] print_req_error: I/O error, dev mtdblock1, sector 8
kern.err kernel: [ 35.313293] print_req_error: I/O error, dev mtdblock1, sector 16
kern.err kernel: [ 35.322234] print_req_error: I/O error, dev mtdblock1, sector 24
kern.err kernel: [ 35.325637] print_req_error: I/O error, dev mtdblock1, sector 0
kern.err kernel: [ 35.330954] Buffer I/O error on dev mtdblock1, logical block 0, async page read


seems resolved in latest 07/29 build today. solid so far

changelog 07/29/19:
-kernel update 4.14.133
-e2guardian update 5.3.3
-network throughput optimization e.g. cake can now shape up to 450Mbps (depends on type of wan)
-fix override notification display not being able to change routers ip address



Yes First time after 2 years my Kernel log hasnt that trash...
jerrytouille
DD-WRT Guru


Joined: 11 Dec 2015
Posts: 1304

PostPosted: Mon Jul 29, 2019 23:14    Post subject: Reply with quote
<Kong> is the extra overhead value between 2-6 bytes still recommended for this build 07/29? i assume the overhead estimator is still there?
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany

PostPosted: Tue Jul 30, 2019 5:14    Post subject: Reply with quote
jerrytouille wrote:
<Kong> is the extra overhead value between 2-6 bytes still recommended for this build 07/29? i assume the overhead estimator is still there?


I'm using no overhead on my vdsl now, as I ran the atm overhead detector which showed that the recommendation for vdsl is not correct for my vdsl line

https://github.com/moeller0/ATM_overhead_detector

_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
labrok
DD-WRT User


Joined: 11 Feb 2011
Posts: 297
Location: Greece

PostPosted: Tue Jul 30, 2019 13:15    Post subject: Reply with quote
jerrytouille wrote:
<Kong> is the extra overhead value between 2-6 bytes still recommended for this build 07/29? i assume the overhead estimator is still there?


do we have to change default overhead on sqm qos from 34 for vdsl over atm to something else?
jerrytouille
DD-WRT Guru


Joined: 11 Dec 2015
Posts: 1304

PostPosted: Tue Jul 30, 2019 13:33    Post subject: Reply with quote
labrok wrote:
jerrytouille wrote:
<Kong> is the extra overhead value between 2-6 bytes still recommended for this build 07/29? i assume the overhead estimator is still there?


do we have to change default overhead on sqm qos from 34 for vdsl over atm to something else?


it depends on your line. use the tool kong shared
aaronburrsir108
DD-WRT Novice


Joined: 05 Jan 2019
Posts: 3

PostPosted: Tue Jul 30, 2019 13:58    Post subject: Reply with quote
Is there an easy way to completely disable ipv6 ? I've tried via sysctl but the module still gets loaded. I would like to set 'ipv6.disable=1' as a kernel boot parameter but not quite how to do that.

thanks
Goto page Previous  1, 2, 3 ... 13, 14, 15 ... 17, 18, 19  Next Display posts from previous:    Page 14 of 19
Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum