Re: No route to host -- first attempt. Second time works.

[Cathryn Mataga http://junglevision.com]

Hey, thanks!  That fixed it.

Richard Adams wrote:
> 
> >
> > I'm running axutils under Redhat 6.0, and things seem to be basically working.  
>(Though I
> > don't use any Netrom stuff.)
> >
> > Here's a slight oddity though.  When I type 'telnet w6yx.ampr.org' which is 1 hop 
>away
> > from here, the very first time, I"ll get 'no route to host' for the ip adress, 
>which is
> > correctly resolved.  Then, right away, I'll 'telnet w6yx.ampr.org' again, and it 
>works
> > fine.  I get in no problem.  How do I go about diagnosing this -- or figuring out 
>what's
> > happening.   Here's the setup for the soundmodem.  Also, right now I'm not really 
>sure what
> > 'window' and 'irtt' do -- and I just guessed at sensible numbers.
> >
> > /usr/sbin/sethdlc -p -i sm0 mode sbc:afsk1200 io 0x220 irq 5 dma 1 pario 0x378
> > /usr/sbin/sethdlc -i sm0 -a txd 200 slot 50 ppersist 128 half
> > /sbin/ifconfig sm0 hw ax25 KE6I-1 up
> > /sbin/ifconfig sm0 44.4.28.50 netmask 255.255.255.0 up
> > /sbin/ifconfig sm0 broadcast 44.4.255.255 mtu 512
> > /sbin/route add -net 44.4.0.0 netmask 255.255.240.0 window 128 irtt 2000 dev sm0
> > /sbin/route add -net 44.4.0.196 window 128 irtt 2000 dev sm0
> > /sbin/route add -net 44.0.0.0 netmask 255.0.0.0 gw 44.4.0.196
> >
> 
> The routing above is very confusing, w6yx.ampr.org = 44.4.0.196 so he is a
> "host" not a "net"
> 
> route add 44.4.0.196 window 128 irtt 2000 dev sm0
> would be more applicable i think. (See comment on wondowsize below)
> 
> You attach a route for 44.0.0.0 via sm0 as the first route, however after
> adding the bogus route to 44.4.0.196 you add a default route for 44.0.0.0
> again but now via 44.4.0.196 who at firstsight is a "net".
> 
> I would do the following.
> 
> ifconfig sm0 down  # clears routing.
> ifconfig sm0 up    # should use the old configured address etc.
> ifconfig sm0 braodcast 44.255.255.255
> route add 44.4.0.196 window 128 irtt 2000 dev sm0
> route add -net 44.0.0.0 netmask 255.0.0.0 gw 44.4.0.196 sm0
> 
> On another note you define a MTU of 512 which carries 472 bytes of data,
> you then configure a window size of 128 which is incompatable, a beter size
> would be 944 which is 2 packts every transmission.
> 
> If you are worried about transmitting and receiving Too large packets, then
> lower the MTU to 256 and set the window size to 216 thats one packet.
> 
> Now i hope i got my sums right.
> 
> --
> Regards Richard.
> [EMAIL PROTECTED]

-- 
http://junglevision.com