Tamadite
07-12-2004, 20:11
When establishing a FTP connection to a server that uses port 113 for identification (IDENT) I can observe the following:
TCP handshaking via port 21 elapsed time: 511ms
Delta time between TCP ACK packet and IDENT packet: 28ms
I can see that when using port triggering on my WL-500g it still drops the incoming packets with port destination 113 sent by the FTP server to my client. Port trigger is configured and enabled as follows:
Trigger port: 21
Protocol: TCP
Incoming port: 113
Protocol: TCP
LAN-to-WAN firewall disabled.
WAN-to-LAN firewall active on drop mode. Rule: any:any to any:113 TCP
The 113 packet attempt goes through the firewall without problems when using port forwarding.
All given ports are "destination port" always.
Is there some problem with "port trigger" implementation in WL-500g firmware release 1.8.1.9?
Is there some way to set up a "Port Trigger Idle Time" to specify the time that incoming ports are open since the outgoing port is triggered?
TCP handshaking via port 21 elapsed time: 511ms
Delta time between TCP ACK packet and IDENT packet: 28ms
I can see that when using port triggering on my WL-500g it still drops the incoming packets with port destination 113 sent by the FTP server to my client. Port trigger is configured and enabled as follows:
Trigger port: 21
Protocol: TCP
Incoming port: 113
Protocol: TCP
LAN-to-WAN firewall disabled.
WAN-to-LAN firewall active on drop mode. Rule: any:any to any:113 TCP
The 113 packet attempt goes through the firewall without problems when using port forwarding.
All given ports are "destination port" always.
Is there some problem with "port trigger" implementation in WL-500g firmware release 1.8.1.9?
Is there some way to set up a "Port Trigger Idle Time" to specify the time that incoming ports are open since the outgoing port is triggered?