actually denote what the network topology could be #12

New issue

Open

opened 2024-09-09 06:45:37 +00:00 by fack · 3 comments

fack commented

2024-09-09 06:45:37 +00:00

Owner

ran into some showstopping issues w/ the idea to utilize ad-hoc networking on the intel 7265 chipset the chromebooks i'm using come with.

revising network topology is necessary.

Things to re-evaluate:

is batman-adv needed/wanted if we don't have any p2p meshing?
performance of other wireless systems (bluetooth PAN?)
consider other hardware (other wifi chipsets or entirely new platforms)

ran into some showstopping issues w/ the idea to utilize ad-hoc networking on the intel 7265 chipset the chromebooks i'm using come with. revising network topology is necessary. Things to re-evaluate: * is batman-adv needed/wanted if we don't have any p2p meshing? * performance of other wireless systems (bluetooth PAN?) * consider other hardware (other wifi chipsets *or* entirely new platforms)

fack commented

2024-09-09 06:59:31 +00:00

Author

Owner

While writing this issue I kinda thought of a new way to make use of the most "stock" hardware:

[ISP]>>>>[chrome**box** eth0]<>[chrome**box** wlan0])))))[chrome**book** wlan0]

This means I would be able to make use of the otherwise unused wireless cards on the chromeboxes.

the chromeboxes were going to function as access points for the chromebooks anyways, this makes that more intrinsic.

topology becomes much more standard while remaining just as useful (if not even more useful due to performance improvements of removing "relay" mesh nodes from the mix)

While writing this issue I kinda thought of a new way to make use of the most "stock" hardware: ``` [ISP]>>>>[chrome**box** eth0]<>[chrome**box** wlan0])))))[chrome**book** wlan0] ``` This means I would be able to make use of the otherwise unused wireless cards on the chromeboxes. the chromeboxes were going to function as access points for the chromebooks anyways, this makes that more intrinsic. topology becomes much more standard while remaining just as useful (if not even more useful due to performance improvements of removing "relay" mesh nodes from the mix)

fack commented

2024-09-12 03:28:13 +00:00

Author

Owner

Relates to:

Relates to: * https://git.cyberia.club/fack/rls/issues/14 * https://git.cyberia.club/fack/rls/issues/2 * https://git.cyberia.club/fack/rls/issues/7 * https://git.cyberia.club/fack/rls/issues/10

fack commented

2024-09-12 03:31:24 +00:00

Author

Owner

While writing this issue I kinda thought of a new way to make use of the most "stock" hardware:
[ISP]>>>>[chrome**box** eth0]<>[chrome**box** wlan0])))))[chrome**book** wlan0]
This means I would be able to make use of the otherwise unused wireless cards on the chromeboxes.

the chromeboxes were going to function as access points for the chromebooks anyways, this makes that more intrinsic.

topology becomes much more standard while remaining just as useful (if not even more useful due to performance improvements of removing "relay" mesh nodes from the mix)

An interesting property of this might be that the chromeboxes could function as PoPs on entirely separate networks.

> While writing this issue I kinda thought of a new way to make use of the most "stock" hardware: > > ``` > [ISP]>>>>[chrome**box** eth0]<>[chrome**box** wlan0])))))[chrome**book** wlan0] > ``` > > This means I would be able to make use of the otherwise unused wireless cards on the chromeboxes. > > the chromeboxes were going to function as access points for the chromebooks anyways, this makes that more intrinsic. > > topology becomes much more standard while remaining just as useful (if not even more useful due to performance improvements of removing "relay" mesh nodes from the mix) An interesting property of this might be that the chromeboxes could function as PoPs on entirely separate networks.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: fack/rls#12

No description provided.