That makes sense. Since I don't control the telnet server, I seriously doubt that I'll get anybody to add the route. I'll try out the NAT solution and see if I can get that to work. Thanks.
~Brian On 4/26/07, Bill Marquette <[EMAIL PROTECTED]> wrote:
The telnet server probably has no route back to 192.168.1.0/24. You'll need to either add a route on that machine pointing back at your OPT interface or use advanced outbound nat and nat the traffic from your 192.168.1.0/24 network to something (like the 172.22.99.197 address of your firewall) that is reachable by the telnet server. --Bill On 4/26/07, Brian Neufeld <[EMAIL PROTECTED]> wrote: > Since a picture is worth a thousand words, let me start with that... > http://www.gliffy.com/publish/1062004/ > > I can't figure out how to configure pfSense > (1.0.1-SNAPSHOT-03-27-2007) to allow telnet from any LAN PC to the > telnet server. I have plugged OPT1 in to the partner's switch and it > gets its IP via DHCP. With the interface enabled and no other > configuration, I can ping 172.22.99.1, but no further. The "PC for > telnet" can access the host as expected, but I need the space and > would like to get rid of it, if possible. > > I have tried various firewall rules and static routes. I also > experimented with advanced outbound nat, but I can't find the right > combination of settings. Any help would be appreciated. > > ~Brian
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
