Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow binding network cards to sides of microcontroller #788

Closed
magik6k opened this issue Jan 5, 2015 · 5 comments
Closed

Allow binding network cards to sides of microcontroller #788

magik6k opened this issue Jan 5, 2015 · 5 comments
Milestone

Comments

@magik6k
Copy link
Contributor

magik6k commented Jan 5, 2015

As microcontroller can fit multiple network cards, binding them to sides would allow creation of compact networking devices like routers.
The only thing I see, that requires a little discussion, is how the sides would be bound.

  • Through some kind of component API
  • Using GUI, like in server rack
  • Using some tool like wrench on sides to decide how is specific side connected, probably slightly changing textures
@Vexatos
Copy link
Contributor

Vexatos commented Jan 6, 2015

This should be specific to the Tier 2 Microcontroller.

@fnuecke
Copy link
Member

fnuecke commented Jan 11, 2015

Hmm, making this T2 specific might make T1 MCUs a little too special-case?

Maybe have both be sided, but the side for sending network messages be hardwired to the back in T1? (or all sides, actually... would still provide different enough functionality from both computers and T2).

@magik6k
Copy link
Contributor Author

magik6k commented Jan 11, 2015

Ohwait, from what you've wrote, you might have misunderstood what I intended. It was more like having 2 network cards in one uC and allow connecting of specific sides ot them(so one card could be conected to something like WAN port, and second one would provide LAN port(s)), not just binding send/recv functions to sides.

@fnuecke
Copy link
Member

fnuecke commented Jan 12, 2015

Ah, so you mean something like the side-assignment in server racks, but instead for servers for slots? Sortakinda? Or just have slot one be connected to up/back/down, slot two to left/right or something like that? (hardcoded)

@magik6k
Copy link
Contributor Author

magik6k commented Jan 12, 2015

Yep, Having it done in way server racks are done would be nice, but would require messing with additional guis, having it hardcoded would be still nice(like second slot connected to back and first slot to rest of sides. Also I dunno if It'd be possible but it'd be really nice if in this(hard-coded) case all sides but back were acting as one network node))

@fnuecke fnuecke added this to the v1.5.0 milestone Feb 2, 2015
@fnuecke fnuecke closed this as completed in edbfbe8 Feb 7, 2015
fnuecke added a commit that referenced this issue Feb 7, 2015
… network. Closes #788.

MCUs do not automatically forward network messages. They do not distribute power. Network messages arriving on all sides will always be forwarded to the MCU. Which sides are used for sending can be controlled via the `microcontroller` component. Further change: computers must now sit directly adjacent to MUCs to access their external component. Avoids the nasty hacks used in access points to avoid duplicate components if two sides are in the same network.

More cleanup, drones can be named now.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants