Hi,
On Mon, Feb 23, 2015 at 12:42:47PM -0800, Toerless Eckert wrote:
Q: Did i hear it correctly, there is no standard show mac-address-table like
CLI on linux/openwrt for built-in switches ?
Right. Usually communication to these built-in switches is limited due
to lack of documentation, lack
On Fri, Feb 20, 2015 at 8:56 AM, Teco Boot t...@inf-net.nl wrote:
Bad luck, I kindly ask you to pay a little more attention to it. Link metrics
for wireless links are crucial, but let's not forget wired links.
Some years ago, Thales NLD worked on olsr-lc (link costs, ETT). A plugin
probed
Op 20 feb. 2015, om 09:54 heeft Henning Rogge hro...@gmail.com het volgende
geschreven:
On Fri, Feb 20, 2015 at 9:51 AM, Teco Boot t...@inf-net.nl wrote:
At the moment I just get the ethernet port link speed... that is not
really good for switched ports, but its better than nothing.
On Fri, Feb 20, 2015 at 9:19 AM, Teco Boot t...@inf-net.nl wrote:
There is also the linklayer database approach I selected for my
olsrd2 implementation. Instead of hardcoding linklayer specific code
into the metric, I split the codebase into link layer gathering code
(which is often OS and
Op 20 feb. 2015, om 09:22 heeft Henning Rogge hro...@gmail.com het volgende
geschreven:
On Fri, Feb 20, 2015 at 9:19 AM, Teco Boot t...@inf-net.nl wrote:
There is also the linklayer database approach I selected for my
olsrd2 implementation. Instead of hardcoding linklayer specific code
On Fri, Feb 20, 2015 at 9:51 AM, Teco Boot t...@inf-net.nl wrote:
At the moment I just get the ethernet port link speed... that is not
really good for switched ports, but its better than nothing.
So what I want to see is a proposal for a routing protocol that specify link
metrics for a set of commonly used link types in homes. This spec could be
BCP.
Does it need to be a routing protocol? Just to throw another possible protocol
into the mix being tossed around (like we don't have
Op 20 feb. 2015, om 15:55 heeft STARK, BARBARA H bs7...@att.com het
volgende geschreven:
So what I want to see is a proposal for a routing protocol that specify link
metrics for a set of commonly used link types in homes. This spec could be
BCP.
Does it need to be a routing protocol?
If you have hardware with a built-in switch that can report the link-speed,
The WNDR3700v2 under OpenWRT appears to do so:
# swconfig dev switch0 show | grep 'link:'
link: port:0 link:down
link: port:1 link:down
link: port:2 link:up speed:100baseT full-duplex
link: port:3
Does it need to be a routing protocol? Just to throw another possible
protocol into the mix being tossed around (like we don't have enough),
I don't think current protocols used by ISPs or enterprises fits our plugplay
requirements. Also, there is a lot more wireless in homes. That doesn't
A marginal link is simply one that has a measurable amount of packet loss.
Ok, re-reading this exchange, it looks like I may have wrongly assumed
that people are aware of background. I'll need to put that into the
routing comparison document, this is as good a place as any to draft my
text.
On Thu, Feb 19, 2015 at 11:45 AM, Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr wrote:
A marginal link is simply one that has a measurable amount of packet loss.
Ok, re-reading this exchange, it looks like I may have wrongly assumed
that people are aware of background. I'll need to put
Op 19 feb. 2015, om 22:01 heeft Dave Taht dave.t...@gmail.com het volgende
geschreven:
1. Prefer solid links
This is pretty obvious. If you can choose between an Ethernet link and
Well, ethernet runs at different speeds and there is no abstraction
for that in babel...
Why not?
I
On Feb 19, 2015, at 5:23 PM, Teco Boot t...@inf-net.nl wrote:
After having selected the Homenet Routing Protocol, I expect some discussion
on how to set the metric. If box A from vendor A sets cost=100 on 1GE links
and another box B from vendor B sets cost=50 on 2Mbit/sec WiFi links, we
Well, ethernet runs at different speeds and there is no abstraction
for that in babel...
Why not?
Switches.
Most home routers have their (on-chip) Ethernet interface behind an
internal switch. That is how they provide 5 or more Ethernet ports using
a single-NIC SoC.
That has the
Op 19 feb. 2015, om 23:42 heeft Juliusz Chroboczek
j...@pps.univ-paris-diderot.fr het volgende geschreven:
Well, ethernet runs at different speeds and there is no abstraction
for that in babel...
Why not?
Switches.
Most home routers have their (on-chip) Ethernet interface behind
16 matches
Mail list logo