FFXI-Boot Mod 3.1 Hairpin Question

[Azalia]

I'm using the latest FFXI-Boot with the hairpin option to connect to a local private server. ZoneIP on the server is set to my external address and all remote connections are working fine.

When I attempt to login locally with the --hairpin option, I am able to login completely and move around the current zone. Once I attempt to change zones I immediately R0. On the server the Game Server log has the following error repeating:

[Error][0m map_encipher_packet: bad packet from <192.168.1.58>

If I change the ZoneIP to the servers local IP address and remove the --hairpin option on the client I have no issues. The following is my boot command line in Ashita:

<setting name="boot_command">--hairpin --server 192.168.1.4</setting>

Hopefully I'm missing something easy; before FFXI-Boot Mod 3.1 I could not connect at all with hairpin since it was broke.

Server Information:
Revision - 3605
Modified files: login_darkstar.conf, map_darkstar.conf, search_darkstar.conf, settings.lua

Thanks for all the great work you guys are doing!

[bluekirby0]

The hairpin option was fixed and tested on the US client. I do not know if the offset is the same for other client versions. I did test zoning locally on a LAN server (10.11.15.16) with zoneip set to localhost (127.0.0.1) without any problems.

If you are running a different client version than US, that is the most likely cause. There are a few additional functions I have offsets for that can be NOP'd as well if they are found to be causing problems.

[Azalia]

Thanks for the reply, I'm running the US version.

I just setup FFXI on a second computer and got the same results. Follow the wiki to the letter:

1. Installed FFXI (All expansions including SoA)
2. Applied Update Patch
3. Created fake member account in POL and checked/downloaded files.
4. Moved data folder
5. Downloaded Darkstar Ashita and setup the following boot command in profile
- <setting name="boot_command">--hairpin --server 192.168.1.4</setting>

[0m[08:07:30][1;37m[Info][0m [1;37mmapsession[0m:[1;37m192.168.1.1[0m:[1;37m54090[0m is coming to world...
[08:07:31][1;37m[Info][0m parse: 00A | 0001 0000 2E from user: Azalia
[08:07:31][1;36m[Debug][0m [1;36mCZone:: Port_Windurst IncreaseZoneCounter <1> Azalia
[0m[08:07:31][1;31m[Error][0m map_encipher_packet: bad packet from <192.168.1.58>
[08:07:32][1;31m[Error][0m map_encipher_packet: bad packet from <192.168.1.58>
[08:07:34][1;31m[Error][0m map_encipher_packet: bad packet from <192.168.1.58>
[08:07:36][1;31m[Error][0m map_encipher_packet: bad packet from <192.168.1.58>
[08:07:37][1;31m[Error][0m map_encipher_packet: bad packet from <192.168.1.58>
[08:07:39][1;31m[Error][0m map_encipher_packet: bad packet from <192.168.1.58>
[08:07:41][1;31m[Error][0m map_encipher_packet: bad packet from <192.168.1.58>
[08:07:43][1;31m[Error][0m map_encipher_packet: bad packet from <192.168.1.58>
[08:07:45][1;31m[Error][0m map_encipher_packet: bad packet from <192.168.1.58>
[08:07:47][1;31m[Error][0m map_encipher_packet: bad packet from <192.168.1.58>
[08:07:49][1;31m[Error][0m map_encipher_packet: bad packet from <192.168.1.58>
[08:07:51][1;31m[Error][0m map_encipher_packet: bad packet from <192.168.1.58>
[08:08:32][1;36m[Debug][0m [1;36mmap_cleanup: Azalia timed out, session closed

Just to test this computer and make sure it wasn't the issue I did the following:
1. Created a VPN connection from this computer to an external network (wanted to get off the local network)
2. changed Ashita boot command to:
<setting name="boot_command">--server myexternalIP</setting>

Once I logged in, server logs where showing the connection from the external network. I was able to zone without any issues.

Hopefully this info helps, thanks for the help.

[bluekirby0]

Alright I'll look into NOPing those other functions then and see if that helps.

[Azalia]

Thanks for all the help Bluekirby0!

Just a little more information for you, hope it helps.

I replicated how you tested by setting up the server on the same machine I was using as the client. ZoneIP set to machines IP and hairpin used with 127.0.0.1. I was able to connect and zone without any issues.

The problem seems to occur when the server is a dedicated machine.


Thanks again!

[bluekirby0]

No, what I tested was using 127.0.0.1 as the zoneip setting with a server running on a different machine on the LAN and using the LAN IP with the hairpin option.

[Azalia]

Oh my mistake, I'll try that and see what the outcome is.

[bluekirby0]

Try again with 3.1.1

Everything should be sorted now.