laraqui@SICS.SE (Hakiml Laraqui) (06/27/90)
First, I don't think you would want to use a gateway above TCP since this would be inefficient (you don't use transport protocols in gateways no matter what, according to some, or unless you absolutely have to according to others). Second, ISODE is very modular and hence easily expandable. Adding a new X25 interface shouldn't be to much of a problem. Adding a new TCP interface over packet radio (amprnet) to ISODE wasn't to difficult (as an example). Kim Laraqui, Swedish Telecom Radio
harald.alvestrand@elab-runit.sintef.no (07/06/90)
Well....I did make a gateway-based approach....
the 3 x.25 layers present in ISODE 5.0 were all using some kind of sockets,
all with their own bugs and weird ioctls.
the X.25 I worked with was Symicron's, which shows strong traces of having
come from the PC world, where one connection is a lot....
Anyway, what I did was to make a new x.25 layer based on an existing one
(as recommended), and to get one single application, the tp0bridge, working
with this x.25 layer.
The hacks involved were nauseating (how about one data-shuffling UNIX process
for EACH DIRECTION ON EACH CONNECTION!), but it worked, and with acceptable
performance for my application.
So, sometimes a bridge works....as a side effect, I got the possibility of
using the X.25 card in a single PC for transport connections from many.
Nice try!
- Harald A
patcher of what I have to