GitPS / PiCasino

Java based casino game hosted on a Raspberry Pi.
GNU General Public License v3.0
1 stars 0 forks source link

Connecting via WiFi and on a Pi #27

Closed ghost closed 10 years ago

ghost commented 10 years ago

I get the following error message when connecting to a RaspberryPi server connected to a router from my laptop connected via WiFi to the router.

capture

GitPS commented 10 years ago

Try it with a wired connection. WiFi may not be a reliable enough connection for this to work. I will try it with my laptop on WiFi and let you know what happens.

GitPS commented 10 years ago

Via WiFi:

Server

blackjack
server
Nov 15, 2013 11:43:40 PM com.piindustries.picasino.blackjack.server.ServerNetworkHandler <init>
INFO: Server is running and waiting for connections...
Nov 15, 2013 11:47:00 PM com.piindustries.picasino.blackjack.server.ServerNetworkHandler$1 connected
INFO: Client connected with ID: 1
Nov 15, 2013 11:47:00 PM com.piindustries.picasino.blackjack.server.ServerNetworkHandler addConnectedUser
INFO: Added username: phil with ID: 1

Client

blackjack
client
192.168.1.6
Phil
What action?
    ADD_PLAYER
    REMOVE_PLAYER
    ADVANCE_TO_BETTING
    BET
    PASS
    ADVANCE_TO_DEALING
    DEAL_CARD
    ADVANCE_TO_PLAYING
    HIT
    SEND_CARD
    STAND
    SPLIT
    DOUBLE_DOWN
    ADVANCE_TO_CONCLUDING
    ADVANCE_TO_INITIALIZATION
    MESSAGE
    PING
    INTEGRITY_CHECK
    PLAYER_DISCONNECT
    REQUEST_GAME_STATE
Nov 15, 2013 11:46:57 PM com.piindustries.picasino.blackjack.client.ClientNetworkHandler$1 connected
INFO: Connection with server established.
GitPS commented 10 years ago

I finally got my Pi up and running. I have it connected via an ethernet cable to my router. I was able to connect 7 clients from my desktop to the Pi which was running the server. Memory usage was under 40mb total for the Pi. CPU stuck between 0.0% - 5.0% when a connection was being made.

20131116_112648

areis422 commented 10 years ago

All, please try using SSH to connect to the Pi @ my place: dev1.andrewreiscomputers.com:2222. You can either use SFTP or SCP to copy your JAR files there or pull the source directly from GitHub. I have port 60000 open in my router so you should be able to connect via the client from your pc over the WAN to the Pi

I'll create user accounts for everyone, but the root login is: username: pi password: raspberry

Andrew Reis CompTIA Network+ Microsoft Certified Technology Specialist Cell: (608) 797-1481 Email: reis.andr@uwlax.edu

On Sat, Nov 16, 2013 at 11:38 AM, Phil notifications@github.com wrote:

I finally got my Pi up and running. I have it connected via an ethernet cable to my router. I was able to connect 7 clients from my desktop to the Pi which was running the server. Memory usage was under 40mb total for the Pi. CPU stuck between 0.0% - 5.0% when a connection was being made.

[image: 20131116_112648]https://f.cloud.github.com/assets/5472140/1556684/d6e9b12e-4ee5-11e3-925b-f7e9d612cfa2.jpg

— Reply to this email directly or view it on GitHubhttps://github.com/GitPS/PiCasino/issues/27#issuecomment-28631510 .

GitPS commented 10 years ago

Aaron and I spoke with Professor Berns this afternoon about this issue. We were able to reproduce issues similar to it (they weren't the exact error). My guess is that all of these issues stem from the TCP connection not being fully established before objects are sent across the network. This is likely leading to incomplete objects being received on the client.

Prof. Berns and I were able to make connections between his desktop/netbook and my laptop. The desktop was on the wired network and the netbook was on UWLSecure. My laptop was on UWLSecure and wired for a seperate test. All the connections were successful between our computers.

The problem is likely completely negated when using a LAN that has no interference. Therefore, I am closing this issue as "wont fix" simply because we do not have time to debug an issue that will not prevent our application from working. This is something I would like to have a solution for, but it isn't worth anymore effort when we have bigger issues to work on. If, in future, we discover issues with LAN connections we may need to revisit this, but for now I'm no longer worrying about it.

Prof. Berns also stated he wouldn't worry about it if we can only use a LAN.