14 messages in com.perforce.perforce-user[p4] Re: Across Firewall| From | Sent On | Attachments |
|---|---|---|
| Lai, Wing Hon | 03 May 2001 01:59 | |
| Sebastian Rahtz | 03 May 2001 02:18 | |
| Lai, Wing Hon | 03 May 2001 02:22 | |
| Simon Morton | 03 May 2001 09:03 | |
| Dave Lewis | 03 May 2001 09:24 | |
| Stephen Vance | 03 May 2001 09:32 | |
| Ganesh Kondal | 03 May 2001 10:17 | |
| Justus Pendleton | 03 May 2001 11:06 | |
| Stephen Vance | 03 May 2001 15:47 | |
| Ganesh Kondal | 03 May 2001 16:54 | |
| Chri...@ClassiX.de | 04 May 2001 01:20 | |
| Stephen Vance | 04 May 2001 09:35 | |
| Ganesh Kondal | 04 May 2001 11:45 | |
| Ganesh Kondal | 04 May 2001 15:54 |
| Subject: | [p4] Re: Across Firewall![]() |
|---|---|
| From: | Stephen Vance (ste...@vance.com) |
| Date: | 05/04/2001 09:35:19 AM |
| List: | com.perforce.perforce-user |
At 10:20 AM 5/4/2001 +0200, Christian.Langmann at ClassiX.de wrote:
Hi,
Maybe this is an idea:
1. the output
------------- [gkondal at Cobra gkondal]$ Address 127.0.0.1 maps to gkondal-lt, but this does not map back to the address - POSSIBLE BREAKIN ATTEMPT! -------------------
states, that you try to login from localhost (127.0.0.1), which can be mapped to gkondal-lt. Okay. I guess gkondal-lt also has a "real"-IP-address, hasn't it? Try to use this one - I'm afraid I don't know where localhost comes from in your settings. I think it's quite common that a dns-name isn't resolved to 127.0.0.1 but to the "real" IP-address.
If you have set up the host name as another alias for 127.0.0.1 in the hosts file and the hosts file is the first or only authority for domain name lookup, you would get this result.
2. To test whether a request reaches the server or the firewall or something in between you can use a IP-sniffer. You can set a filter for the Perforce-Server-Port (1666 I guess).
If that fails, you can set up a shell script as an inetd service on that TCP port (shutting down the Perforce server, of course, to make the port available). All it has to do is cat to a file. The only problem you will have is that unless the Perforce protocol ends requests with EOF (generally ctrl-D), the process will hang because cat doesn't know to end. It's a good quick way, however, to check for connectivity.
Steve
Stephen Vance mailto:steve at vance.com http://www.vance.com/




