A2 OA 1.54 BAF client unable to connect to A2 OA 1.54 BAF Lite DS

**Victim ZSU** · Aug 30 2010, 00:53

it seems part of the issue is that with modline checking turned on the server, there is implicit modline checking, even if one is not specified on the client.

i.e. if client has A2 1.54 OA BAF and has no modline set, the implicit modline is actually ArmA 2; ArmA 2 Operation Arrowhead; British Armed Forces

and if the server has A2 1.54 OA BAF (Lite) and has no modline set, the implicit modline is actually ArmA 2; ArmA 2 Operation Arrowhead; British Armed Forces (Lite)

I ask again, does everyone else just run their server with modline checking off?

**Defunkt** · Aug 30 2010, 01:10

What do you mean by modline checking? equalModRequired=1 or verifySignatures=1? The first is inflexible and deprecated in favour of the second. If you wanted to go to the trouble of enforcing the use of certain mods you'd be better off making them mission dependencies.

**SWAT_CDN** · Aug 30 2010, 02:59

Defunkt I think what Victim ZSU is "equalModRequired=1 or verifySignatures=1" as you said.

When a dedicated server runs with "equalModRequired" or "verifySignatures" turned off there is no issues.

This is something we do not want to turn off in our server, hopefully we can get some sort of answer.

I guess this would be the major question to the server admin's.
Admin, are you running with these off?

**Defunkt** · Aug 30 2010, 03:16

You post as though they are either both on and or both off when in fact they achieve distinctly different things. Leave verifySignatures on and turn equalModRequired off, the former controls what addons players can have running and if you also want to dictate which mods players must have it's better set in each mission's "RequiredAddons" list. equalModRequired is pedantic and inflexible and would appear from your posts to not cope with the distinction between BAF Lite and BAF Full.

**Dwarden** · Aug 30 2010, 03:33

yep equalModRequired is deprecated and shall be used only if you want 1:1 user to client content

**SWAT_BigBear** · Aug 30 2010, 03:50

This is what happens with equalmods off, verifysig on, when I join with Full BAF my side, 1.54 BAF Lite on the server.

**Defunkt** · Aug 30 2010, 03:53

What is the content of the server's \Keys\ folder? What is the content of the client's \BAF\AddOns\ folder?

**SWAT_BigBear** · Aug 30 2010, 04:11

Server's Key Folder has bi.bikey only.

Client BAF/Addon..hmm
15 PBO's
16 BISIGN's

Only thing that looks odd.
dubbing_baf PBO
dubbing_baf.pbo.bi.bisign BISIGN
dubbing_baf.pbo.bisign BISIGN

Edit, also I bet that screen shot would list all 15 PBO's if it was able to.

**Defunkt** · Aug 30 2010, 04:20

Yeah I had that dubbing_baf.pbo.bisign file also, I just removed it, no ill-effects.

The rest is odd. So this is a Combined Operations server running on Windows? Might be a good idea to start a DOS prompt in the ArmA2 root and enter...

dir /s > arma_dir.txt

...then post arma_dir.txt (from that folder) along with your server's command line.

**SWAT_BigBear** · Aug 30 2010, 04:54

Windows Server 2003 x64
A2 then added OA standalone.
cmd line in FireDaemon, -config=server.cfg -cfg=arma2.cfg
rpt.
Spoiler:

Thread: A2 OA 1.54 BAF client unable to connect to A2 OA 1.54 BAF Lite DS

Thread Tools

Display

Posting Permissions