Guess was right on the money, thank you!
It turns out that there was a route for that entire /23 on another
interface for some unfathomable reason.
I had to turn that iface down too to remove it, but once I did so,
everything is once again peachy!
Thank you!
On 3/20/2015 午前 12:58, Eric van
Hi,
is anyone going to include gre over IPv6 into the current stable branch?
It would be nice to have it in the upcoming 10.2 release.
Kind regards
Julian
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To
On 03/17/15 at 12:34P, Adrian Chadd wrote:
> On 17 March 2015 at 11:33, Jason Wolfe wrote:
> > On Mon, Mar 16, 2015 at 2:43 AM, Hans Petter Selasky
> > wrote:
> >> On 03/16/15 10:37, Vitalii Duk wrote:
> >>>
> >>> I've changed use_flowid to 0 and it helped! But isn't it setting
> >>> significant
> On 3/19/2015 午前 11:20, Paul S. wrote:
>> root@ipfw-0:~ # arp -d 110.62..211.87
>> arp: writing to routing socket: Invalid argument
I have a vague memory of similar behavior when I had a misconfigured
route. I think there was a route for a local interface address with an
off-box gateway. (Don'
Hi!
It is already several years as the "opaque ifnet" has been discussed,
and almost a year since it was announced to be worked on.
For now I've got a branch in svn, where some proof of concept is done:
http://svn.freebsd.org/base/projects/ifnet
I've described what's going on in wik
On 03/19/15 12:38, Emeric POUPON wrote:
Hello,
I noticed two questionable things in the fragmentation code:
- in ip_fragment, we do not copy the flowid from the original mbuf to the
fragmented mbuf. Therefore we may output very desynchronized fragments (first
fragment emitted far later the sec
Hello,
I noticed two questionable things in the fragmentation code:
- in ip_fragment, we do not copy the flowid from the original mbuf to the
fragmented mbuf. Therefore we may output very desynchronized fragments (first
fragment emitted far later the second fragment, etc.)
- in the ip_newid macr
