Custom firmware build for R7800 v. 1.0.2.40SF & 1.0.2.41SF

[Jeanmi]

nothing special in ISP
after reset it works again.

root@R7800:/$ ps | grep appflow
4736 root 1916 S /usr/bin/redis-server /etc/appflow/redis.conf
4937 root 3116 S /usr/sbin/sead --daemon --run-dir=/var/run/appflow --
5044 root 436 S /usr/sbin/sbnoded --daemon -p /var/run/appflow/sbnode
5085 root 688 S /usr/sbin/sbmacouid --daemon -p /var/run/appflow/sbma
5119 root 472 S jigglyp0f -d -f /var/run/appflow/p0f.fifo -p /var/run
5414 root 340 S /usr/sbin/flowman --redis-unixsocket=/var/run/appflow
5419 root 348 S /usr/sbin/cape --daemon -u /var/run/appflow/redis.soc
5448 root 4940 S /usr/sbin/p0f -s /var/run/appflow/p0f.sock -i br0 -f
19706 root 364 S grep appflow

I will follow

Jeanmi

 

[Voxel]

nothing special in ISP
after reset it works again.

root@R7800:/$ ps | grep appflow
4736 root 1916 S /usr/bin/redis-server /etc/appflow/redis.conf
4937 root 3116 S /usr/sbin/sead --daemon --run-dir=/var/run/appflow --
5044 root 436 S /usr/sbin/sbnoded --daemon -p /var/run/appflow/sbnode
5085 root 688 S /usr/sbin/sbmacouid --daemon -p /var/run/appflow/sbma
5119 root 472 S jigglyp0f -d -f /var/run/appflow/p0f.fifo -p /var/run
5414 root 340 S /usr/sbin/flowman --redis-unixsocket=/var/run/appflow
5419 root 348 S /usr/sbin/cape --daemon -u /var/run/appflow/redis.soc
5448 root 4940 S /usr/sbin/p0f -s /var/run/appflow/p0f.sock -i br0 -f
19706 root 364 S grep appflow

I will follow

Jeanmi

OK, let's hope that it's OK now. Something in overlay partition what spoiled your QoS.

Voxel.

 

[Sizzlechest]

I currently have an old Netgear WNDR3700 router running an old version of OpenWRT. There's one feature of OpenWRT that I really need: I can set up a port forwarding rule such that the port used can be DIFFERENT for a specified incoming IP range. For example, I have a remote administration tool that normal uses custom port 5000. Every router will allow you to port forward that. With OpenWRT, I can add ANOTHER rule such that IP ranges on the internet that go from XXX.XXX.XXX.0/24 get port forwarded to 443. This is useful since certain network environments block outgoing traffic through all ports EXCEPT 80 and 443. I wouldn't want to always use 443 since hackers may port scan 80 and 443 for vulnerable web servers and I'd rather them not let them get curious at what I have running at that port. I understand your firmware is based on the stock one. However, I don't mind connecting to the router through ssh and manually create a special configuration from the command line to accomplish this.

Do you know if a superseding port forwarding rule based on the originating IP address range can be done with your firmware?

EDIT: an iptables rule like:

-A zone_wan_forward -s XXX.YYY.0.0/17 -d 192.168.1.ZZZ/32 -p tcp -m tcp --dport 5000 -j ACCEPT

would work, but I don't know if I can manually add that with your firmware.

EDIT 2: I think I messed that up.

iptables -t nat -I OUTPUT --src XXX.YYY.0.0/17 --dst 192.168.1.ZZZ -p tcp --dport 443 -j REDIRECT --to-ports 5000

 

[Voxel]

EDIT: an iptables rule like:

-A zone_wan_forward -s XXX.YYY.0.0/17 -d 192.168.1.ZZZ/32 -p tcp -m tcp --dport 5000 -j ACCEPT

would work, but I don't know if I can manually add that with your firmware.

EDIT 2: I think I messed that up.

iptables -t nat -I OUTPUT --src XXX.YYY.0.0/17 --dst 192.168.1.ZZZ -p tcp --dport 443 -j REDIRECT --to-ports 5000

So you question could be rephrased as "Is it possible to set your own iptables rules", right?

Please have a look at https://www.snbforums.com/threads/c...v-1-0-2-42hf-1-0-2-42hf-hw.40688/#post-342246

it is for R9000, but practically the same is for R7800.

Voxel.

 

[Sizzlechest]

So you question could be rephrased as "Is it possible to set your own iptables rules", right?

Please have a look at https://www.snbforums.com/threads/c...v-1-0-2-42hf-1-0-2-42hf-hw.40688/#post-342246

it is for R9000, but practically the same is for R7800.

Voxel.

I think I understand.

1. Rename net-wall binary to net-wall-bin.
2. Put the script: https://github.com/SVoxel/R9000/blob/master/git_home/net-wall.git/net-wall in the same location as net-wall-bin and name it net-wall. It's a wrapper for net-wall-bin (the old net-wall.
3. Edit the IPTables rules in the script to do what I need.

I'm assuming I would still use the GUI for all the normal port forwarding setup and then add the additional iptables commands to do what I need. Is that correct?

 

[Voxel]

• Rename net-wall binary to net-wall-bin.

• Put the script: https://github.com/SVoxel/R9000/blob/master/git_home/net-wall.git/net-wall in the same location as net-wall-bin and name it net-wall. It's a wrapper for net-wall-bin (the old net-wall.

It is already done by me. There are net-wall script wrapper and net-wall-bin in my firmware. I.e. you have just edit net-wall script adding your rules.

I'm assuming I would still use the GUI for all the normal port forwarding setup and then add the additional iptables commands to do what I need. Is that correct?

Yes.

Voxel.

 

[zns311]

No offense.Can someone test the SMB download/upload speed for me?I got trapped in choosing the right FW, had to choose the official 1.0.1.30.

 

[Voxel]

No offense.Can someone test the SMB download/upload speed for me?I got trapped in choosing the right FW, had to choose the official 1.0.1.30.

No offence of course ;-) It is interesting for me too (not only my own benchmarks).

Until now I met only two responses

write speed:
https://www.snbforums.com/threads/c...r-r7800-v-1-0-2-39sf.41945/page-2#post-356514

read speed as I guess:
https://community.netgear.com/t5/Ni...eadyshare-not-enough-space/m-p/1428445#M72159

P.S.
Regarding use of old 1.0.1.30 I replied in other thread. Just IMO.

https://www.snbforums.com/threads/qos-on-latest-voxel-fw.41479/#post-361510

Voxel.

 

[kamoj]

OpenVPN client speed: 78 Mbps
I just want to express my happiness with this release!

I just upgraded from R7800-V1.0.2.38SF to R7800-V1.0.2.41SF

The dowload speed of the OpenVPN-client (aes-256 cbc) has increased from 43 Mbps to 73 Mbps (dslreports) / 78 Mbps (speedtest).

This is an incredible achievement!
Thank you very much - again - Voxel.

 

[ulaganath]

nothing special in ISP
after reset it works again.

root@R7800:/$ ps | grep appflow
4736 root 1916 S /usr/bin/redis-server /etc/appflow/redis.conf
4937 root 3116 S /usr/sbin/sead --daemon --run-dir=/var/run/appflow --
5044 root 436 S /usr/sbin/sbnoded --daemon -p /var/run/appflow/sbnode
5085 root 688 S /usr/sbin/sbmacouid --daemon -p /var/run/appflow/sbma
5119 root 472 S jigglyp0f -d -f /var/run/appflow/p0f.fifo -p /var/run
5414 root 340 S /usr/sbin/flowman --redis-unixsocket=/var/run/appflow
5419 root 348 S /usr/sbin/cape --daemon -u /var/run/appflow/redis.soc
5448 root 4940 S /usr/sbin/p0f -s /var/run/appflow/p0f.sock -i br0 -f
19706 root 364 S grep appflow

I will follow

Jeanmi

It usually works after every reboot But never works stable. it will fail anytime. The worst part is QOS crash is not a big deal. Since it is crashing all the pre-defined priority is matters. As any device can consume any amount of bandwidth. needed devices used to suffer.

I tried flashing multiple times . I even went back to 38F. No luck.

If it still fails will do the reset and try again.

 

[Voxel]

I've seen mention of the 4.X kernel. Do your builds use that or does anyone yet?

I use 3.4.103, the same as in the stock firmware. The reason if this is that I can use proprietary drivers, i.e. main advantage of stock firmware. I.e. almost the same approach as Merlin's firmware for ASUS routers.

Can you compare/contrast Voxel firmware vs Kong for a noob?

Sorry, no. I do not think I'll be objective . I use my own. People are free to use what they prefer.

Voxel

 

[Voxel]

OpenVPN client speed: 78 Mbps
I just want to express my happiness with this release!

I just upgraded from R7800-V1.0.2.38SF to R7800-V1.0.2.41SF

The dowload speed of the OpenVPN-client (aes-256 cbc) has increased from 43 Mbps to 73 Mbps (dslreports) / 78 Mbps (speedtest).

This is an incredible achievement!
Thank you very much - again - Voxel.

New version of my custom firmware build: 1.0.2.39SF.

Changes (vs 1.0.2.38SF):
. . .
3. Changes in OpenVPN client (now it is using core1).
. . .

Voxel.

 

[Voxel]

It usually works after every reboot But never works stable. it will fail anytime. The worst part is QOS crash is not a big deal. Since it is crashing all the pre-defined priority is matters. As any device can consume any amount of bandwidth. needed devices used to suffer.

I tried flashing multiple times . I even went back to 38F. No luck.

If it still fails will do the reset and try again.

Your problem is very specific. Previously you said that 38 is OK for you. Did you try previous version of QoS DB?

Voxel.

 

[Tommaso]

Your problem is very specific. Previously you said that 38 is OK for you. Did you try previous version of QoS DB?

Voxel.

Hi, Voxel and ulaganath

just to add my personal experience with this router.

Since i bought the r7800 router i started experiencing this issue. The QoS after a normal reboot of the router worked for a while, then it just stopped. It's not a matter of firmware version QoS version or factory reset. I've tested all the combinations so far and i understood that is something related to the attached device profiles; i try to explain it better; i noticed that if you change the profile of your wrongly recognized device inside the attached device page ( like a windows pc recognized as a general device) to the right one, the router starts acting like that, breaking the QoS process. If you try to restart it manually, like your suggestions, it fails at 40_qdiscman launch. Only after a reboot it starts it over correctly, untill i don't know the specific time yet.
I've found inside the crontab this script /usr/sbin/streamboost_status_monit that runs every 3 minutes (*/3 * * * * /usr/sbin/streamboost_status_monit). It checks the QoS status but i've not found the logs of this script yet. Probably those logs are the key to understand this failuer, because it doesn't make sense that it runs fine for a while and then it stops. It looks like something is "saturated" during the normal operation of the router.

Let me know if you have any idea.

Thank you for your effort and your really fast firmware.

Tommaso

 

[Voxel]

Since i bought the r7800 router i started experiencing this issue. The QoS after a normal reboot of the router worked for a while, then it just stopped. It's not a matter of firmware version QoS version or factory reset. I've tested all the combinations so far and i understood that is something related to the attached device profiles; i try to explain it better; i noticed that if you change the profile of your wrongly recognized device inside the attached device page ( like a windows pc recognized as a general device) to the right one, the router starts acting like that, breaking the QoS process. If you try to restart it manually, like your suggestions, it fails at 40_qdiscman launch. Only after a reboot it starts it over correctly, untill i don't know the specific time yet.

It is interesting. Maybe I do not have such devices which are wrongly recognized. It is just working for me.

I've found inside the crontab this script /usr/sbin/streamboost_status_monit that runs every 3 minutes (*/3 * * * * /usr/sbin/streamboost_status_monit). It checks the QoS status but i've not found the logs of this script yet. Probably those logs are the key to understand this failuer, because it doesn't make sense that it runs fine for a while and then it stops. It looks like something is "saturated" during the normal operation of the router.

This log is /var/streamboost_status. It is really changed every 3 min. From my router:

 [  UP  ] redis-server (pid 4876) is running.
 [  UP  ] policy-reader is running
 [  UP  ] Persistence Daemon (pid 5062) is running.
 [  UP  ] Settings have been loaded.
 [  UP  ] prio-reader is running
 [  UP  ] sead (pid 5142) is running.
 [  UP  ] sbnoded (pid 5163) is running.
 [  UP  ] nodedetectd (pid 5176) is running.
 [  UP  ] sbnamed (pid 5209) is running.
 [  UP  ] sbmacouid (pid 5224) is running.
 [  UP  ] Jigglyp0f (pid 5230) is running.
 [  UP  ] leash (pid 5234) is running.
 [  UP  ] qdiscman (pid 5517) is running.
 [  UP  ] flowmark (pid 5526) is running.
 [  UP  ] Overlord (pid 5531) is running.
 [  UP  ] Flowman (pid 5538) is running.
 [  UP  ] Class Arbiter/Policy Engine (pid 5543) is running.
 [  UP  ] drflocs (pid 5552) is running.
 [  UP  ] p0f (pid 5572) is running.
 [  UP  ] ozKer (pid 6225) is running.

Let me know if you have any idea.

Idea is just it is necessary to trace the problem.

I suggested (until now) two ways:

1. To save config of router, then do reset and restore config

https://www.snbforums.com/threads/c...00-v-1-0-2-40sf-1-0-2-41sf.42222/#post-360323
https://www.snbforums.com/threads/c...-0-2-40sf-1-0-2-41sf.42222/page-2#post-360340

No problem report yet after this.

2. To install previous version of QoS DB. Initially ulaganath confirmed that no problems with previous version. Unfortunately he did not reply did he tried this way.

https://www.snbforums.com/threads/c...r-r7800-v-1-0-2-31sf.39142/page-6#post-328537

Previous QoS DB is https://www.voxel-firmware.com/Downloads/Voxel/R7800-Voxel-firmware/QoS DB/QoS-20160607.zip

3. and probably third way, but not right now. Maybe there are some problems with redis server/client used by QoS. I already tried to upgrade them to most fresh version. But as occur problem with incompatibility. Stock FW is using version 2.6.13. I intend to upgrade now to 2.6.17. Should be compatible and some fatal bugs were corrected since 2.6.13:

https://raw.githubusercontent.com/antirez/redis/2.6/00-RELEASENOTES

Thank you for your effort and your really fast firmware.

You are welcome,
Voxel.

 

[Jeanmi]

OK, let's hope that it's OK now. Something in overlay partition what spoiled your QoS.

Voxel.

Hi Voxel

Qos is dead again

root@R7800:/tmp$ cat restart_process_list
Restart streamboost:2017-11-25T18:51:46Z
Restart streamboost:2017-11-25T19:07:57Z
Restart streamboost:2017-11-25T19:18:06Z
Restart streamboost:2017-11-25T19:27:15Z
Restart streamboost:2017-11-25T19:33:24Z
Restart streamboost:2017-11-25T19:56:39Z
Restart streamboost:2017-11-25T20:01:47Z
Restart streamboost:2017-11-25T20:06:54Z
Restart streamboost:2017-11-25T20:12:01Z
Restart streamboost:2017-11-25T20:17:08Z
Restart streamboost:2017-11-25T20:22:15Z
Restart streamboost:2017-11-25T20:38:27Z
Restart streamboost:2017-11-25T20:44:34Z
Restart streamboost:2017-11-25T20:50:43Z
Restart streamboost:2017-11-25T23:43:55Z
Restart streamboost:2017-11-26T00:01:07Z
Restart streamboost:2017-11-26T08:35:41Z
Restart streamboost:2017-11-26T08:55:55Z
Restart streamboost:2017-11-26T11:54:07Z
Restart streamboost:2017-11-26T11:55:13Z
Restart streamboost:2017-11-26T12:11:26Z
Restart streamboost:2017-11-26T12:13:33Z
Restart streamboost:2017-11-26T12:14:39Z
Restart streamboost:2017-11-26T12:15:45Z
Restart streamboost:2017-11-26T12:16:52Z
Restart streamboost:2017-11-26T12:21:00Z
Restart streamboost:2017-11-26T12:23:07Z
Restart streamboost:2017-11-26T12:30:15Z
Restart streamboost:2017-11-26T12:39:24Z
Restart streamboost:2017-11-26T12:48:33Z
Restart streamboost:2017-11-26T12:49:40Z
Restart streamboost:2017-11-26T12:51:47Z
Restart streamboost:2017-11-26T12:54:54Z
Restart streamboost:2017-11-26T13:15:07Z
Restart streamboost:2017-11-26T13:18:14Z
Restart streamboost:2017-11-26T13:34:27Z
Restart streamboost:2017-11-26T13:39:35Z
Restart streamboost:2017-11-26T15:46:28Z
Restart streamboost:2017-11-26T15:50:36Z
Restart streamboost:2017-11-26T16:20:53Z
Restart streamboost:2017-11-26T16:30:03Z
Restart streamboost:2017-11-26T16:54:17Z
Restart streamboost:2017-11-26T16:59:25Z
Restart streamboost:2017-11-26T17:32:43Z
Restart streamboost:2017-11-26T17:58:59Z
Restart streamboost:2017-11-26T19:05:29Z
Restart streamboost:2017-11-26T19:21:41Z
Restart streamboost:2017-11-27T13:04:45Z
Restart streamboost:2017-11-27T19:11:15Z
Restart streamboost:2017-11-27T19:26:27Z
Restart streamboost:2017-11-27T19:54:44Z
Restart streamboost:2017-11-28T18:10:38Z
Restart streamboost:2017-11-28T18:39:55Z
Restart streamboost:2017-11-28T18:50:04Z
Restart streamboost:2017-11-28T19:00:14Z
Restart streamboost:2017-11-28T19:54:41Z
Restart streamboost:2017-11-29T07:38:28Z
Restart streamboost:2017-11-29T12:06:14Z
Restart streamboost:2017-11-29T12:13:22Z
Restart streamboost:2017-11-29T12:43:38Z
Restart streamboost:2017-11-29T12:52:47Z
Restart streamboost:2017-11-29T12:56:55Z
Restart streamboost:2017-11-29T13:14:07Z
Restart streamboost:2017-11-29T13:18:15Z
Restart streamboost:2017-11-29T13:29:24Z
Restart streamboost:2017-11-29T13:32:32Z
Restart streamboost:2017-11-29T13:40:40Z
Restart streamboost:2017-11-29T13:53:51Z
Restart streamboost:2017-11-29T14:01:00Z
Restart streamboost:2017-11-29T14:11:09Z
Restart streamboost:2017-11-29T14:32:23Z
Restart streamboost:2017-11-29T14:44:32Z
Restart streamboost:2017-11-29T14:51:41Z
Restart streamboost:2017-11-29T15:18:57Z
Restart streamboost:2017-11-29T15:34:08Z
Restart streamboost:2017-11-29T15:42:17Z
Restart streamboost:2017-11-29T16:12:34Z
Restart streamboost:2017-11-29T16:20:44Z
Restart streamboost:2017-11-29T16:42:58Z
Restart streamboost:2017-11-29T16:47:06Z
Restart streamboost:2017-11-29T16:56:15Z
Restart streamboost:2017-11-29T19:53:32Z
Restart streamboost:2017-11-29T20:03:42Z
Restart streamboost:2017-11-30T09:08:01Z
Restart streamboost:2017-11-30T18:54:53Z
Restart streamboost:2017-11-30T19:12:05Z
Restart streamboost:2017-11-30T19:18:12Z
Restart streamboost:2017-11-30T19:36:25Z
Restart streamboost:2017-11-30T19:40:32Z
Restart streamboost:2017-11-30T20:49:03Z
Restart streamboost:2017-11-30T20:50:08Z
Restart streamboost:2017-11-30T20:56:16Z
Restart streamboost:2017-12-01T13:55:11Z
Restart streamboost:2017-12-01T13:56:19Z
Restart streamboost:2017-12-01T13:57:30Z

after Reboot

root@R7800:/$ ps | grep appflow
4938 root 1828 S /usr/bin/redis-server /etc/appflow/redis.conf
5012 root 3108 S /usr/sbin/sead --daemon --run-dir=/var/run/appflow --
5017 root 420 S /usr/sbin/sbnoded --daemon -p /var/run/appflow/sbnode
5067 root 684 S /usr/sbin/sbmacouid --daemon -p /var/run/appflow/sbma
5124 root 472 S jigglyp0f -d -f /var/run/appflow/p0f.fifo -p /var/run
5331 root 328 S /usr/sbin/flowman --redis-unixsocket=/var/run/appflow
5336 root 340 S /usr/sbin/cape --daemon -u /var/run/appflow/redis.soc
5365 root 4932 S /usr/sbin/p0f -s /var/run/appflow/p0f.sock -i br0 -f
7491 root 364 S grep appflow


Jeanmi

 

[Tommaso]

This is mine since this morning.

root@R7800:/$ cat /tmp/restart_process_list
Restart streamboost:2017-12-04T11:23:53Z
Restart streamboost:2017-12-04T11:24:58Z
Restart streamboost:2017-12-04T11:26:47Z
Restart streamboost:2017-12-04T11:27:54Z
Restart streamboost:2017-12-04T11:29:01Z
Restart streamboost:2017-12-04T11:30:33Z
Restart streamboost:2017-12-04T11:31:40Z
Restart streamboost:2017-12-04T11:32:47Z
Restart streamboost:2017-12-04T11:33:54Z
Restart streamboost:2017-12-04T11:35:00Z
Restart streamboost:2017-12-04T11:36:06Z
Restart streamboost:2017-12-04T11:37:13Z
Restart streamboost:2017-12-04T11:38:19Z
Restart streamboost:2017-12-04T11:39:24Z
Restart streamboost:2017-12-04T15:11:50Z
Restart streamboost:2017-12-04T16:04:14Z
Restart streamboost:2017-12-04T20:09:51Z
Restart streamboost:2017-12-04T21:40:31Z

During the week i'll try to factory reset, import the backup and whatch on it.
Now it is still running even after those restarts.

Tommaso

 

[Voxel]

Jeanmi, Tommaso please see your P.M.

Voxel.

 

[e38BimmerFN]

After loading v41SF today, I'm getting the following on a 200/10. I did a factory reset on the router after loading v41SF to be sure all was clean and set up from scratch:
Latest test result (12:28 Dec 05, 2017)
DOWNLOAD UPLOAD
174.82Mbps 10.76Mbps

Last nite I rolled back from v41SF to v30SF and got better speed results:


Is the onboard speed test working correctly?

 

[Prodeje79]

I am excited to install Voxel Firmware for the first time! Thank you for your hard work! Is it OK to use 1.0.2.41SF or do you recommend using an older version for now?