Ray & Charles, Thanks for the direction. I will take a gander back thru the configs, and probably start over with a clean floppy if it doesn't jump out at me. Likely I nicked the code somewhere when I was changing the 192.168.1 references.
It'll be another learning experience :) Dan Quoting Ray Olszewski <[EMAIL PROTECTED]>: > I've not seen that particular error from sendto: before, but Charles' > suggestions are probably the right place to start (even though routing > problems normally generate a different ping error). > > One thing, though: if your hosts are numbered 209.98.58.241, > 209.98.58.244, > and 209.98.58.246, then they are on network 209.98.58.240/29, NOT > 209.98.58.0/29. When checking your setup, you might look for errors > associated with this misspecification (assuming it wasn't just a typo > in > your e-mail). > > At 05:03 PM 1/3/02 -0600, [EMAIL PROTECTED] wrote: > [...] > >...The system at .246 can't ping > >anything in 209.98.58.0/29 --- getting instead: > > > ># ping 209.98.58.241 > >PING 209.98.58.241 (209.98.58.241): 56 data bytes > >ping: sendto: Invalid argument > > > >This system, .246, can ping PAST the router, out to hosts on the > internet, and > >the hosts on the 192.168.2.0/24 subnet behind it can get thru .246 and > access > >the internet. Something in my configs just seems to be hosing the > ping > command > >for my external network on this box. > [...] > > > -- > ------------------------------------"Never tell me the odds!"--- > Ray Olszewski -- Han Solo > Palo Alto, CA [EMAIL PROTECTED] > ---------------------------------------------------------------- > > > _______________________________________________ > Leaf-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
