PPP border router

Development archive
1

Hi again.

What do you think about using a PPP link between RIOT and a computer for border router stuffs?

It should be similar to ethos, but works directly with a ppp counterpart (pppd, for example).

The advantages of a PPP link are:

  • Easy to configure link and network parameters (MRU, IP’s, control characters, etc). This is done automatically by the PPP negotiation algorithm and it’s customizable.
  • As pppd runs at kernel level, there’s no need to set up a tap interface (in Mac OS X I think is not straightforward to set up one)
  • Can carry multiple protocols in same link (IPv4, IPv6, debugging data, etc)
  • It’s very stable (it has special packets for monitoring the link)
  • It’s standard and comes bundled in most OS.

The current implementation of gnrc_ppp is almost done (Link and network protocols are being negotiated).

Does it make sense? Cheers!

Jose

2

Hey,

What do you think about using a PPP link between RIOT and a computer for border router stuffs?

Does it make sense?

Totally, if the memory / code overhead is not too big.

Actually ethos uses basically PPP's framing.

When writing it, I skimmed the PPP RFC's and they seemed a little too - not-hackable-in-a-day, with quite some legacy stuff not needed in the ethos use case. But if there's already a perfectly working PPP implementation... :wink:

How much memory and code does it use?

Kaspar