Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.networking > #1197

Re: Re (2+): ETHO interfacing linux IP:stack?

Cross-posted to 2 groups.

Show all headers | View raw

On 24.3.12 7:58 , no.top.post@gmail.com wrote:
> In article<jkfv56$8gb$1@dont-email.me>, Tauno Voipio<tauno.voipio@notused.fi.invalid>  wrote:
>
>> On 22.3.12 9:28 , no.top.post@gmail.com wrote:
>>> I'm writing this while I'm thinking it through, so I'll have a record.
>>> Duke mentioned the problem of email for LNO.
>>> I don't like LNO much, compared to LEO, which I use all the time.
>>> But LNO can run on a netbook using a framebuffer, without the
>>> full X-window system.
>>>
>>> So let's think this problem through.
>>> And correct my mistaken assumptions and conclusions:-
>>>
>>> N-O was originaly designed for RS232-modem,
>>> and the full<IP/TCP stack>   was in N-O [of course].
>>>
>>> So for<send string1 to IP/port>,
>>> all stages/levels, from the app's passing the string,
>>> down to the serial port driving the modem,
>>> was handled by N-O [of course].
>>>
>>> Under LEO, the underlying linux does the internet handling.
>>>
>>> Without anlysing the source code, I want to know how the
>>> N-O part of LEO interfaces with linux.
>>>
>>> Does the fact that "everything in *nix is a file" make this
>>> easy?
>>>
>>> Since linux, which previously drove a modem via a RS232,
>>> can easily be 'reconfigured' to drive a radio-modem via a
>>> USB; and passing the same byte-stream in both cases, I'm
>>> guessing that just the appropriate file-driver are needed.
>>>
>>> So the byte-stream is just fed to any character-type
>>> file-device, and the appropriate driver handles it.
>>> So the input-feeder need not be concerned what is
>>> receiving the input.
>>>
>>> If that is the case, and although the netbook has no actual
>>> RS232, if I create a /dev/tty0 [pseudo]file and [symbolicly]
>>> link it to the /dev/<existingUSB>   , which is connected to
>>> the remote IP:port via linux, could I communicate with the
>>> remote IP:port via LNO? Would LNO treat the /devtty0/
>>> as if it was a PC's "COM" port?
>>> I guess not, since during boot, linux would see that there
>>> is NO RS232-port and .....?
>>>
>>> If not, I suspect that facilities exist to easily connect into
>>> the IP:stack at various levels, and connecting at the highest
>>> level would be most convenient, via an Oberon<->   C
>>> interface ?
>>>
>>> Thanks for any ideas,
>>>
>>> == Chris Glur.
>>>
>>
>> Would you please make a glossary of the TLA's you used?
>>
>> TLA = three letter abbreviation
>>
> The names of the arguments are arbitrary.
> It's only the underlying concepts that matter.
> I.e. HOW2 connect the program that 'rides on linux',
> to the ppp layer.
>
> The more I try to 'translate' from the original text,
> the more I add distortion.



I'm pretty sure that you do not want to connect directly
to the PPP (packet transport) layer from an application program.

The electronic mail, as we know it in the Internet, runs on
the SMTP (and POP or IMAP) protocols. All of these protocols
are running on TCP stream transport. TCP uses IP for moving
the segments as IP packets. IP can use several different
protocols for moving the packets. Some of them are SLIP,
PPP and Ethernet (with ARP).

The stack looks like this:

   SMTP   POP    IMAP
          TCP
          IP
   SLIP   PPP   Ethernet
     Modem      Net cable

Helper protocols left out.

In Linux, the way to access the protocol stack is via the
C library, libc, using socket connections. There are
different kinds of sockets for connecting to different
layers of the stack.

My understanding of Oberon is that it contains interface
modules from Oberon code to the C library, which is the
native connection in Linux.

There are special interfaces, tunnel and ethertap, for
creating non-standard network interfaces at the network
or physical layer.

The question is:

What are you really attempting to achieve?

-- 

Tauno Voipio

Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

ETHO interfacing linux IP:stack? no.top.post@gmail.com - 2012-03-22 19:28 +0000
  Re: ETHO interfacing linux IP:stack? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2012-03-22 21:39 +0200
    Re: ETHO interfacing linux IP:stack? J G Miller <miller@yoyo.ORG> - 2012-03-22 20:07 +0000
      Re: ETHO interfacing linux IP:stack? Lew Pitcher <lpitcher@teksavvy.com> - 2012-03-22 16:27 -0400
        Re: ETHO interfacing linux IP:stack? Lew Pitcher <lpitcher@teksavvy.com> - 2012-03-22 16:44 -0400
        Re: ETHO interfacing linux IP:stack? Allodoxaphobia <knock_yourself_out@example.net> - 2012-03-23 02:43 +0000
      Re: ETHO interfacing linux IP:stack? Roger Blake <rogblake@iname.invalid> - 2012-03-22 21:12 +0000
    Re: ETHO interfacing linux IP:stack? "Chris Burrows" <cfbsoftware@hotmail.com> - 2012-03-23 19:10 +1030
    Re (2): ETHO interfacing linux IP:stack? no.top.post@gmail.com - 2012-03-23 23:21 +0000
    Re (2+): ETHO interfacing linux IP:stack? no.top.post@gmail.com - 2012-03-24 05:58 +0000
      Re: Re (2+): ETHO interfacing linux IP:stack? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2012-03-24 12:12 +0200
        Re (3) ETHO interfacing linux IP:stack? no.top.post@gmail.com - 2012-03-24 18:24 +0000
    Re (2+++): ETHO interfacing linux IP:stack? no.top.post@gmail.com - 2012-03-24 17:22 +0000
      Re: Re (2+++): ETHO interfacing linux IP:stack? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2012-03-25 15:17 +0300
        Re: Re (2+++): ETHO interfacing linux IP:stack? Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-03-25 12:31 +0000
        Re (2+++): ETHO interfacing linux IP:stack? no.top.post@gmail.com - 2012-03-25 14:26 +0000

csiph-web