thelonelycoder
Part of the Furniture
Any entries of interest in the Syslog?Yes and yes
.View attachment 15692
Also, what makes you think Diversion (supposedly) did not start?
Any entries of interest in the Syslog?Yes and yes
.View attachment 15692
It says it right there. You disabled Diversion in d.I had to manually start pixelserv-tls and reenable Diversion manually.
Jan 2 17:20:19 usb: USB ext4 fs at /dev/sda1 mounted on /tmp/mnt/USBStick.
Jan 2 17:20:21 custom_script: Running /jffs/scripts/post-mount (args: /tmp/mnt/USBStick ) - max timeout = 120s
Also, this one log entry caught my eye. --->> Jan 2 17:20:22 Diversion: pixelserv-tls or Diversion disabled, not starting pixelserv-tls, from /opt/etc/init.d/S80pixelserv-tls
Jan 2 17:20:22 Diversion: started Entware services, from /jffs/scripts/post-mount
Jan 2 17:20:23 rc_service: service 756:notify_rc restart_dnsmasq
Jan 2 17:20:23 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf ) - max timeout = 120s
Jan 2 17:20:24 Diversion: is disabled, no services enabled, from /jffs/scripts/dnsmasq.postconf
Dec 30 01:18:21 rc_service: udhcpc 1089:notify_rc start_upnp
Dec 30 01:18:21 rc_service: waitting "stop_upnp" via udhcpc ...
Dec 30 01:18:22 kernel: scsi 0:0:0:0: Direct-Access SCSI DISK 1.00 PQ: 0 ANSI: 4
Dec 30 01:18:22 kernel: sd 0:0:0:0: [sda] 2007648 512-byte logical blocks: (1.03 GB/980 MiB)
Dec 30 01:18:22 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Dec 30 01:18:22 kernel: sd 0:0:0:0: [sda] Write Protect is off
Dec 30 01:18:22 kernel: sd 0:0:0:0: [sda] No Caching mode page found
Dec 30 01:18:22 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec 30 01:18:22 kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
Dec 30 01:18:22 disk_monitor: Finish
Dec 30 01:18:22 disk_monitor: be idle
Dec 30 01:18:22 miniupnpd[1306]: HTTP listening on port 55636
Dec 30 01:18:22 miniupnpd[1306]: Listening for NAT-PMP/PCP traffic on port 5351
Dec 30 01:18:23 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Dec 30 01:18:23 kernel: EXT4-fs (sda1): Couldn't mount because of unsupported optional features (20000000)
Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
Dec 30 01:18:23 usb: USB /dev/sda1(ext) failed to mount at the first try!
Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
Dec 30 01:18:23 kernel: EXT4-fs (sda1): Couldn't mount because of unsupported optional features (20000000)
Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
Dec 30 01:18:23 kernel: EXT4-fs (sda1): Couldn't mount because of unsupported optional features (20000000)
Dec 30 01:18:23 kernel: EXT4-fs (sda1): Couldn't mount because of unsupported optional features (20000000)
Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
Dec 30 01:18:23 usb: USB /dev/sda1(ext) failed to mount at the first try!
Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
Dec 30 01:18:23 kernel: EXT4-fs (sda1): Couldn't mount because of unsupported optional features (20000000)
Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
Dec 30 01:18:23 kernel: EXT4-fs (sda1): Couldn't mount because of unsupported optional features (20000000)
Whatever that unsupported feature is...EXT4-fs (sda1): Couldn't mount because of unsupported optional features (20000000)
Basically you formatted the USB with a new tool that the router firmware does not recognize. Search in the forum to get help on that.@thelonelycoder - I have the same settings as "Rob O" above but when I looked at /tmp/syslog.log, I saw the following lines. The disk was formatted ext4 before diversion was installed. I see it is still mounted in the latest router merlin firmware web-ui
Code:Dec 30 01:18:21 rc_service: udhcpc 1089:notify_rc start_upnp Dec 30 01:18:21 rc_service: waitting "stop_upnp" via udhcpc ... Dec 30 01:18:22 kernel: scsi 0:0:0:0: Direct-Access SCSI DISK 1.00 PQ: 0 ANSI: 4 Dec 30 01:18:22 kernel: sd 0:0:0:0: [sda] 2007648 512-byte logical blocks: (1.03 GB/980 MiB) Dec 30 01:18:22 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Dec 30 01:18:22 kernel: sd 0:0:0:0: [sda] Write Protect is off Dec 30 01:18:22 kernel: sd 0:0:0:0: [sda] No Caching mode page found Dec 30 01:18:22 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Dec 30 01:18:22 kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Dec 30 01:18:22 disk_monitor: Finish Dec 30 01:18:22 disk_monitor: be idle Dec 30 01:18:22 miniupnpd[1306]: HTTP listening on port 55636 Dec 30 01:18:22 miniupnpd[1306]: Listening for NAT-PMP/PCP traffic on port 5351 Dec 30 01:18:23 nat: apply nat rules (/tmp/nat_rules_eth0_eth0) Dec 30 01:18:23 kernel: EXT4-fs (sda1): Couldn't mount because of unsupported optional features (20000000) Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities Dec 30 01:18:23 usb: USB /dev/sda1(ext) failed to mount at the first try! Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities Dec 30 01:18:23 kernel: EXT4-fs (sda1): Couldn't mount because of unsupported optional features (20000000) Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities Dec 30 01:18:23 kernel: EXT4-fs (sda1): Couldn't mount because of unsupported optional features (20000000) Dec 30 01:18:23 kernel: EXT4-fs (sda1): Couldn't mount because of unsupported optional features (20000000) Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities Dec 30 01:18:23 usb: USB /dev/sda1(ext) failed to mount at the first try! Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities Dec 30 01:18:23 kernel: EXT4-fs (sda1): Couldn't mount because of unsupported optional features (20000000) Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities Dec 30 01:18:23 kernel: EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities Dec 30 01:18:23 kernel: EXT4-fs (sda1): Couldn't mount because of unsupported optional features (20000000)
Minitool Partition Wizard (Free edition) works well. I've formatted my USB stick with the ext4 filesystem. No idea if I should have used ext2 for a stick less than 1GB but it works.Try Disk Genius, www.diskgenius.com
Never had any issues with that tool.
That's the one I usedMinitool Partition Wizard (Free edition) works well. I've formatted my USB stick with the ext4 filesystem. No idea if I should have used ext2 for a stick less than 1GB but it works.
Minitool Partition Wizard (Free edition) works well. I've formatted my USB stick with the ext4 filesystem. No idea if I should have used ext2 for a stick less than 1GB but it works.
That's already built into filter by term. Just enter the IP as term.@thelonelycoder Hey! If it's not too much work can you also add the ability to filter "unfiltered log" by IP address. For example if I want to see all the unfiltered log originating from a single IP.
That's already built into filter by term. Just enter the IP as term.
If you look at /opt/var/log/dnsmasq.log and search for the IP, what lines do you find with the IP?I already know about it but that doesn't show complete unfiltered log with details of blocked domains and answered queries etc. It simply shows all the A queries being done from that IP.
If you look at /opt/var/log/dnsmasq.log and search for the IP, what lines do you find with the IP?
You mean to highlight lines containing the IP? It would mark the same lines as only those contain the IP.This is exactly what I'm saying, right now filter by term option is only greping out the lines which includes the term input by user and not showing any other lines except "query[A]" line
If I input my IP as a filter term I'm just getting "query[A]" lines from the log and no "reply" lines etc
I hope I'm making any sense to you lol
You mean to highlight lines containing the IP? It would mark the same lines as only those contain the IP.
I see. That's doable. As an example, this is a query from 172.20.16 with the follow up lines associated with it.No, look this is what I get if I use option 4 and enter my IP address as a filter term:
Jan 4 02:31:19 dnsmasq[9297]: query[A] itunes.apple.com from 10.0.0.5
Jan 4 02:31:19 dnsmasq[9297]: query[A] itunes.apple.com from 10.0.0.5
Jan 4 02:31:19 dnsmasq[9297]: query[A] app-measurement.com from 10.0.0.5
Jan 4 02:31:19 dnsmasq[9297]: query[A] app-measurement.com from 10.0.0.5
Jan 4 02:31:19 dnsmasq[9297]: query[A] p45-buy.itunes.apple.com from 10.0.0.5
Jan 4 02:31:19 dnsmasq[9297]: query[A] p45-buy.itunes.apple.com from 10.0.0.5
Jan 4 02:31:19 dnsmasq[9297]: query[A] ads.mopub.com from 10.0.0.5
Jan 4 02:31:19 dnsmasq[9297]: query[A] ads.mopub.com from 10.0.0.5
Jan 4 02:31:19 dnsmasq[9297]: query[A] www.google.com from 10.0.0.5
Jan 4 02:31:19 dnsmasq[9297]: query[A] www.google.com from 10.0.0.5
Jan 4 02:31:19 dnsmasq[9297]: query[A] googleads.g.doubleclick.net from 10.0.0.5
Jan 4 02:31:19 dnsmasq[9297]: query[A] googleads.g.doubleclick.net from 10.0.0.5
Jan 4 02:31:20 dnsmasq[9297]: query[A] report.appmetrica.yandex.net from 10.0.0.5
Jan 4 02:31:20 dnsmasq[9297]: query[A] report.appmetrica.yandex.net from 10.0.0.5
And this is what I get if I use option 2 ( or 1 ) which shows unfiltered log ( from all devices )
Jan 4 02:31:31 dnsmasq[9297]: blocked by blockinglist wpad.myasus is 10.0.0.2
Jan 4 02:31:33 dnsmasq[9297]: query[A] news.iadsdk.apple.com from 10.0.0.5
Jan 4 02:31:33 dnsmasq[9297]: blocked by blockinglist news.iadsdk.apple.com is 10.0.0.2
Jan 4 02:31:33 dnsmasq[9297]: query[A] iadsdk.apple.com from 10.0.0.5
Jan 4 02:31:33 dnsmasq[9297]: blocked by blockinglist iadsdk.apple.com is 10.0.0.2
Jan 4 02:31:33 dnsmasq[9297]: query[A] iadsdk.apple.com from 10.0.0.7
Jan 4 02:31:33 dnsmasq[9297]: blocked by blockinglist iadsdk.apple.com is 10.0.0.2
Jan 4 02:31:33 dnsmasq[9297]: query[A] www-cdn.icloud.com.akadns.net from 10.0.0.5
Jan 4 02:31:33 dnsmasq[9297]: forwarded www-cdn.icloud.com.akadns.net to 202.143.112.206
Jan 4 02:31:34 dnsmasq[9297]: reply www-cdn.icloud.com.akadns.net is <CNAME>
Jan 4 02:31:34 dnsmasq[9297]: reply www.icloud.com.edgekey.net is <CNAME>
Jan 4 02:31:34 dnsmasq[9297]: reply e4478.a.akamaiedge.net is 104.117.76.86
Jan 4 02:32:25 dnsmasq[9297]: query[A] e673.dsce9.akamaiedge.net from 10.0.0.5
Jan 4 02:32:25 dnsmasq[9297]: forwarded e673.dsce9.akamaiedge.net to 202.143.112.206
Basically I'm saying add an option to see unfiltered log ( like in my second example ) but originating just from my entered IP Address (10.0.0.5) and not from other devices on my network.
I see. That's doable. As an example, this is a query from 172.20.16 with the follow up lines associated with it.
I highlighted them in yellow. Is that what you want, but just related to the IP?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!