What's new

Kamoj Kamoj Add-on Beta testing

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

o_O I agree!
I thanked him for his report.

What are you putting into it? So why you think otherwise?
Iäm sorry my English is not understandable.
So enlighten me, and please try to excuse me, I'm not English native at all :oops:.

I'm a/was poor farmer son and not even had the money to buy books for my higher studies,
or going abroad learning languages.
But Voxel convinced me I should publish my "thing".
It's 2 years ago, and it became my hobby.
I guess it was wrong of me. I should have stayed back.
Where I come from there is a saying, "trees are not allowed to reach the sky".
Sutor, ne ultra crepidam.

Sorry to "everyone" feeling offended.
I'm of course only happy if someone use the useless add-on, think nothing else.
20000 Voxel users, 40 add-on users.
Not much to discuss, is it?

In all, I beg your pardon, despondently yours.
kamoj
Kamoj,

I have always found it easy to understand what you are saying. However, with many members of different backgrounds, it is often difficult to convey the intended meaning when writing in forums such as this... especially when we are not all native English language speakers. Sometimes the meaning does not come across as intended. So to be clear, I sincerely appreciate you, the Add-on, and your willingness to put up with my (sometimes) ineptitude.

I grew up before the age of computers (started school with an abacus and graduated using a slide rule), so I am a bit out of my comfort zone with much of what happens here. However your add-on has made it easy for me to add the functionality I need. And the members of this forum have made me feel welcome and helped me learn new skills that are fun and useful (whenever I can find a few moments to dig into things). Thank you everyone!

Netgear owes you and Voxel a debt of gratitude, as I would likely be looking at other equipment if it wasn't for you both.

Best wishes,
BL
 
@kamoj and community,

Is there any way for WiFi supervision to determine the TxPkts / RxPkts numbers that are highlighted in yellow in the screen snippet below (from the stock Show Statistics page /RST_statistic.htm) became "stuck" ?

View attachment 32132

My 5G band on my R7800 in AP mode has dropped after almost 3 days of uptime, and as I've mentioned previously those numbers that are highlighted remain stuck at those values and do not increment as they normally would.

The output from the commands used to check the current status indicate that the radios are on, but the 5G band is actually not showing up on scans from WiFi clients, such as a smartphone running a scanner app.

Code:
root@R7800:/usr/bin$ dni_wlan radio 11a -s
ON
root@R7800:/usr/bin$ dni_wlan radio 11g -s
ON
root@R7800:/usr/bin$ wlan radio 11a --status
ON
root@R7800:/usr/bin$ wlan radio 11g --status
ON
root@R7800:/usr/bin$ iwconfig ath0
ath0      IEEE 802.11ac  ESSID:"5GBAND"
          Mode:Master  Frequency:5.2 GHz  Access Point: B0:B9:8A:6F:10:CF
          Bit Rate:1.7333 Gb/s   Tx-Power:29 dBm
          RTS thr:off   Fragment thr:off
          Encryption key:F328-2D93-E811-9EA6-C18D-0A0F-DCB1-EF20 [2]   Security mode:open
          Power Management:off
          Link Quality=0/94  Signal level=-95 dBm  Noise level=-95 dBm
          Rx invalid nwid:47748  Rx invalid crypt:6  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@R7800:/usr/bin$ iwconfig ath01
ath01     No such device

root@R7800:/usr/bin$ iwconfig ath1
ath1      IEEE 802.11ng  ESSID:"24GBAND"
          Mode:Master  Frequency:2.452 GHz  Access Point: B0:B9:8A:6F:10:CD
          Bit Rate:378.4 Mb/s   Tx-Power:29 dBm
          RTS thr:off   Fragment thr:off
          Encryption key:89DB-2C81-C31E-5D47-CEC3-E400-AEEB-EEFF [2]   Security mode:open
          Power Management:off
          Link Quality=0/94  Signal level=-95 dBm  Noise level=-95 dBm
          Rx invalid nwid:619474  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@R7800:/usr/bin$ iwconfig ath11
ath11     No such device

There is no ath01 and no ath11 device because I don't enable guest WiFi.

I have the Supervise WiFi function enabled and there is no new log entries added to /var/log/kamoj_addons.log since all the radios appear to be on and working, although that is not true.

Any ideas for detecting this "stuck" TxPkts / RxPkts condition on both 2.4G and 5G bands? Thanks.
I've added check of Tx/Rx in the upcoming version. Doing tests now. Thank you for testing and reporting back!
 
@kamoj :eek:o_O

How can you think so poorly of yourself!
You ARE one of the pillars of this community, and your addon is far from useless. I think it makes things a lot easier for many users that are not power users. You give them an easy and well designed way to fine tune their routers.
I know your work, opinion and knowledge is highly respected and praised here, and you are an asset to this forum.

@Voxel was absolutely right in thinking you should publish your addon.

I have great respect for farmers that are doing a very hard, respectful and essential work (feeding us!).

You managed to get a good education to have high skills in computer science, programming and networking, and be fluent in English. And I know you caught up in traveling the world ;)

Don’t beat yourself up my friend. If anyone here think your work is useless or that your education is poor, they are just displaying their stupidity and they don’t belong here, where you certainly do!
Thank you for the comforting words, and I know you mean it.
You have such a bog good heart!
 
Absolutely agree with @HELLO_wORLD. It is pitty that there is not button "dislike": I'd push it immediately on the post of @kamoj...

English of @kamoj is much better vs e.g. my. Excellent. And time-to-time he starts this pessimistic mood... All this is because of lock down... Damn COVID...

@kamoj : First. Your add-on increases the amount of users of Voxel firmware. For example after your important work amount of R9000 was significantly increased. Really. Second. A bit overcomplicated procedure to get your add-on IMO. Do you really think that the only people registered in this forum are using your add-on? They are just sharing downloaded add-on version. If I would think that only people who pushed [Like] are using my firmware, I would get 100 users. Maybe 200. Think of population e.g. China, 1.4 billion. With their GW firewall. The one gets your add-on, thousands are re-using. They just are not able to register here.

Go on @kamoj. We all need your job. Including me because exactly your add-on increases the amount of my users. Think positive.

P.S. Now I am not "Very Senior Member" but "Part of the Furniture"... What I found yesterday. So my posts are extremely serious :cool: . Do not ignore this.

Re: English. Funny, I am furniture... Like a chair. Wishing you to become the sofa soon. Show must go on. People need you.

Voxel.
Yes, I would like the "dislike" button back! Actually there was one a short time after Higgins changed the forum software!
I pressed it once after someone wrote something offending about Voxel! After that I suppose Higgins removed the button again...

Well, I've no idea about what's going on in China, or if they would use the add-on. But it's good thinking Voxel.

"Part of the Furniture"... I prefer "Very Senior Member". Unfortunately todays youth have no respect for the "seniors" - at least where I live.
I can be the sofa, but we need a table as well, and a fridge full of beers... :p

Thank you for cheering me up in these Corona times.
 
Kamoj,

I have always found it easy to understand what you are saying. However, with many members of different backgrounds, it is often difficult to convey the intended meaning when writing in forums such as this... especially when we are not all native English language speakers. Sometimes the meaning does not come across as intended. So to be clear, I sincerely appreciate you, the Add-on, and your willingness to put up with my (sometimes) ineptitude.

I grew up before the age of computers (started school with an abacus and graduated using a slide rule), so I am a bit out of my comfort zone with much of what happens here. However your add-on has made it easy for me to add the functionality I need. And the members of this forum have made me feel welcome and helped me learn new skills that are fun and useful (whenever I can find a few moments to dig into things). Thank you everyone!

Netgear owes you and Voxel a debt of gratitude, as I would likely be looking at other equipment if it wasn't for you both.

Best wishes,
BL
Ok, thank you.
What is important here is that we help each other.
I feel better now after reading your post as well!:)
 
I've added check of Tx/Rx in the upcoming version. Doing tests now. Thank you for testing and reporting back!
That is awesome @kamoj.

Some observations from trying to get my 5G band to work again without rebooting...

Initially I tried the wlan toggle command-line. It spat out 1 line as shown below, but did not fix the issue:

Code:
root@R7800:/usr/bin$ wlan toggle
/sbin/wlan: eval: 1: wpsled: Permission denied

Next, I tried the wlan up command-line and that did not fix the issue, with output as shown below:

Code:
root@R7800:/usr/bin$ wlan up
Interface doesn't accept private ioctl...
setHwaddr (8BE4): Device or resource busy
/usr/sbin/wlanconfig: ioctl: Invalid argument
enable_qcawifi(wifi1): Failed to set up ap vif
Interface doesn't accept private ioctl...
setHwaddr (8BE4): Device or resource busy
/usr/sbin/wlanconfig: ioctl: Invalid argument
enable_qcawifi(wifi0): Failed to set up ap vif
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
config_generic failed in handle_vendorie(): Operation not permitted
config_generic failed in handle_vendorie(): Operation not permitted

Next, I tried the wlan down command-line and that did not fix the issue, with output as shown below:

Code:
root@R7800:/usr/bin$ wlan down
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
/sbin/wlan: eval: 1: wpsled: Permission denied

Finally, I tried the wlan up command-line again and that worked, with output as shown below:

Code:
root@R7800:/usr/bin$ wlan up
Invalid command : dni_vlan_pri
Error for wireless request "Set Fragmentation Threshold" (8B24) :
    SET failed on device ath1 ; Invalid argument.
Interface doesn't accept private ioctl...
stafwd (8BE0): Invalid argument
Interface doesn't accept private ioctl...
vhtmubfee (8BE0): Invalid argument
Configuration file: /var/run/hostapd-ath1.conf
ath1: Could not connect to kernel driver
Using interface ath1 with hwaddr b0:b9:8a:6f:10:cd and ssid "24GBAND"
ath1: interface state UNINITIALIZED->ENABLED
ath1: AP-ENABLED
Invalid command : dni_vlan_pri
Error for wireless request "Set Fragmentation Threshold" (8B24) :
    SET failed on device ath0 ; Invalid argument.
Interface doesn't accept private ioctl...
stafwd (8BE0): Invalid argument
Interface doesn't accept private ioctl...
vhtmubfee (8BE0): Invalid argument
Configuration file: /var/run/hostapd-ath0.conf
ath0: Could not connect to kernel driver
Using interface ath0 with hwaddr b0:b9:8a:6f:10:cf and ssid "5GBAND"
ath0: interface state UNINITIALIZED->ENABLED
ath0: AP-ENABLED
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.

----------------------------------------
Vendor IE info Ioctl CMD id     : 29
ID                              : dd
Len (OUI+ Pcapdata) in Bytes    :  b
OUI                             : 00146c
Private capibility_data         : 0801020110000000
Frame Include Mask              : 18
----------------------------------------

----------------------------------------
Vendor IE info Ioctl CMD id     : 29
ID                              : dd
Len (OUI+ Pcapdata) in Bytes    :  b
OUI                             : 00146c
Private capibility_data         : 0801020110000000
Frame Include Mask              : 18
----------------------------------------

I hope the information will provide additional insight and be useful to your work.
 
Well, I've no idea about what's going on in China
Me too but I had to deal many years ago with about hundred of potential employees from China (remotely, they had to pass my exams) and I really know re: sharing and re-using.

but we need a table as well, and a fridge full of beers... :p
Yeah.

Stay safe. The taste after COVID might be changed... I started to prefer weissbier instead of my usual lager...

Voxel.
 
That is awesome @kamoj.

Some observations from trying to get my 5G band to work again without rebooting...

Initially I tried the wlan toggle command-line. It spat out 1 line as shown below, but did not fix the issue:

Code:
root@R7800:/usr/bin$ wlan toggle
/sbin/wlan: eval: 1: wpsled: Permission denied

Next, I tried the wlan up command-line and that did not fix the issue, with output as shown below:

Code:
root@R7800:/usr/bin$ wlan up
Interface doesn't accept private ioctl...
setHwaddr (8BE4): Device or resource busy
/usr/sbin/wlanconfig: ioctl: Invalid argument
enable_qcawifi(wifi1): Failed to set up ap vif
Interface doesn't accept private ioctl...
setHwaddr (8BE4): Device or resource busy
/usr/sbin/wlanconfig: ioctl: Invalid argument
enable_qcawifi(wifi0): Failed to set up ap vif
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
config_generic failed in handle_vendorie(): Operation not permitted
config_generic failed in handle_vendorie(): Operation not permitted

Next, I tried the wlan down command-line and that did not fix the issue, with output as shown below:

Code:
root@R7800:/usr/bin$ wlan down
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
/sbin/wlan: eval: 1: wpsled: Permission denied

Finally, I tried the wlan up command-line again and that worked, with output as shown below:

Code:
root@R7800:/usr/bin$ wlan up
Invalid command : dni_vlan_pri
Error for wireless request "Set Fragmentation Threshold" (8B24) :
    SET failed on device ath1 ; Invalid argument.
Interface doesn't accept private ioctl...
stafwd (8BE0): Invalid argument
Interface doesn't accept private ioctl...
vhtmubfee (8BE0): Invalid argument
Configuration file: /var/run/hostapd-ath1.conf
ath1: Could not connect to kernel driver
Using interface ath1 with hwaddr b0:b9:8a:6f:10:cd and ssid "24GBAND"
ath1: interface state UNINITIALIZED->ENABLED
ath1: AP-ENABLED
Invalid command : dni_vlan_pri
Error for wireless request "Set Fragmentation Threshold" (8B24) :
    SET failed on device ath0 ; Invalid argument.
Interface doesn't accept private ioctl...
stafwd (8BE0): Invalid argument
Interface doesn't accept private ioctl...
vhtmubfee (8BE0): Invalid argument
Configuration file: /var/run/hostapd-ath0.conf
ath0: Could not connect to kernel driver
Using interface ath0 with hwaddr b0:b9:8a:6f:10:cf and ssid "5GBAND"
ath0: interface state UNINITIALIZED->ENABLED
ath0: AP-ENABLED
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.

----------------------------------------
Vendor IE info Ioctl CMD id     : 29
ID                              : dd
Len (OUI+ Pcapdata) in Bytes    :  b
OUI                             : 00146c
Private capibility_data         : 0801020110000000
Frame Include Mask              : 18
----------------------------------------

----------------------------------------
Vendor IE info Ioctl CMD id     : 29
ID                              : dd
Len (OUI+ Pcapdata) in Bytes    :  b
OUI                             : 00146c
Private capibility_data         : 0801020110000000
Frame Include Mask              : 18
----------------------------------------

I hope the information will provide additional insight and be useful to your work.
Yes thank you, that is how the test-code is working now.
So let's hope it will work for you as well.
Still we should eventually try to understand the root cause of your problem.
 
Yes thank you, that is how the test-code is working now.
So let's hope it will work for you as well.
Still we should eventually try to understand the root cause of your problem.
Agreed. It would be great to be able to nail down the root cause for the wlan drops in my case. Thanks.
 
...
I guess it was wrong of me. I should have stayed back.
...
kamoj

Just registered
- to disagree that "it was wrong" to bring your excellent work to public,
- to thank and appreciate you (kamoj), voxel, hello_world and all the others, who do much work to enhance (sic!) the sold and forgotten(?) netgear-hardware,
- and not at least because of the post "To unregistered readers of SNB forums". (yes, i am/was one of thes silent readers)

I also would like to try the kamoj-addon, but i´m not able to take part in the development like requested (not enough time, not enough knowledge, to much fear to brick the router).
But i have a question: Can you think about the option to publish/create a "stable=frozen" version of one without/only few bugs. The "open" v5-addon is rather old...

Keep up your excellent work and your efforts - perhaps/hopefully a few others register to honor you and the other masterminds here!
With deep respect
old_kraut
 
Just registered
- to disagree that "it was wrong" to bring your excellent work to public,
- to thank and appreciate you (kamoj), voxel, hello_world and all the others, who do much work to enhance (sic!) the sold and forgotten(?) netgear-hardware,
- and not at least because of the post "To unregistered readers of SNB forums". (yes, i am/was one of thes silent readers)

I also would like to try the kamoj-addon, but i´m not able to take part in the development like requested (not enough time, not enough knowledge, to much fear to brick the router).
But i have a question: Can you think about the option to publish/create a "stable=frozen" version of one without/only few bugs. The "open" v5-addon is rather old...

Keep up your excellent work and your efforts - perhaps/hopefully a few others register to honor you and the other masterminds here!
With deep respect
old_kraut
Very well written @old_kraut !

One reason for keeping it in Beta stage is that It's difficult to not add something new for each release... :oops:
And then I don't consider it stable until after some time has elapsed without complaints.
For the moment I want to finish the WiFi-supervision I already started.
Current b24 had an issue with enabling also Guest network that should be off:eek:.
All is ok in the unreleased b25, since I also wanted to see if there was any way to fix the @n1llam1 issue:
https://www.snbforums.com/threads/kamoj-add-on-beta-testing.67375/post-674079

So thank you very much for registering and your good suggestion.:)
Maybe I have time and power to make an "official" release after the Easter period.
 
...
Maybe I have time and power to make an "official" release after the Easter period.

Thank you for your answer and your fast reply!
Please do not feel pressurized - the right name for my fantasy was "snapshot" (i lost the word in the post above - sorry).
If it´s called "snapshot", nobody should expect "rocksolid, free of bugs, full of all features, everything possible included..." - you know what i mean...
It´s YOUR decision, when and if there will be a snapshot or an official release. And if not - sh*t happens... ;) Nobody is in the position to claim something from you or from someone else of the masterminds here!

Respectfully
old_kraut
 
Last edited:
Thank you for your answer and your fast reply!
Please do not feel pressurized - the right name for my fantasy was "snapshot" (i lost the word in the post above - sorry).
If it´s called "snapshot", nobody should expect "rocksolid, free of bugs, full of all features, everything possible included..." - you know what i mean...
It´s YOUR decision, when and if there will be a snapshot or an official release. And if not - sh*t happens... ;) Nobody is in the position to claim something from you or from someone else of the masterminds here!

Respectfully
old_kraut
@old_kraut, my experience with the Kamoj Add-on V5.4b24 has been solid. If you would like to give that "snapshot" a try, please send a request message to @kamoj directly.

Like you I previously found only the 5.0 version "generally available". I took the leap and registered a little over a month ago so that I could reach out to @kamoj to send in my request to try out the 5.4 beta and be able to share my experiences with it. @kamoj's add-on led to me trying out things such as @Voxel's build of Entware and @HELLO_wORLD's Aegis. I trust that you will also find them to be as useful tools as they have been for me.
 
@kamoj Is there new link to beta folder, because the old one doesn't work for me?
See below:
Changes in kamoj-addon beta version 5.4b23
--------------------------------------------------
- System Information: "AP stats" show: Added more information. (@n1llam1)
- Router Information: Use the value of "nvram get kamoj_restart_ping_timeout". ($blueliner)
- Include Voxel Snapshot when evaluating latest release color
- Added Netgear cronjobs to "System Information: cron jobs: show" (@sppmaster)
- Removed streamboost cron job if streamboost disabled (@sppmaster, @NetBytes)
- OpenVPN Client: Added VyprVPN (@schneidewind)
(But have no account, so I can't test it)
- entware_install.sh : Fixed to work with R9000 again. Please PM me if still any problem.
- Split kamoj.sh into 2 different programs to speed up processing.
No need for users to care, but please report unexpected behaviors.

This release and on will be hosted at another place.
If you want to continue doing beta testing, you need to contact me kamoj,
here at the forum again.
You can use/bump your original PM and just tell me you want to continue.
I expect to reply to you within 24 hours.
 
Hello All, got a reboot after few days of Voxel FW:V1.0.2.83SF (Voxel). Kamoj Add-on:5.4b24. i'm coming from a clean installation. anyone get some issue?
 
Hello All, got a reboot after few days of Voxel FW:V1.0.2.83SF (Voxel). Kamoj Add-on:5.4b24. i'm coming from a clean installation. anyone get some issue?
2 devices in my case with the same firmware and add-on as you, with the following continuous uptimes... stable so far.
R7800 AP - System Uptime 3 days 21 hours 32 min 51 seconds
R7800 router - System Uptime 7 days 0 hours 6 min 52 seconds
 
I also thank Voxel and Kamoj for great work. I also sent a private message to Kamoj.
Ladies and gentlemen, our R7800 is very stable with the Voxel firmware and the Kamoj add-on. Netgear should send the boys the equipment for free.

I have a question. Is it possible to add another ddns client in the software. As of March, Netgear with No-IP requires a renewal every 30 days. Netgear was sharply scared.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top