[Solved]Tremulous 1.2 No or bad challenge for your address?[Solved]!!!

[ArrowBlade]

When I try to join a server in tremulous 1.2 it says "No or bad challenge for your address" and a never ending timer... I have been trying to fix it but have had no luck so I was hoping you guys could help me fix it... Thanks in advance.

[Superpie]

check your firewalls, including those that are integrated into your router/modem - temporarily disabling them all and seeing if the problem is solved is a good start

[ArrowBlade]

I tried that and it didn't work...

[ArrowBlade]

I'm not sure how much this helps but I downloaded the game on my sisters laptop and it works fine...

[ArrowBlade]

I don't understand why this works but I got 1.2 working.

I did /bind x reconnect then I have to press it 2-4 times when connecting to a server... X can be any key, I used F12 as my key...

[D@ve]

Sorry for answering in this old topic but I exactly have the same problem.
None of the two solutions described here did help.
When I /reconnect, it still says "No or bad challenge for your address" and I can reconnect many times like this without any change...
I can't connect to any server..

That's not an installation problem as it still does not work using the windows version trough wine...
And 1.1 works like a charm... So what's wrong with 1.2?

[arf]

EDIT: wrong year
Sorry

[KillerWhale]

Well, that was a convenient accidental necro, as I've had this very same error occur.

I've contacted my ISP to see if I can get firewalling disabled on my line entirely and just go back to using my router/modem's firewall.
I'm not at all knowledgeable about firewalls, so here's my configuration's ruleset:

Code: [Select]

Inbound:
permit tcp any host mail.sonic.net eq 25
deny tcp any any eq 25
deny tcp any eq 25 any
permit ip any any
Outbound:
permit ip any any
My computer is in DMZ+ mode on my router's firewall, so that's not the issue.
Any clue if that ruleset would block Trem, or is there another issue?

[Qrntz]

Any clue if that ruleset would block Trem

AFAIK, not quite. It denies any e-mail server/client connections except from host mail.sonic.net and permits everything outbound.
That shouldn't cause any problems if you aren't running a spam gateway.
I don't really have an idea about what DMZ+ is (apart from regular DMZ), but if it's DMZ without NAT, that shouldn't cause tremproblems as well.
What about software firewalls?

[KillerWhale]

No, I haven't any software firewalls active at the moment.
It's only started happening since I switched to Sonic.net, which is a shame, because they offer great service.

Going to post a condump of client startup -> attempting to join a server for good measure, in case anyone wants to take the time to read it.

Code: [Select]

Sound memory manager started
Loading vm file vm/ui.qvm...
File "vm/ui.qvm" found in "/home/whales/.tremulous/gpp/vms-gppr2203.pk3"
total 0, hsize 1021, zero 1021, min 0, max 0
total 4074, hsize 1021, zero 39, min 0, max 13
Loaded 44 of 44 emoticons (MAX_EMOTICONS is 64)
^3WARNING: Menu file ui/credit.menu not found
^3WARNING: Menu file ui/addfilter.menu not found
UI menu file 'ui/menus.txt' loaded in 364 msec
UI menu file 'ui/ingame.txt' loaded in 27 msec
UI menu file 'ui/tremulous.txt' loaded in 17 msec
UI help file 'ui/help.txt' loaded in 1 msec (16 infopanes)
File "ui/" found in "/home/whales/.tremulous/gpp/z_hudoption.pk3"
--- Common Initialization Complete ---
IP: 127.0.0.1
IP: 208.106.49.21
IP6: ::1
IP6: fe80::4261:86ff:fefa:bbc7%eth0
Opening IP6 socket: [::]:30720
Opening IP socket: 0.0.0.0:30720
69.175.114.216:30720 resolved to 69.175.114.216:30720
No or bad challenge for your address.
I cut out things that I knew were unimportant, but I still left some unimportant stuff intact.

[arf]

I'm guessing it's some DNS problem, I was able to connect by adding this to /etc/hosts
69.175.114.216 master.tremulous.net

[KillerWhale]

Thanks, I'll try that when I get to my Linux machine.

Would flushing DNS possibly fix it?

[arf]

It seems like the problem was caused by slow DNS lookups?
And the slow DNS lookups can be fixed in /etc/resolv.conf
In my case, the first nameserver needed to be the modem (not the router)

(IPs may vary)
Incorrect:

Code: [Select]

domain Belkin
search Belkin
nameserver 192.168.30.1
nameserver 192.168.2.1

Correct:

Code: [Select]

domain Belkin
search Belkin
nameserver 192.168.2.1
nameserver 192.168.30.1

Hope this helps

[baybal]

i bet, your isp sniffs your dns requests