• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Gamma FAQ and TeAm Gamma Proxy

Viztech

Platinum Member
With the recent interest in the Gamma project, I thought that I would take a look at the FAQ to be sure that things are up-to-date. A couple of things need a little attention. Thought we could discuss them in the forum before I Email JHutch to make the changes on the TeAm website

First, Joe O has done considerable work in updating the FAQ, and certainly needs recognition for that effort.

Second, I believe that it was The Magic Man that wrote the batch files for sneakernetting Gamma, and needs recognition for such.

The TeAm proxy address at proxy.teamanandtech.com port 4556 seems to be invalid. My DNS server resolves this to 65.33.87.232. Anyone who is having immediate trouble with flushing should try keys.dcypher.net port 4356 until we resolve this issue. Also, past experience has shown difficulty in connecting to this address for SOME users. I would like to see a reliable alternate proxy posted. I can fire mine back up, which worked well for most users in the past who had difficulty flushing direct to dcypher.

The port 80 firewall proxy of port80.dcypher.net does not work for me, on port 80, 4356 or 4556. Is anybody using it succesfully? DNS resolves to 24.141.163.62.

Thanx for your help.

viz



 
At the moment, we aren't running a Dcypher proxy on any TA proxy. Last time we tried, we found out the hard way that the Dcypher proxy hates the Dnet proxy, which is why we had problems a few months ago with Mika's running dry.🙁 Once Dcypher makes a pproxy that can run properly, we'll reconsider installing it on at least Mika's.
 
Oh, and as for any changes you need done to the FAQs(or adding any new FAQs), send them to JHutch, so he can make the nessisary changes and upload them.🙂
 
Thanx for that info ViRGE, I edited my post accordingly.

To clear the record, I myself ran both the Dnet and DCypher proxies simultaneously on my NT4 server without trouble. I was NOT running stats or a webserver and did not have a ton of traffic like Mika does. Networking with the DCypher clients and proxies is lacking, but many of us have seen issues when running conflicting software on machines which obviously we saw in Mika's case.

viz
 
Can the DCypher proxy be run as a service? If it can, I would be willing to try and run it simutaneously with my Dnet pProxy.

Jay
 
I don't believe so Jay, but Servany from the old NT Resource kit may work. If we find the need to set up a team proxy for Gamma, we should keep it off a machine running the Dnet proxy.

viz
 
Well, I have a few machines here at home, but I am running out of ports to forward with my router. 🙁

And only one machine runs NT, the rest are Win9X. 🙁

Jay
 
Standard dcypher port is indeed 4356. There WAS a software in dcypher downloads (client or pproxy, I cant remember) for some time that had a goofy port setting in the ini file, and that prevented me from flushing for a day or two. Maybe thats where this odd 4556 comes from ?
 
Is there a setting for the proxy to tell it to try to connect only when a dial-up connection is detected? Kind of like "lurkonly"?
 
Doh!

We discussed that FAQ a couple weeks ago and I made changes to the FAQ to reflect the fact that we don't run a DCypher proxy... However, I missed the very first reference to it in the FAQ... 😱

I'll make the change ASAP. Sorry about missing that!

JHutch
 
I have been running three proxies on one box without a hiccup for months now... 2 dnet (one that goes to the TA proxy, another that doesn't) and one GF. I would say that the problems you were having on mika's box are due to one or more of the following:
1) heavy heavy volume
2) some sort of stats software
3) webserving
4) anything else, but it is NOT that the proxies hate eachother.

btw, ViRGE, nice to think that it is dcyphers proxy that has issues and not d.nets
 
Actually PF, I talked to Charrison about it a while ago, and he admited there was a problem in the proxy that could cause that.🙁
 
Back
Top