Le 2014-03-13 15:12, Eric Vyncke (evyncke) a écrit :
> What annoys me more if the fact that AVM (and they are not the only one --
> see Technicolor & others) naively believes that NAT44 offered some
> security by preventing inbound connections... This means that there is NO
> open connectivity betw
Postfix + Spamassassin
Le 2014-02-05 10:59, Bill Owens a écrit :
> It appears they haven't worked for some time, at least on Firefox:
> https://bugzilla.mozilla.org/show_bug.cgi?id=700999
Thanks for the pointer. I added my vote.
Simon
--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 o
Wow. IE 11 implements RFC 6874 perfectly.
This is a shame.
Simon
Le 2014-02-05 10:43, Simon Perreault a écrit :
> Am I becoming crazy or do URIs such as these no longer work?
>
> http://[fe80::1%em0]/
> http://[fe80::1%25em0]/
> http://[fe80::1%em0]:80/
> http://[fe80::1
Am I becoming crazy or do URIs such as these no longer work?
http://[fe80::1%em0]/
http://[fe80::1%25em0]/
http://[fe80::1%em0]:80/
http://[fe80::1%25em0]:80/
I tested Firefox 26.0 and Chrome 32.0.1700.102 on Fedora 20. The
browsers just pass the whole string to Google. There seems to be no
attem
Le 2014-01-22 11:54, Francis Dupont a écrit :
On 20/01/2014 17:12, Simon Perreault wrote:
> IIRC, recent versions of Bind open a socket per address on IPv4
=> not it is not by choice, just:
- DNS requires to answer from the address the request was received
- there is no st
Le 2014-01-20 12:00, Gert Doering a écrit :
Anyway, if you really want to make your life miserable, open sockets
bound to the individual IP addresses found on the machine---and then
also listen on a routing socket so you know you have to look for new
addresses coming in... (Last time I checked t
Le 2014-01-20 09:00, Gert Doering a écrit :
I've run into this sort of problems a few years ago, but I used a
different solution: I didn't use mapped addresses but two separate
sockets, one for IPv4 and another for IPv6.
This *is* a long-term goal, though, to enable OpenVPN to listen on multipl
Le 2014-01-07 10:18, Mark Townsley a écrit :
And generating stinkin' ICMPv6 too big messages ends up being perhaps the most
significant scaling factor of a 6rd BR deployment...
The worst thing is a lot of content providers will simply ignore those
too bigs you worked so hard to produce... *s
Le 2014-01-07 08:46, jean-francois.tremblay...@videotron.com a écrit :
In the list of "tricks", you might want to add:
* Slightly raise the ICMPv6 rate-limit values for your 6RD BR (we do 50/20)
Yeah, this is really problematic. When IPv6 packets arrive at the BR
from the Internet, the BR need
Le 2013-12-19 11:46, Phil Mayers a écrit :
What does "ip -6 route" show on an affected box?
Ok, this is getting really strange. Maybe the "userspace RA listener"
has just kicked in, because IPv6 is working, but config is still funny.
A reboot doesn't change this, so it's a stable situation.
Le 2013-12-19 11:22, Hannes Frederic Sowa a écrit :
NM has a user-space RA listener.
Any pointers to documentation? I'm trying to investigate...
Thanks,
Simon
--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source--> http://ecdysis.viagenie.ca
STU
Le 2013-12-19 11:16, Jeroen Massar a écrit :
On 2013-12-19 17:09 , Simon Perreault wrote:
Is there any other Fedora user on this list that could confirm this?
I filed a bug here:
https://bugzilla.redhat.com/show_bug.cgi?id=1045118
net.ipv6.conf.em1.accept_ra = 0
How do you expect that to
Is there any other Fedora user on this list that could confirm this?
I filed a bug here:
https://bugzilla.redhat.com/show_bug.cgi?id=1045118
Thanks,
Simon
--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source--> http://ecdysis.viagenie.ca
STUN/TURN
Le 2013-11-25 08:20, Dick Visser a écrit :
I'd like to 'upgrade' out existing NAT64/DNS64 setup to do 464XLAT, but
there aren't many docs about how to set 464XLAT to begin with.
FYI, our OpenBSD implementation of NAT64 also does NAT46. It's been part
of regular OpenBSD releases since 5.1. But
Le 2013-11-05 14:53, Jen Linkova a écrit :
http://www.dslreports.com/shownews/TMobile-Goes-IPv6-Only-on-Android-44-Devices-126506
W00t!!!
P.S. The link to the news does not work from IPv6-only network.
Use SSID ietf-nat64.
Our own dog food. Eat it. :)
Simon
--
DTN made easy, lean, and
Le 2013-10-24 17:48, Brandon Ross a écrit :
> I'd like an option to rotate my privacy address for every TCP session.
I suppose you could simply do this on Linux to get a new one every second:
net.ipv6.conf.all.temp_prefered_lft = 1
Simon
Le 2013-10-14 08:30, Mikael Abrahamsson a écrit :
> I had an entry in my /etc/hosts with an IPv4 address only, and was
> SSHing to it. By some internal magic, OSX had discovered the NAT64
> prefix and was using it by itself to connect to this "ipv4 only" host.
Did they implement the NAT64 prefix d
18 matches
Mail list logo
