Server Help :: View topic - Freqs arent private

Server Help

ASSS Questions - Freqs arent private

TeHsU - Sun Oct 31, 2004 2:09 pm
Post subject: Freqs arent private

My Frequencys arent private, they show up even when i put it in the confs to be private.. any ideas?

Dr Brain - Sun Oct 31, 2004 2:19 pm
Post subject:

Using contenc or nullenc?

Do you have the security module loaded?

TeHsU - Sun Oct 31, 2004 3:01 pm
Post subject:

nullenc, since contenc doesnt load and no i dont, security module wont load either, its a custom compile, but security.so is in the bin dir

Unrecoverable error (5): Error in loading module 'security:security'

Mine GO BOOM - Sun Oct 31, 2004 5:20 pm
Post subject:

Check your group settings. Mods have the seeprivfreq ability set to them, and if you put yourself in the mod group, you'll see private freqs. If you have this setup in the public group, everyone will see private freqs.

TeHsU - Sun Oct 31, 2004 5:26 pm
Post subject:

yeah, the default has just the default theres no seeprivfreq in it

Dr Brain - Sun Oct 31, 2004 8:38 pm
Post subject:

Load the security module and things should work.

You'll also notice that the doors wont sync between clients while it's unloaded.

TeHsU - Sun Oct 31, 2004 11:19 pm
Post subject:

Unrecoverable error (5): Error in loading module 'security:security'

it wont load

Dr Brain - Mon Nov 01, 2004 6:38 am
Post subject:

Then freqs won't be private.

TeHsU - Mon Nov 01, 2004 12:33 pm
Post subject:

Exactly, now it seems to me the security.so is bad, any ideas what could be wrong?

Dr Brain - Mon Nov 01, 2004 3:19 pm
Post subject:

Out of date, probably.

TeHsU - Mon Nov 01, 2004 4:40 pm
Post subject:

Its in the 1.3.2 Folder...Any ideas where to get a later version, cuz this isnt working well, this is the only thing thats messing with me hosting asss

TeHsU - Mon Nov 01, 2004 6:33 pm
Post subject:

Just to addon, its FreeBSD, and i downloaded 1.0RC2, which had a totally different security.so it had freebsd things inside of it, so maybe it needs to be compiled customly?

Grelminar - Tue Nov 02, 2004 3:07 am
Post subject:

You can't use linux binaries on freebsd. Well, at least not easily. If you want to use the linux binary of security.so (which is what's included in the package), you'll probably have to run the whole thing in linux emulation. I have no experience doing this, so I can't help. I might be able to compile security.so for freebsd, though. What version are you using?

TeHsU - Tue Nov 02, 2004 8:58 am
Post subject:

4.10, i can give you a shell on my server, and you can compile it for me if you want..

TeHsU - Tue Nov 02, 2004 10:22 pm
Post subject:

Yeah, i think i just fixed my linux emulator
UPDATE: so yeah it works, but i lost all the edits i did in the source

TeHsU - Tue Nov 02, 2004 11:39 pm
Post subject:

If grelminar you can make me the .so files on freebsd or let me compile it myself, it'd be so much easier for me, or you can compile it on my server, i got the linux running, but to add my own source updates i need to compile it on a linux box and make precompiled binarys, which I dont have

Grelminar - Wed Nov 03, 2004 3:37 am
Post subject:

First, don't make new topics just to get more attention. This board has a wonderful feature that highlights topics with new posts, and I see them and read them.

Second, try this and see if it works.

TeHsU - Wed Nov 03, 2004 1:40 pm
Post subject:

Sorry about that, The security module loads, but the freqs are not private, I checked the Team:PrivFreqStart, but it doesnt want to work

I <cmod> loading C module 'security' from 'security'

but they still show up

ADDITION: After putting in the security module, we're having checksum mismatchs allover

TeHsU - Thu Nov 04, 2004 12:48 am
Post subject:

I got a friend with gentoo i think, not sure what hes running but its linux, i got the source, i edited, put it on, compiled it, and it seems to work fine

, so everythings fine now, but to compile a module i have to do it on his box, which is a downpoint, so that security module would still be greatly appreciated, but if not possible its ok..and good job

Grelminar - Thu Nov 04, 2004 1:09 am
Post subject:

It's possible the one I compiled for freebsd is somehow buggy, but I think it's more likely that your server is just configured badly. Do you have cont 0.39pr1 in clients/continuum.exe? and are you using the scrty/scrty1 files that came with 1.3.2?

TeHsU - Thu Nov 04, 2004 12:19 pm
Post subject:

Well, I tried the linux part with emulation works fine, so i dont think its the server..What version of FreeBSD did you compile it on?

TeHsU - Thu Nov 04, 2004 7:18 pm
Post subject:

I figured out whats up, ur security module for freebsd works, it was my compile that was bad, the core.c was changed a little, i was trying to let it enter .38, and i changed

Code: Show/Hide

if (p->type == T_CONT)
{
struct {
u8 type;
u16 contversion;
u32 checksum;
} pkt = { S2C_CONTVERSION, CVERSION_CONT, contchecksum };
net->SendToOne(p, (byte*)&pkt, sizeof(pkt), NET_RELIABLE);

lr.exechecksum = contchecksum;
lr.codechecksum = codechecksum;
}

that to

Code: Show/Hide

if (p->type == T_CONT)
{
lr.exechecksum = -1;
lr.codechecksum = -1;
}

basically it let anyone enter, but problem was, the freqs wernt private, so the freqs are private now..

Now is there anyway to let .38 enter?

i88gerbils - Thu Nov 04, 2004 11:02 pm
Post subject:

I think 1.3.2 is compiled to let .39 enter only?

Grelminar - Thu Nov 04, 2004 11:59 pm
Post subject:

Correct. I don't think it's worthwhile to let more than one version connect. The concensus seemed to be for .39pr1, so that's what it does now. If you want different, you'll have to hack it yourself.

TeHsU - Fri Nov 05, 2004 12:39 am
Post subject:

Ah, Ok, Well hopefully .39 comes out soon then..

TeHsU - Fri Nov 05, 2004 12:47 am
Post subject:

Any ideas on map checksum mismatch?

Smong - Thu Nov 11, 2004 5:30 pm
Post subject:

There was a bug in mapdata.c sometime ago (wrong struct field or something), not sure which version it was in and I know there was a fix for it made. Could be a different problem though.