To have a short look on the agenda, some quick personal effects, I want to highlight the
handed as a mission statement of the handnet, because it's very important.
Give you a short introduction for a handnet in a nutshell, and we'll give you some ideas about
how a handnet has evolved, what the pitfalls have been, and what Dr. David for mitigation.
And I wanted to discuss a little bit about how a handnet can evolve further.
So some personal effects, so my name is Jan Toshewski, my course on a Statue of 18 November
by Koleff November.
I am licensed since 1997, getting old, obviously, and I'm the VHF Manager of the German
Emeterator Club, the DASC.
You may know, I'm a member of the German IP coordination team for handnet.
My colleagues are Eckberg, DD9QP, and Thomas, the online SAU.
So together, we run the IP allocations for handnet in Germany.
In the professionalist systems engineer at Schrodingschwarzen Munich, you may know that
we do some measurement devices quite expensive, but it's nice gear to have on the DASC
if you want to play with.
And my family, I have three boys, they are all now under 10 years old, so eating up
all of my time, but I finally made it at least to foster them.
And of course, I love Levi.
My location is to read November 590, but you'll get it's a Nürnberg.
OK, so handnet, the mission statement.
I think the mission statement is really important to understand what the project is about.
And if it is cash about, how can you do this?
Can you do that?
I always reflect, is this the right way in terms of the mission statement?
So the mission of the handnet is to build a maintainer European, or even larger,
let's see.
TSPIP-based radio only network for a moderator community, providing IPN to end connectivity.
So everybody knows, Nat is evil.
I don't know what the expression is coming from, but somebody created this.
And that's why we want to have these end-to-end communication.
Because you can do a lot of things if you're able to reach the wisest from one
and two at the other end without any strange nut in between.
So handnet in a nutshell.
So we're talking about a close community, unfortunately.
So we are talking about an emitter radio network where you need to have a license
to take part of it.
So we need to make sure that if you want to use the network,
you need to be a emitter radio operator.
And I think there are a lot of ways nowadays to get a license for this.
The RF backbone is on the six-centimeter band.
So it's like five gigahertz or like Wi-Fi gear.
And yeah, sometimes we have even for the backbone.
We are using other frequencies who come to that later.
The RF user access is typically on the third-centimeter band.
So two dot, three gigahertz and even on six-centimeter.
But you always need the line of sight, or typically you need it,
or you're very nearby to the sight in order to use that.
And as of today, we are using that infrastructure 90% of the time,
but for the end, users to be honest.
But we are using it for interconnection of amateur infrastructure,
like amateur repeaters and so on.
So this is the main thing.
And many people try to get a way how to get the local repeater connected
to the internet in order to, for example,
feeding APS information to the internet, I.S. stream.
So we offer, if you're suffering from that line of sight problem,
then we're offering a VPN access.
I will show this later on how to gain access to the network.
And most of the time, people are using this for service activity
of the repeaters or whatever you can find there.
So actually, we are using the IPv4 address space from the globally unique IP
space, 44128-10.
It has been formally 44-8, so very large,
but this even this portion of the network is large enough
for getting everything inside.
We are using the 16-bit and 32-bit private anonymous system numbers.
You can see the RFCs here for our internal BGP routing.
So all the network is using BGP only.
We have some new domains since last year,
we're using the domains here in the radio,
and the cloud in the dot network.
I will come to that what it is, and how we are going to use it.
And of course, there is really much potential for further project on the application layer.
And I'm really interested in that M17,
what we just heard about data communication.
Let's see whether this is somehow integrated.
So here you can see the hemat map,
or let's say part of the map, of course, you can scroll around the world,
but you will not find too much there.
You can see this is where we are dense on the German speaking area.
It's not wide known to non-German speaking area, unfortunately.
And this is maybe hopefully with this talk,
they're beginning to expand.
And this, the picture on the right inside,
you see a typical hemat installation.
And the funny point is that I gave the exactly a talk 10 or 11 years
ago in the US using the same picture, because it didn't change too much.
So we have for the user access, we have small devices,
which are covering different directions,
nauseous, nauseous, is rest, with 90 degrees beams,
so that you can easily access the hemat site.
And below you see the interlinks.
So they have a very narrow bound beam,
so that they can point to other handed infrastructure
to have a good link.
Yeah, on the left side you can see the UL for our platform.
If you go to hamnatdb.net and click here on the map,
this map will open, you can scroll in, you can zoom in,
you can do a lot of tools inside,
and you can play around with that.
So what is the amazing thing?
The amazing part, there are people trying to ask,
what can I do with it?
It's not me.
I'm only interested in building up the infrastructure,
and there are many people really trying to build up
that RF only infrastructure for our ematerial infrastructure,
and we don't care about what is going on on the network.
So we are really focusing on building up the network
and thinking in layers, say, okay, look,
you have now here a nice network, use it.
I'm not interested what you're doing,
but you can do it.
So this is really satisfying to me.
You can see here a trace route from the southern part
of Germany going from here over Austria,
and then even up to the Norse coast or east coast of the Norse.
Yeah.
And as you can see, we have 28 hops,
and can down up down to 85 milliseconds.
Yeah, around trip time.
So this is what amazes me,
and there are even plenty of other users
or administrators who like to build up the network,
and just see, okay, trace route is working.
Now we have a new link.
Now we can interconnect,
there we don't need to have internet anymore.
For example, you see a little bit that problem here,
that bit is Berlin, and still there are two last people
interested or two last nice sites
to connect Berlin to our main network.
So actually, we're using a VPN,
and if I'm talking about radio,
I'm talking about the radio layer,
which is really important.
I'm talking about this,
the project to connect everything by radio.
But of course, we have some islands
which we need to connect by VPNs.
I want to talk a little bit about the involvement,
so my personal case, who has been in 2009,
locally, repeater has been connected
from the university to the GV Tower in November,
spectrum is crowded, 2.4 gigahertz,
you can imagine 4 kilometers,
it's quite too bad to operate.
So the question was,
can we use the 5 giga emitter spectrum with some more power
to interconnect to this side,
because our NPTEL is hosted there?
And can't we use our global unique IP space,
44th or 8, rather than VRC-1980 IP space,
like 19268 and so on?
And it turned out, yes, of course, we can.
So the National Regulator approved our application
for the 5 gigahertz channel.
We have only 10 gigahertz channel bandwidth and Germany allowed.
We started with 15 watts of ERP nowadays.
We can run up to 1 kilowatt ERP.
After talking to military because they are primary uses
in that band.
Of course, we switched them to network 44.
IP space and promoted to do the same in other regions
in Germany.
So the idea was that everybody is building up their stuff
in that unique IP space, so we can grow over time together
and we don't need to re-number anything.
That was at least the idea.
So yeah.
And of course, the Internet disconnected regions
we have been connected by VPNs.
Yeah, some pitfalls, let's say.
So pitching versus routing.
In Austria, there started some a little bit with a large ring,
which is on layer two.
But the problem was on layer two.
If you build a wireless link over many hops,
you have really problems to debug if things go wrong.
So if you want to find out which, exactly,
which link breaks from a user perspective,
you're not able to do that.
You need to have some interfaces.
And that's why we switched over to normal layer three
or IP hops transfer networks to solve that issue.
So if you do a threshold from anywhere on the network,
you can see each single rate you hop.
And if things fail, you can see when it broke and tell,
hey, you guys, here's something wrong.
You need to check what's going on in your network.
Yeah.
So other best practices that we have are whole prefix
for the whole side.
If you talk about the hand inside,
we have a site on a high building or high mountain.
And we want to keep the routing tables small.
So that's why we have one IP prefix for one site.
And you split it internally in trustful, not trustful devices.
So some of these devices are allowed to talk to the internet
for example, local devices you have there.
Or if you want to offer radio access,
then you may think about, well, this is not a good idea
to have access to the internet.
OK, let's go to the routing protocols.
We played a little bit.
So the idea was that our IP allocation team said,
this region can play with that routing protocol.
You can do whatever you want.
But over time, as I've seen,
that the regions were built together.
And then the first link between the regions came up.
And then how do we interconnect this now?
And so we need to do, yeah, we need to change the routing
protocol on the borders.
And the problem is, really, that you need to interact
with every operator in a region to change things,
if the topology changes on the network.
And this was really annoying.
And yeah, because if you talk to every one
and you know people are people, and it's always
hard to get everybody on the same page and to understand
or you know you need to change the configuration,
this was really a bad lesson.
So the lesson here is we need to find a routing protocol,
which is considering every single side
as an absolutely independent side.
And that's where EBGP has been chosen.
So we were really thinking about it
because EBGP is not the best way to do that.
But finally, it turned out the pros are better
than at the cons or the arguments to use this as higher.
So we have there a 32-bit private A's end range.
I mean, after six, nine, and six.
So we have plenty of sides, which we coupled in the hand
that right now.
So 9 million will be, oh, is it 9 million?
Yeah, 94 million.
OK.
So we have plenty of time to do that.
So yeah, everything is side is fully independent.
So we don't have any problems with the topology change.
And only the direct, if you build up new links,
then only the operators directly concerned with the new link
will need to interact with the configuration.
But the cons is that we cannot row back this decision.
The routing protocol does only know 0 or 1.
So it doesn't matter if you have a weak radio link,
then you have a weak radio link.
And if it's too bad, and they are alternative links,
available, then it's not good to keep it running.
So you really need to have a threshold where the link can be
considered as a really good properly working link.
And then you can keep it running, otherwise
you need to turn it off, because it will disturb the whole
transit on that one.
And of course, the question is, does it scale?
Because I have never seen so long AS hops in the internet
to be honest.
So if you try to get around the internet on the back bone
of the internet, we'll not see that long AS pass, usually.
So of course, it's maybe limited on 255, I don't know.
But yeah.
So up to now, we don't see any issues in this daily
operation.
It works quite well.
For example, there's a hand inside, a hand inside
is a part of the RF backbone.
And it's usually running more, one of multiple RF links
on the network.
And yes, it can offer some services to you, like
webcams, was a piece of whatever.
And may offer our user access.
This is not typical hand inside.
And what is the hand?
Users can connect to the hand it.
Using that hand inside, it has radio gear pointed
to the hand inside and get an IP address by DHCP
protocol.
Yeah, some people like to have static IP.
So just call the operator of their tenant site and say,
hey, I'm new to you.
Here's my megator.
Please give me a static IP here on the network.
And of course, if you don't have line of size to a hand
inside, then you need to make use of the hand that we
pay in service.
Yes.
Well, this is a site in the central Germany.
It's called the broken DBZHEX.
And you can see here the adjacent channel
interference problems.
So if you have a lot of transmitters nearby,
and you're like, like on a repeater,
you cannot have a repeater without any filters.
That's why, for example, we changed this antenna here,
because the feet will have the other antennas around,
even this one is changed now.
This has an RF shield right around the feet.
So that's isolated against each other and to have, yeah.
This is a really challenging task to get this really
working.
So how can this be mitigated?
You can do a frequency separation.
Of course, we have limited spectrum.
So we have 200 max of bandwidth and the 60-meter band
depending on the country.
You can use the whole 200 max, sometimes not.
You can, of course, reduce the power.
Usually you're interested in high speeds.
So you look on a regular link that you
reach the full modulation coding scheme in order
to have the full capacity available.
But if you're even above that enough margin
that you can reduce the power, you
then take back the power to avoid these issues.
Or you use higher gain antennas.
I know that many people on these sides
have problems to install larger dishes,
because the site owner say, well, it's got in large.
It's got in huge.
This is all for free for you, so don't use too much antennas.
And yeah, sometimes physical separation is good.
But as you have seen, this is a redone.
And there's really hard to physically separate these things.
OK.
So yeah, as I said, the impact on the hand it is very large.
If you have this turped link, because if you have such a high
side and very good connected to hand it side,
and traffic is passing through, then the beach
is quite comfortable with that.
It's telling the network, well, I'm a running link.
But if soon as you put data on that,
then you will have a problem because of other transmitters
on the same side.
So even if on large packages like if you want
to have a real stream or large content, large data
with M to U of 1500, you really run into issues
because of the packets get chunked and then you need
to take care.
So please, if you have a problem like this,
either explore the situation or sometimes
it's even better to just don't establish that link.
The capacity of that side is full.
You have seen maybe on the map.
Here is even some purple and some blue lines.
And we don't even only use the amateur radio spectrum.
We are making even use of other spectrum
like public Wi-Fi stuff.
And even 60 gigahertz equipment is quite nice nowadays
to have high speed links or to, let's say,
to interconnect links where you have these interference issues.
For example, if you have only four or five kilometers
long on such a high side, then just use some public Wi-Fi
frequencies and make the configuration
or make the established link.
Net neutrality issues.
So what we see very often is that on these B2P routers,
it usually should act like a normal transit provider,
but since everybody is learning how from scratch
and the administrators don't want to just apply something
that they want to learn, they want to, yeah,
this is the whole part of it to learn how things are working.
And sometimes they just didn't plan
the standard configuration and then some nuts rules
are still in the transit and it's really hard to track down
if you have in the transit a nutting router in between.
Or if the firewall has some modes for only established
and related, there's a situation
that we have asynchronous routing so that the package
going forward is going another route
than the package going back was.
So that's creating issues on some firewalls.
If there shouldn't be a firewall at all,
at least in the backbone.
So there were even some problems in the beginning
that we have uncoordinated VPNs
in between the sites, which is really bad
because if you look on the map and you make a link
between hamburger and Munich, you can transfer everything
by radio, but this is not going to be used anymore
because of the VPN tunnel.
So we needed to interact and to, well,
this is a radio project.
We don't want to tunnel everything here.
And so, and this was a problem in the beginning,
but nowadays, it's not a problem.
Everybody accepted at least in the SSL,
in the German-speaking area, it's quite common
that we don't have any issues anymore.
Yeah, so now we come to a very interesting point
that we have handed back bone capacity issues.
Yeah, from the internet, usually the use of the internet
thinks, oh, I have, my DSL has 50 megabits up and down,
or let's say, up, down, 50 megabits.
Why can't I see it on the handnet?
So they don't understand that it's not being in the handnet.
There is a backbone infrastructure behind,
and if you want to have some data from handbook
and you're setting a Munich, it takes time.
It must cross all these back bones.
It's not like on the internet, you click on it,
and it's there.
It's really neat and sand, what are you doing here?
And what in the early days came up here
is that a lot of VPN popped up in some regions,
because people want to be nearby the infrastructure
and locked by VPN into that network.
The issue is here that if you have a lot of,
and somebody says, hey, look, I have a new video stream in Munich,
and people from Hamburg logging into a VPN provider in Hamburg,
and they want to get all these data from Munich.
So the question was, how can we free up the artifact
on in terms of capacity by using so-called dual-homed handnet sites?
We have one lag in the handnet and the other lag in the internet.
So the hand cloud here has been born.
What you can see here now is really a cloud infrastructure.
You don't need to know much about the cloud inside.
They show a little bit, but inside the cloud,
it's more or less on the map.
You have these blue icons.
I have made them a little bit larger,
so you can see them better.
They have these dual-homed handnet sites,
and they all maintain a VPN connection
to this cloud service.
And the key is now that the whole infrastructure,
or the whole topology, the routing,
will be transferred by VPN to this cloud.
So this cloud always knows the best and fastest pass
inside of the handnet.
Everything is living in here.
And this is the prefix we actually using.
So everything inside that prefix or inside that network
is making use of that technology.
So we have run about 70 or 80 dual-homed systems in handnet.
So as soon as you lock in here by the VPN user,
by the way, this is the URL if you want to join.
There are two ways I will show that later.
So just click on it and you can see
how you can join in the handnet on VPN
if you don't have radio with you.
And even we have some basic services.
But of course, this is not the main mission.
Again, about the mission, the mission is to build a radio network.
But this project is only there to get rid of all these data,
which is going to be passed on the RF,
which we don't want to have there.
So the idea is to get data which is supposed to go to the internet
or coming from the internet on the quickest way out of the network.
Yeah.
So yeah, this is maybe what I just explained.
Import or write from handnet.
Yeah, export or write this, that prefix will not be.
The internet handed into routing will not be influenced.
This was the important part.
And yeah, a shorter pass.
And I think it's from the best connectivity.
Yeah, got it.
And this is, yeah, this is what you can see here.
Of course, it's not a single, a single system.
It is a system out of three.
I think one in Berlin, one in Aachen, and one in Duysburg,
which is interconnecting by other VPN tons, which is OSPF.
And so on.
So forget about that.
This is not really important.
It just works.
Yeah, in that case.
OK.
So yeah, some key factors in general about SSL.
It's a community project.
So you need to find people contributing.
And to get people on board, one of the principles we
have seen is really worse to look at is keep it simple, stupid.
The complex system, the more problems you will generate here.
Make things transparent.
Make a clear policy that people can understand.
And give the power to the user so that they can select
how to route your traffic.
So that you have to have the power to decide
that I want to use the radio, even if the radio is bad.
And since we have now the new domains,
we are trying to reflect this ideas into the main names
so that you can select better how to use the resources.
Yeah, just a quick overview.
So we have some services on the same cloud.
So the network is everything we do on the internet.
So there's a link where you can see, unfortunately,
still in German, so things are to do.
So there are some services running on it.
And yeah.
So the connection from the hemids to the hemplot
is available to many VPN tunnels, as we said.
It doesn't matter if the current VPN tunnel will fail,
because the new route, the new route will just take other RF
tops.
So this is the beauty.
So if you contribute on the network,
your service is getting much more stable,
because if your local internet connection will break,
or your local VPN tunnel to the hemplot will break,
the system will automatically reroute
to the nearest way to the same cloud thing.
Yeah.
So we get redundancy.
Yeah, what else is possible on the hand-to-backbone?
Well, it's an IP network.
It can transport almost everything from HP and vice versa.
Be just creative.
It's just some examples.
In the hembrated frame, which is often
we usually show a two and a half megabits
we just stream from DBZVHPS, which is almost 1000 kilometers
if you count all the hops, lengths together.
And it's fluent, usually.
We provide access to web SDRs from the Alps
and during that fair, or through a radio.
Yeah, some regions that are interconnected
all of their FM repeaters by that network.
This is quite nice.
And some regions run MCOM services on it,
like they're even some projects where you have
from the government, get some funding
for making hardening the hand-to-site
in terms of power outages.
There's something to play, like, voiceover,
a piece of stuff inside the hand-to-pump pump.
So yeah, this is what we present in three to a half, usually.
So you can see the optical fuel on the right bottom side
and the hole of the fair on the left side and the parcel
the network.
Same here for the radio stream.
Yeah.
So this is the concentration, I have 50 minutes, so and good.
We have the future revolvement of the timets.
What you can see here now is, can you see what this is?
I remember.
It's Europe.
Yeah, it's broken, yeah, I know.
But this shows Europe in the late 90s.
This is a map.
There was some guy in Slovakia trying to get what
we formally built in Picard Radio.
And I can remember the times when I was young
that I was able to sit in front of the PC,
you remember that even internet was not there yet.
Oh, well, not papity here, there.
So sitting in front of the PC and trying to go down
to Spain through the network.
This was really a beauty to go through it and have fun.
And you can see the speed.
Well, it's better than I'm 17, isn't it?
It's not.
I apologize.
But I'm looking forward to it to integrate maybe something.
And the question is, yes, on 23 centimeter,
you don't need that line of sight.
You don't have that line of sight requirement.
But even if you have good sight, I have a one link
on 217 kilometers with minus 60 dBm and 50 megabits,
both directions.
So it's only a matter.
Can you see each other?
The question is, can we grow that large?
So what do we need for further expansion?
Of course, we need the sights.
This is all the important thing.
We need the sights where we can climb on top of mountain
and put some stuff there.
You need to have some buildings, high buildings where
you are allowed to put some large dishes on it,
or even smaller dishes.
It really depends.
We need some tools.
We have some nice propagation tool in the hand of database,
so you click on it, and you can quickly
draw whether I have a line of sight between two sides.
We have ready for another.com.
We'll see that later, and of course,
you need to have the IP resources, but this is all solved.
So for example, I can do it even live,
but time is running.
So yeah, okay, I do it live.
Someone was laughing, so that's challenging.
Where are we?
So this is Brussels here on the left hand side.
This is Arhan from, let's say, go to this side.
It's not too, and it.
So you can see, so you can easily check,
check whether you have a line of sight
and even make a larger profile out of it.
And forget about the tree.
There are some measures you can take about the trees, yeah?
All right.
So it's really quick where you can check that.
About the IP resources, AS numbers,
and how to get an ended up length,
if you need it by radio, VPN connections,
please just contact me.
I'm available on the email address,
and even on my course line is available
on all the messages out there.
And there's even some quick stuff thing.
So we thought about, okay, we have country allocations,
but nowadays we even have some,
let's say, global hand-to-project allocations.
So we can simply allocate in a very easy scheme resource,
so that you can immediately start
if you have good sites and want to contribute on the network.
Yeah, and these are the two uplink providers,
calls for getting a hand net islands into the network.
Applications.
I have a personal backlog.
So just imagine that in this hemp cloud thing,
I have a CIPServer providing a CIPServer for phones,
which you can connect on your radio.
And if you have two CIPS clients,
and I connect for usually know that these phones
have one to three direct CIPS clients,
where you can just click on that, which line to use.
And it would be nice to have one line for peer-to-peer mode,
so that you have the directory service,
like the voice of a piece of indie hemp cloud.
So you just using it for getting the information,
which IP address has your partner, your own a call,
or your device should call.
And if you do that, then we can easily
and quickly phone to each other either by radio only,
if possible.
And you can compare it afterwards.
If you do the second supply, where the server is forcing
that all the audio stream is not going past directly,
but over the hemp cloud, on the VPN tunnel.
So this is actually one of the projects
which I'm trying to do in 2025.
And of course, I have a lot of other further ideas,
but as you can see, I hide them because of personal overload here.
And of course, what are you at the DSC?
I'm looking for inputs.
So about RF access.
I told you that line-of-sight is always necessary.
Unfortunately, there are not too many solutions out there
how to get around this.
So we have on the 23 centimeter band, 60 max,
still, even with scaleneo issues.
So let's see how much we can still keep.
But we could use standard RF, I guarantee,
have transferred us to mix down a 5m chunk
in order to use the 23 centimeter band.
Or you have heard about this new packet radius project,
maybe, and there's a solution for 70 centimeter.
And soon, there will be something for 23 centimeter.
This can be used.
But it depends on our technology, how good it is.
We have another project.
We're running GSM, or GPRS, on 70 centimeter,
thanks to Eric Osmocom.
There's an implementation now available
where you can build up a GSM system on home radio frequencies.
And yes, of course, if we want to have speed,
we need to have multi-slots implemented in action on.
But of course, you always need to have some room
for improvement.
And some satellite things.
We have the Q100 Transponder in there,
there's one project from the same guy who's doing this NPR thing.
And I think Daniel, your system is even described here.
And I'm really interested in whether this can be turned out
to a permanent solution, maybe.
I have good context to the M-set people and maybe a good site,
good spot where we can get the data into the handled network.
And of course, we have some spectrum available
in the Tengik band, which I would like to use,
because I fear that if we don't use it, we lose it.
We can see that all the commercials are eating up
over our frequencies.
So I want to use the Tengik help span.
We have two links on Tengik help.
We're making use of 160 max spentwas.
There's plenty of pentwas available, 500 max,
but the gear is very expensive right now.
So we actually pay two k for one end, plus antenna.
So this is not easy to do.
But of course, the same thing applies,
like if we have transmetors and go from standard Wi-Fi gear
up to 10 gigs, this would be a beauty.
Yeah, other stuff to explore.
We could even look about the terahats, so laser links.
They are high speed, of course.
As you know, that space exists playing around in space
with that.
Of course, they don't have any archie in,
or some other molecules, as they're facing the Earth.
So of course, we know that laser links are suffering
from fork, but we don't have any service-level equipment,
don't do we.
So even if you just reach 90% and this is good in our case,
the commercial, you can forget about that.
But this makes me think about why not using laser links
on a terrestrial level.
And the feedback can, if fork is there,
and we use the existing in five weeks infrastructure
as a backup.
Playing a little bit about with LTE,
there's a time division duplex band.
It's called B40.
On the surgery centimeter band,
so 2,300 to 2,400, it's overlapping with the M2 radio
allocation.
And we're actually looking for an X&B for a 40T radio.
If you have some context, let me know.
And some pure software implementation could be
from SRS.
SRS around project, so that we can maybe even start with 5G.
But yeah, there are a lot of, well, of course,
it's talking to your phone.
So the distance would not be solved, the distance issues.
And we can play with open Wi-Fi, if you have seen that.
And I think this was the last slide I have five minutes left.
APPLAUSE
Thank you.
So any questions, please?
Yeah, but for over Wi-Fi, you might as a misplug the mega wide,
so it will fit exactly 70% of the time.
Well, there are quarter and half rate and quarter rate chips.
So there are even some chips,
which could go down to 2.5 max.
There are terrorist chipsets, 600, 600, blah, blah, blah.
So there are some projects where you can narrow it.
And it's standard is 10 max and 5 max.
On the 80, 11, a X, it's not available anymore.
But if you have some oligas, you can just tell the radio
to go down to 5 max.
OK.
Another question.
Another question?
I have a question.
How have you got the tune that needs to be time hours
or enable the directional hardware detection
or something like this, the noise that the whole thing has.
Well, of course, we actually, I said, keep it simple stupid.
So the idea is always, if you have a sitting in front of a configuration,
I will have a look at the configuration.
The configuration is good if you don't touch it as much as possible.
So there's BFD, as I have heard.
And we can play with that.
We didn't investigate so far because we're concentrating on the mission.
So that's why we didn't look at this too much.
But yes, if a link is getting weak,
we would like to see it more faster than the three minutes
limit, I think, which actually is BFD standards.
Yeah, but the thing is, to make a large change
and you don't have full control of network,
means that, well, can you change it?
Can you change it?
So it takes time until we will decision the propagates
through the whole network.
There was another question?
Yeah, please.
Maybe something you might be interested in is, of course,
especially point points in and over a Q100.
We did some testing with a hand from Savakya on the custom protocol
for any over QPSK.
And so we reached a few megabits per second
with a custom protocol.
And so that could be used instead of,
is it somehow broad on the ULA available where
can we talk about it or, yeah, I can send you a link.
OK, great.
So I can edit later.
Thank you very much.
The other question for the, from the matrix channel,
are you so is asking you what about IPBs?
Yes, I was waiting for this question.
OK.
Again, the thing is, I am really concentrating on the mission.
I know that we are trying to solve a problem
which we actually don't have.
Yeah, well, slash 10 is really hard to deplete.
Well, it depends on you.
Yeah, of course, if you're far from.
But yes, we have looked at it.
We were thinking about some ways how to do that.
I think even though you had a proposal written,
it's just not my project.
So you're absolutely invited.
It's a community thing.
If it's low, low effort for me to take part on your idea,
feel free to contact us and to push things.
Of course, if you want to have a large IPv6
prefix, that's just the other thing.
If you want to have the large one, you need to coordinate
in a worldwide system.
And to really have everyone in the world to accept that,
if you come and say, hey, I have a slash 40 for the whole world,
then whoa, am I slash 40 is even better?
So they have accepted the same problem.
So you need to have a slash 24 or something
in order to get it approved by the emincerator community
to have a single IPv6 prefix.
There are other ideas like, from Daniel there,
where you have a list of chunks where you have these
prefixes just collected and say, this is belonging to emincer
or not.
So there are many ways around how to do that.
But yeah, again, it's not the mission, it's not my mission, actually.
Further questions?
Well, I have 30 seconds.
Yes, please.
So it's very advanced, like, then for the half of the board,
like, you know, I mean, another of nodes
and he comes to you, it's something like more real work.
Then can you look at this being, like,
starting, like, a full work Internet,
just in case something would happen to the world.
Yes.
It is absolutely a system which can be used for emergency communication
and we're even getting support, as I said,
from the government.
They're even some projects inside and Germany,
where you have, let's say, all these m-com guys
trying to get in touch and even to collaborate somehow.
Of course, it's a bit a little bit tricky
about the emincerator regulations, but technical, yes.
And you can adapt even regulations, if necessary.
Okay, thank you very much again.
Thank you.