Cannot ping network unless the -g option is used and cannot telnet
I am trying to reach a remote network to telnet to a system on that network. My setup is as such using bogus IP's:
Interfaces:
Local Ethernet - 3.3.3.1
Local ATM Interface - 1.1.1.1 (VLAN)
Server acting as router on distant end (ATM) - 1.1.2.5
Distant system trying to telnet into - 2.2.2.1
Local Routes added:
1.1.2.01.1.1.1
2.2.2.01.1.2.5
default3.3.3.1
local system > distant server > distant system
The server on the distant end (1.1.2.5) is on the network with the local ATM interface (1.1.1.1), and it is also on the network with the distant system (2.2.2.1) I'm trying to telnet into.
If I try to ping or telnet into the distant system (2.2.2.1) I get nothing, if I ping the distant system with the -g option ( ping -sg 2.2.2.1 1.1.2.5 ) I get a successful ping.
Does this make sense, if the route is in the table to use the 1.1.2.5 interface to get to any 2.2.2.0 address why does it only work if I use the ping -g? I've also made the route a class D in the route table but it didn't change anything. If I could force the telnet like the ping I could likely log in, but I'm not aware of a way to do that and I'd rather it worked as is should.
As a note, the local ATM interface is a VLAN because there are additional ATM networks configured. If I traceroute it does go out the correct interface which is isar0:3.
Thanks for the assistance.
