At 04:40 AM 8/26/98 -0700, you wrote:
>Actually, looking at this again, here's the problem with your 
>ping:
>
>You've got an interface set up (de0) that automatically creates a 
>route to q.r.s.* via that interface, where * is "everything except
>myself".  There's actually a separate "host route" for the
>interface itself that says "don't go out the interface, process
>packets locally".  So, when you add the route to q.r.s.27 via the
>local address, the packets never actually get sent anywhere.

aha... hrm... so should I do a route delete on the q.r.s.0 before
adding my route?

>Try it without adding the route to .27

ok, will try

>Of course, this still doesn't solve the problem of getting packets
>from one side to the other...

I was hoping to have arp help me out on that one ;)

>On Wed, 26 Aug 1998, Paul Goyette wrote:
>
>> How would you expect this to work?  You've explicitly told the 
>> machine "to get from here to address q.r.s.27, send packets
>> out to q.r.s.202"
>> 
>> Basically, your set-up cannot work.  You can't have both of
>> your interfaces set up for the same Class C network and expect 
>> it to figure out which host(s) are on which side.  You need to
>> get a _separate_ address space for the second interface. 
>> 
>> On Wed, 26 Aug 1998, nm wrote:
>> 
>> > I run 1.3.2 on a DEC Alpha
>> > 
>> > I have both a de0 and a de1.
>> > on the de0 side q.r.s.27 is a host
>> > on the de1 side the rest of the q.r.s class c sits.
>> > 
>> > My question is should the following work?
>> > 
>> > root@anomoly:~$ ifconfig de0 q.r.s.202 255.255.255.0
>> > root@anomoly:~$ route add -host q.r.s.27 q.r.s.202
>> > add host q.r.s.27: gateway q.r.s.202
>> > root@anomoly:~$ ping q.r.s.27
>> > PING q.r.s.27 (q.r.s.27): 48 data bytes
>> > ^C
>> > ----q.r.s.27 PING Statistics----
>> > 4 packets transmitted, 0 packets received, 100% packet loss
>> > 
>> > Should I ping be working or not?
>> > Did I screw up the route?
>> > 
>> > Thanks,
>> > Nick
>> > 
>> 
>>
-----------------------------------------------------------------------------
>> | Paul Goyette      | Public Key fingerprint:    | E-mail addresses:
   |
>> | Network Engineer  |   0E 40 D2 FC 2A 13 74 A0  |  paul@whooppee.com
   |
>> | and kernel hacker |   E4 69 D5 BE 65 E4 56 C6  |
paul.goyette@ascend.com |
>>
-----------------------------------------------------------------------------
>> 
>> 
>
>-----------------------------------------------------------------------------
>| Paul Goyette      | Public Key fingerprint:    | E-mail addresses:        |
>| Network Engineer  |   0E 40 D2 FC 2A 13 74 A0  |  paul@whooppee.com       |
>| and kernel hacker |   E4 69 D5 BE 65 E4 56 C6  |  paul.goyette@ascend.com |
>-----------------------------------------------------------------------------
>
>