home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #20 / NN_1992_20.iso / spool / comp / unix / bsd / 5753 < prev    next >
Encoding:
Internet Message Format  |  1992-09-15  |  1.2 KB
  1. Path: sparky!uunet!spool.mu.edu!uwm.edu!ogicse!pdxgate!rigel!brians
  2. From: brians@rigel.cs.pdx.edu (Brian Smith)
  3. Newsgroups: comp.unix.bsd
  4. Subject: 386BSD Routing?
  5. Summary: routing doesn't work
  6. Keywords: routing, 386bsd
  7. Message-ID: <6104@pdxgate.UUCP>
  8. Date: 15 Sep 92 23:05:40 GMT
  9. Article-I.D.: pdxgate.6104
  10. Sender: news@pdxgate.UUCP
  11. Lines: 23
  12.  
  13. I have 386bsd running just wonderfully except for one simple problem:
  14. routing isn't happening.  I have a Western Digital ethernet card and a
  15. SLIP connection working just fine.  The problem is that packets aren't
  16. being routed between the two interfaces.  I didn't set the NOROUTING
  17. option in the kernel build, so I am at a loss.  Is the functionality
  18. expected to work?  I really do believe that I have the routing tables
  19. primed correctly.  RIP should take care of the rest.  Routed is started
  20. with the -g option, so that routing is propagated via the RIP protocol.
  21.  
  22.     ifconfig we0 192.203.133.4
  23.     ifconfig sl0 192.203.133.3 137.39.73.3
  24.     route add default 137.39.73.3
  25.  
  26. The problem is that 192.203.133.2 can't ping 192.203.133.3, nor can
  27. it ping 137.39.73.3.
  28.  
  29. This is fairly critical, so if anyone can help me with this, I'd *REALLY*
  30. appreciate it.
  31.  
  32.  
  33. Thanks,
  34. Brian Smith
  35. brians@rigel.cs.pdx.edu (503)645-5400ext138 and (503)524-4693
  36.