Re: File upload works on wlan but not directly

Hi Jorlebar,

Yes, there is currently the "issue" that the upload box doesn't work in situations out of the normal PirateBox environment. As the Upload box is served by an additional daemon on a different port, we currently need to use an iframe that points to a specific address. This address usually can be resolved during the PirateBox's dns service and everything is fine.
When you run PirateBox in an environment, where the Box is only a dedicated device, the dns name "piratebox.lan" can't be resolved by the normal DNS server on the network. That ends up in the "hostname not found" message inside the iframe. Stupid, I know.

Quote

Also I would like to add that the address pirate box.lan does not work for me, and does not resolve to anything when I do a nslookup.

Yes, that doesn't work, while you are connected to your normal network. It doesn't know anything about the domain name "piratebox.lan"

If you want to access the uploadbox from your non-piratebox-network via ethernet you should enter the IP of the box followed by the Port:

Language: PHP
http://192.168.x.y:8080

That should bring you up the UploadBox
We are working on a new better integrated upload-interface, but in the lack of my JavaScript & HTML skills, there is currently no progress for a nice integration.

Quote

Also there is another home page running on 192.168.77.1 but no other links work on that page.

I don't understand that part. The webserver (lighttpd) is running on each network interface, which is available on the running Pi, and it should serve the same homepage everywhere.
If you connect via WLAN to the PirateBox, you get an IP in the segment 192.168.77.x and the PirateBox deliveres always the IP 192.168.77.1 for the asked domain.

EDIT: And chat does not update automatically on the Wlan - but does work through the direct ip connection but it takes a long time 1-2minutes to update =/

this is something, I understand, but I can't follow it. We already started a thread here. It seems this is a browser specific issue. I can't reproduce it and technically, there is no magic running on the backend.
When you post a message, that message is added to a storage file, which is used for generating a static html page (chat_content.html). This file is re-read by a JavaScript on the Browser.
Feel free to contribute in finding a solution in the other thread, because on every device I tested it, it worked. btw: the chat reload happens every 10 seconds.

Hope that helps a bit,
best regards Matthias