Re: lwIP on SLIP interface

[Sergei Gavrikov <sergei dot gavrikov at gmail dot com>]

On Sun, Mar 15, 2009 at 05:05:06PM +0200, Sergei Gavrikov wrote:
> On Sat, Mar 14, 2009 at 06:53:23PM +0200, Sergei Gavrikov wrote:
> > On Sat, Mar 14, 2009 at 06:05:31PM +0200, Sergei Gavrikov wrote:
> > > On Sat, Mar 14, 2009 at 09:46:46AM -0600, Gary Thomas wrote:
> > > > Sergei Gavrikov wrote:
> > > > > Hi
> > > > > 
> > > > > A few days ago I needed to run lwIP on sl0. I ran into two problems. It
> > > > > seemed for me what a medice can be interesting. Please, look at the
> > > > > http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000717 for details.
> > > > 
> > > > is it working with these changes?
> > > 
> > > It works with my tweaks the slipif.c and sio.c. I attach minimal ecm
> > > what I use on olpce2294 here.
> > 
> > Garry, I would want tojthat another person test it on another platform.
> > Perhaps, I must investigate a bit more time to be sure that tweaks do
> > not break PPP stuff. I did not test eCos lwIP PPP with and without the
> > tweaks. I will do it and then report about.
> 
> It was surprise for me that I could not build PPP with CYGDBG_LWIP_DEBUG:
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000719
> 
> Then I built it. It ran, my tweaks no break input. I'm sorry, I have no
> time this sunday to set up host side PPP things. Instead, I write a memo
> what I done _exactly_ when I tested SLIP. Perhaps, the next weekend,

If you read that memo until the end. It seems for me that I can finish
the story on a major note.

I thought about TTL for P-t-P connection. Let's look on TTL as on hops
= hosts. Why 255 in my case? I limited the the default TTL values:

cdl_option CYGNUM_LWIP_TCP_TTL {
    user_value 16
};

cdl_option CYGNUM_LWIP_ICMP_TTL {
    user_value 16
};

cdl_option CYGNUM_LWIP_UDP_TTL {
    user_value 16
};

Rebuild test and and run _simultaneously_ three things:

1st) adaptive ping

ping -A 192.168.1.222

2nd) echo with a timeout

while [ 1 ];do echo `date +%s`|socat - tcp4:192.168.1.222:7;sleep 1;done

3rd) echo without timeout

while [ 1 ];do echo `date +%s`|socat - tcp4:192.168.1.222:7;done

Even if I run that killer as fourth task

4th) yes|socat - tcp4:192.168.1.222:7

I did continue to see the replies from the ping! When I killed 'yes'
killer, then echoing awaked.

Sergei