According to Jorge Matias: While burning my CPU.
> 
> On Thu, 22 Apr 1999, Richard Adams wrote:
> 
> > According to Jorge Matias: While burning my CPU.
> > > 
> > >   Hi all!
> > >   Do I need to configure /proc/sys/net/ax25/<iface>/t?_timeout files when
> > > I`m using AX.25 interface in datagram mode for TCP/IP connections only?
> > 
> > No, there for ax25 connections.
> > 
> > >   Why does the modem takes so long to transmit when I make a Ping, Telnet,
> > > Ftp, etc? It doesn`t tramsmit right after issuing the command.
> > 
> > Possably your system is trying to do a DNS lookup to resolve the hostname of
> > the target address, is there any difference in speed by doing ping
> > 44.xx.xx.xx in stead of ping ct1abc ??
> > 
> > A possable way around that is to add all known hosts to your /etc/hosts
> > file.
> 
> > -- 
> > Regards Richard.
> > [EMAIL PROTECTED]
> > 
> 
>   I don't have problems with DNS lookups because I have the machines in my
> /etc/hosts.
>   My configuration is:
>     Pentium 133MHz
>     YAM 9k6 (Serial) connected to COM2 (yamdrv v0.7 patched in the kernel)
>     Linux v2.0.36 (SlackWare 3.6)
>     AX25-Utils 2.1.42a
> 
>   The computer, most of the times, takes too long to transmit, even
> if I do "ping -i 5 44.158.xx.xx". I do pings with 5 seconds of interval
> to leave some bandwith available and time to get the answer from the
> other side.

Like GM7GOD said, if named is running the system will still insist on doing
a DNS lookup. That i did not think of when i wrote my reply, thanks Riley.
 
> 
>   Do you want to know the config in /proc/sys/net/ax25/yam/ ?

The default value's should not cause the problem you are having, so no i
dont thing there is a need to send them, they are for ax25 connections.

I always use Datagram mode and not VC.

>   By the way, the extra options of command "route" (mss, irtt, window) are
> to be used? How do I know what values I have to give? 

I use the following;

route add 44.137.28.27 mss 512 window 944 irtt 3000 scc3 
route add default gw 44.137.28.27 mss 512 window 944 irtt 4000 scc3

I think to obtain a decent value you could use ping, (if and when you solve
the waiting problem) 'ping -c3 -i5 -s216 <host>'
That will produce an "average" RTT.


The thing i would do to hunt down the problem is, kill things like named (if
running) make sure hosts are known in /etc/hosts start a listen session on
another console with the "-at" option and trace whats happening when you use
ping.

-a = show transmitted packets, 
-t = timestamp.

Of course i have no experiamnce with your modem or its driver, another shot
in the dark would be, are you sure its not a DCD problem.

>     
>   Thanks.
> 
> 
>   Regards,
> Jorge Matias
> 
> 
> - -- --- ------------------------------------------------- --- -- -
>   Computer Science Student at Instituto Superior Tecnico (Lisbon)  
>   A3000/060 32Mb -[Ariadne][MFC III][CV64]- LinuxOS 2.0.36 
>   QRZ: CT2HBZ  - E-Mail: [EMAIL PROTECTED] 
> 


-- 
Regards Richard.
[EMAIL PROTECTED]

Reply via email to