I do not have any experience with nailed connections yet, however here
is a solution for pipeline's that are using nat on a non-nailed link.
A couple of recommendations for telnet.. Under ethernet -> nat -> nat
you can set the default server to the local ip thats on their lan. This
will cause any connections coming into the pipeline to be routed to the
pipeline's address (if you set it at the pipeline's lan address) and
therefore enabling you to telnet in.
Another more recommended solution is go under ethernet -> nat -> nat ->
static mappings and setup port 21 to port 21 with their lan address
under loc adrs, this will cause any incoming connections to port 21 on
the pipeline to be sent to the pipeline itself on port 21 therefore
enabling telnet. I've included a static mapping below.
For example a pipeline that is configured for NAT that has a lan adress
of 10.0.0.1
ethernet -> nat -> nat -> static mappings
Valid=Yes
Dst Port#=21
Protocol=TCP
Loc Port#=21
Loc Adrs=10.0.0.1
would allow you to telnet to the pipeline.
Hope this helps,
Anthony
Scott Kozicki wrote:
>
> Has anyone figured out a way to monitor a Pipeline that is doing NAT
> over a nailed link? Appearently, once you've turned on NAT, you cannot
> ping or telnet to the Pipe. I remember this being an issue (and seeing a
> solution) for DHCP based Pipes, but not nailed.