> I have lived in France and now Hungary. I have never seen power lines
> above ground, but I have heard there are some in rural France.
You'll find them even in Budapest:
https://www.google.com/maps/@47.4720119,19.1245507,3a,75y,127.74h,82.44t/data=!3m6!1e1!3m4!1sWCy2Wa7XFx751XnTwI4ZEA!2e0!7i163
> What "all the ethernet control frame juju" might you be referring
> to? I don't recall Ethernet, in and of itself, just sending stuff back and
> forth.
I did not read the 100G Ethernet specs, but as far as I remember
FastEthernet (e.g. 100BASE-FX) uses 4B/5B coding on the line, borrowed
from FD
On Mon, Sep 12, 2016 at 04:08:08PM -0400, William Herrin wrote:
> On Mon, Sep 12, 2016 at 1:41 PM, Jean-Francois Mezei
> wrote:
> > To do so, it will provide ISPs with list of web sites to block
> >
> > Are there examples of an ISP getting sued because it redirected traffic
> > that should have go
> IPV6 connectivity to fireball.acr.fi is failing inside Cogent AS174. I
> have already contacted the Cogent NOC, but I haven't heard anything back
> yet. I'm wondering if somebody else with Cogent IPV6 connectivity can
> run some tests. IPV4 connectivity is working fine.
It works from AS2547
> It's that business deal I want to hear about. When A-B and B-C are
> free peering but the traffic goes A-B-C for some reason other than a
> misconfiguration or deliberate abuse. On or off list, I'd like to know
> about real-life use cases where folks do this on purpose.
As far as I understand so
> Second, in the hotspot scenarios where this is likely to be a problem
> (in IPv4 -or- IPv6) it's addressed by the "AP isolation" feature
> that's getting close to omnipresent even in the low end APs. With this
> feature enabled, stations are not allowed to talk to each other over
> the wlan; they
> > just a small comment: As far as I understand "AP isolation" doesn't work
> > if you don't have a WLAN controller but do have more than one APs. E.g. in
> > the following setup
> >
> > ap1--sw1--sw2--ap2
> >
> > with "AP isolation" turned on, clients associated to ap1 cannot
> > communicate dire
Ray,
> With a 60 second timeout on TIME_WAIT, local port identifiers are tied
> up from being used for new outgoing connections (in this case a proxy
> server). The default local port range on Linux can easily be
> adjusted; but even when bumped up to a range of 32K ports, the 60
> second timeou
> Well the requesting router could announce the route. ISC's client
> has hooks that allow this to be done. That is, after all, how
> routing is designed to work. The DHCP server usually is sitting
> in a data center on the other side of the country with zero ability
> to inject approptiate rout
9 matches
Mail list logo
