Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ikbent

Pages: [1]
1
Technical Help: Problems BEFORE entering the game /
« on: June 06, 2005, 11:33:57 pm »
Let me guess...
I think.... it may be the line saying:

;Video.OpenGL.UseExtension.GL_SGIS_generate_mipmap = false

And, errrrrm, you may just find it in

data/config/r3dopengl.cfg

But, of course, all of this is blind guessing.

2
Technical Help: IN GAME bugs (after loading world) /
« on: May 15, 2005, 11:59:28 am »
Oos some errors there:

iptables -A INTPUT -t udp --dport 7153 -j LOG --log-level debug --log-prefix \"INPUT udp at 7153: \"

should read:

iptables -A INPUT -t udp --dport 7354 -j LOG --log-level debug --log-prefix \"INPUT udp at 7354: \"

3
Hi there,

To monitor ip traffic in linux, you could try the following:

You could use nmap to check whether port 7354 is open. However, it will only show as being open when YOUR computer is waiting for a connection to come in on that port, which I doubt. However, if indeed your computer is waiting for a connection to come in on 7354, try the following:
  start planeshift
  go to another machine (running unix)
  do: nmap your.ip.address (at a command prompt)
This will give you the list of open ports. Ports that are blocked by a firewall will most likely be in the \"filtered\" state, ports that are open but don\'t have an application listening are most likely to be in \"closed\" state, and ports that have an application listening are in \"open\" state. However, it is often possible to configure your firewall so that ports that the firewall blocks are in \"closed\" state: this depends on the choice and configuration of your firewall.

Also worth trying is monitoring all network traffic coming in on the ports you\'re interested in, or on all ports. You can use the IP tables command for this. For example:

iptables -A INPUT  -j LOG --log-level debug --log-prefix \"INPUT PACKETS; \"

This command will log all incoming traffic and will put a log line in the debug log file (e.g. /var/log/debug)

You can also log outgoing traffic (by changing INPUT to OUTPUT) or only logging traffic that comes in at a specific port, e.g., for ingoing traffic at UDP 7354:

iptables -A INTPUT -t udp --dport 7153 -j LOG --log-level debug --log-prefix \"INPUT udp at 7153: \"

Finally, the tcpdump program is useful for logging tcp traffic.

Hope this is helpful,

Robert

Pages: [1]