On Wed, 18 Jun 2003, Michael Mee wrote:

> Hmm. What happens when you try a traceroute or ping from a machine on
> your LAN?  Destination unreachable or timeout or ???

Both ping and traceroute work fine.

> I'm guessing you need a route setup in the firewall so it will
> redirect appropriately. I don't know enough about the route command to
> do it, but here's a start:
*snip*

Hmm, now this is interesting. The output of "/sbin/route get
wonko.com" is this:

   route to: dsl093-174-104.pdx1.dsl.speakeasy.net
destination: dsl093-174-000.pdx1.dsl.speakeasy.net
       mask: 255.255.255.0
  interface: sis1
      flags: <UP,DONE,CLONING>
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu
expire
       0         0         0         0         0         0      1500
-5245

That destination looks fishy to me, although I'm really sketchy on what
(if anything) it actually means.

After running "/sbin/route add dsl093-174-104.pdx1.dsl.speakeasy.net
dsl093-174-001.pdx1.dsl.speakeasy.net", the output changes to this:

   route to: dsl093-174-104.pdx1.dsl.speakeasy.net
destination: dsl093-174-104.pdx1.dsl.speakeasy.net
    gateway: dsl093-174-001.pdx1.dsl.speakeasy.net
  interface: sis1
      flags: <UP,GATEWAY,HOST,DONE,STATIC,LOCAL>
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu
expire
       0         0         0         0         0         0      1500
0

That looks more like what I'm seeing for other addresses that I can
access, but I still can't connect to my server via the external address.

I'll continue reading up on route and see if I can figure anything out.
Thanks for all the suggestions.

-- 
Ryan Grove
ryan at wonko dot com
http://wonko.com/