|
2006-06-11 11:23
|
Network_error.jpeg (149,372 bytes) |
|
|
Network error looks weird too |
|
|
I'm not one to care much for MS internals regarding network support, but this should be as easy as only counting modem and ISDN device types. Though, I think it would be better to just filter VPN devices and hit on anything else. I don't care to redo any code to handle other connection types properly (like IrDA, ATM, parallel, PPPoE, etc.). I'll add the VPN filter later today, but anything else would require more knowledge of the RAS internals that I care to ever know. |
|
|
This code change should be in the RC2 build. Have you had a chance to try it out? |
|
|
Do you mean this build http://www.hard-light.net/forums/index.php/topic,40410.0.html ? I tried it, its the same. I just dont understand this bug, why we cant be connected to the internet and play on LAN at the same time? |
|
|
You can't because the code isn't able to figure out how to route the game traffic properly. What other connections do you have active when you play over LAN? All I fixed was to allow for VPN connections, but if you have more connections active (even PPPoE) then it doesn't ignore those. |
|
|
I have active internet and Hamachi only, no PPPoE or other. |
|
|
If you are just using dial-up or something then that's nothing I'm going to fix. The FS2 network code is already freaky enough, and I don't want to ever add more RAS knowledge to my brain. Unless you want to work on it, we'll probably close this as a won't-fix, at least until someone else steps forward to have a go at it. |
|
|
Ok, you should close it I cant programming. |
|
|
Hopefully someone who knows more about RAS programming can take a look at the net code at some point. I'll keep that in mind to ask any new programmers who join the project. For now... Closered. |
|
|
I am reopening this because the bug should be fixed in fs2open369 rc4 but it is not. Try to allow RAS VPN connects since they probably aren't dial-up and shouldn't be seen as such |
|
|
Run a debug build, go to the point where it gives you the error, then exit and attach your multi.log file (from the data/ directory) here. |
|
2006-07-09 11:59
|
|
|
|
Here is it. I had Hamachi online when I ran debug. |
|
|
Hmm, it says that it found no RAS connections. Filtering the VPN connections out doesn't happen unless it finds at least one, so it just not getting to that point. Without knowing more about the RAS API I have no clue what to do here. We'll just leave this open until I can find the time to research this a bit more. |
|
|
Ater looking over the code I can see no possible way that you will be able to get that error message from that multi.log. Did you get the error from the session that the multi.log is from? |
|
|
Is multi.log always from the latest multi session like fs.log? |
|
|
It's supposed to be. But the multi.log is timestamped so it's pretty easy to see that the log you posted was created on "Tue, Jul 04, 2006 at 09:01PM", and closed 6 minutes later. Is that the last build that you ran when you posted the log? |
|
2006-07-16 12:31
|
|
|
|
Yeah the right log is multi2.log the previous was incorrect i posted log from main data directory but I had mediavps mod. |
|
|
btw I had new build http://icculus.org/~taylor/fso/testing/multi_test.rar while running multi2.log debug. |
|
|
It still only found one connection (the ADSL/ISDN) and didn't recognize the VPN as being active. All I can do at this point it just let it ignore the VPN connection as RAS, I can't make a direct ISDN/PPPoE connection also get ignored since that's just inviting trouble. The bug is fixed, VPN connections won't be detected as a RAS connection, but that won't solve the dial-up/LAN setting issue when directly connected to the internet via standard dial-up, ISDN, or PPPoE. The only thing that you can do is to get your internet connection working via LAN (via router or a networked computer), then the VPN bug that got fixed will allow everything to work normally. |
- Anonymous
