10001110100110101
Argh! It did it again! This is really annoying. I really should get his page off of Scienide and onto a local machine soon. Anyway, I've been playing around with static IPs for the LAN and things seem to be progressing slowly. There's more to talk about I guess, like AgentP's voyage into Sweden (which he really should start up some sort of web journal of sorts) and my ongoing attempts to get this blasted LAN to function, and my ever belated attempts to clean up my room. Oh yeah, does anyone know how to get Microsoft Netmeeting to live happily with my router? (i.e. Does anyone know which port it accesses?)
Okay, I'm going to cut this short before I get cut off. Hopefully the connection will be more stable later in the day..
Thursday, September 07, 2000 at 23:03:03 (UTC)
The quick and clever solution (good old Microsoft) to get netmeeting going is... open all ports for UDP. (1024-65535)
Alternatively, you can look for a proxy that supports H.323 - you'd have to proxy all those ports, I guess...
Note this is only if you want the audio and visual stuff.
Otherwise..
389 Internet Locator Service (ILS) TCP
522 User Location Service TCP
1503 T.120 TCP
And these two (along with the big block 'o everything) for A/V
1720 H.323 call setup TCP
1731 Audio call control TCP
And yes, that is rather silly. It's obviously been designed by people with no understanding of firewalls.
the mad bomber what bombs at midnight
Friday, September 08, 2000 at 05:39:32 (UTC)
DMZ it is then!
QYV
Friday, September 08, 2000 at 22:53:26 (UTC)
Install linux on that damned 486 - set it up as a gateway temporarily (with 2 interfaces) and then make the one lan machine start up netmeeting while it tcpdumps all traffic on both interfaces... thats how I got the port(s) for Diablo 2 and Age of Empires.
Tux
Friday, September 08, 2000 at 22:56:55 (UTC)
Ahem - reading that last comment I noticed an ambiguity... the gateway runs 'tcpdump' while another machine runs netmeeting. tcpdump will record ALL tcp headers from every packet that arrives/leaves, all you have to do is find all entries that have the IP address of the machine running netmeeting and record the ports and protocols that it is using. Lemme know if you need a hand with it.
Tux2
Saturday, September 09, 2000 at 09:54:31 (UTC)
Perhaps I wasn't sufficiently clear - the ports I listed are the ports needed. The first three should be used for the file sharing, etc. For the audio/visual stuff, Netmeeting uses H.323 to dynamically determine ports. The reason you need to have a whole pile open (or proxied) is that the INCOMING calls are to random ports -s niffing will only tell you the port which was used for that particular connection.
A DMZ? Do you have that many machines? (I'm curious, does girl have any security at the moment?)
the misunderstood mad bomber
Saturday, September 09, 2000 at 14:24:03 (UTC)
Currently, I've only got three computers hooked up to the LAN. The Linksys allows one computer to be thrown out into the DMZ for situations like this. But this also means that there's probably no security for girl's machine right now. *looks around cautiously*
QYV