> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]

I didn't see any replies, so I'll throw some chum out ;-)

>   I have a RAS box that uses 198.168.X.X coming in from the 
> field and my  router is using 10.X.X.X .

OK, tho I /hate/ RFC1918 addys...
Your guys "in the field" are using dialup and are getting
a dynamic addy via DHCP ?   What's the DHCP server ?
Cisco or M$ ?   No error msgs, and plenty of address space?

>  I am using Eigrp 109 for my routing protocol.

OK^2, tho we don't care about the 109

> Here is is my setup?
> 
> router eigrp 109
>  redistribute connected
>  redistribute static
>  network 10.0.0.0
>  network 192.168.1.0
>  distribute-list 6 out Serial0.1
>  distribute-list 6 out Serial0.2
>  distribute-list 6 out Serial0.3
>  distribute-list 6 out Serial0.4
>  distribute-list 6 out Serial0.5
>  distribute-list 6 out Serial0.6          

Um, the rest of the config may be important :-)
Hey, if you're RFC1918, you don't even need to be embarrassed
about posting it ;-)

> Why is it we have to clear the Arp tables so the 192.168.1.0 
> can come inbound to the 10.X.X.X network. 

Dunno.  
Does it *ever* work ?   
Do you just 'clear arp' sometimes when it breaks ?
Or do you have to 'clear arp' to get it working at all ?
Did you try clearing out just /some/ arp entries ?
Who figured out that clearing the arp cache would help,
and how did they figure that out ?

(I used to work w/ JPMorgan.  Whenever I called the NOC w/
a networking problem, the tech would say, "Hang on, I'm
gonna clear the arp cache."   If that didn't work, he'd
flush the routing table.  Then he'd call an operator.  Hmmm...)

> Any ideas what I should try?

More description of the problem.
A sniffer.
deb ip packet, and friends.  sho arp, deb arp, for ex.
Got any error msgs to tell us ?

T "RFC1918 && NAT hater" H

___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to