On 24 January 2016 at 11:36, Otacílio wrote:
> Em 24/01/2016 07:24, Olivier Cochard-Labbé escreveu:
>
>> On Sun, Jan 24, 2016 at 9:41 AM, Ben Woods wrote:
>>
>> Hi everyone,
>>>
>>> Could someone running FreeBSD current on a test machine try loading the
>>> ip_mroute driver on their machine?
>>>
Em 24/01/2016 07:24, Olivier Cochard-Labbé escreveu:
On Sun, Jan 24, 2016 at 9:41 AM, Ben Woods wrote:
Hi everyone,
Could someone running FreeBSD current on a test machine try loading the
ip_mroute driver on their machine?
Hi,
no problem here:
root@lame5 # uname -a
FreeBSD lame5.bsdrp.ne
On Sun, Jan 24, 2016 at 9:41 AM, Ben Woods wrote:
>
> Hi everyone,
>
> Could someone running FreeBSD current on a test machine try loading the
> ip_mroute driver on their machine?
>
Hi,
no problem here:
root@lame5 # uname -a
FreeBSD lame5.bsdrp.net 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r294522
yone,
Could someone running FreeBSD current on a test machine try loading the
ip_mroute driver on their machine?
This is to enable multicast routing, but I am wondering if it fails to load
for everyone, or it is specific to my build some how.
I am running r294463, please let me know which
On Tue, Jan 21, 2014 at 2:33 PM, Gleb Smirnoff wrote:
> On Sun, Jan 19, 2014 at 02:42:32AM +0100, Olivier Cochard-Labbé wrote:
> O> But there is still a regression regarding the PIM socket behavior not
> O> related to the packet format.
>
> Can you please try this patch to kernel?
>
>
Lot's bette
On Wednesday, January 15, 2014 6:34:30 am Gleb Smirnoff wrote:
> Damn, what a mess. I'd like to go towards absolutely unmodified packets
> for the 11-release cycle.
I agree.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.free
On Sun, Jan 19, 2014 at 02:42:32AM +0100, Olivier Cochard-Labbé wrote:
O> > Olivier,
O> >
O> >
O> > TL;DR version: you need not subtract iphdrlen in 10.0. Code in
O> > igmp.c:accept_igmp()
O> > should be smth like:
O> >
O> > iphdrlen = ip->ip_hl << 2;
O> > #ifdef RAW_INPUT_IS_RAW /* Linux */
On Wed, Jan 15, 2014 at 12:34 PM, Gleb Smirnoff wrote:
> Olivier,
>
>
> TL;DR version: you need not subtract iphdrlen in 10.0. Code in
> igmp.c:accept_igmp()
> should be smth like:
>
> iphdrlen = ip->ip_hl << 2;
> #ifdef RAW_INPUT_IS_RAW /* Linux */
> ipdatalen = ntohs(ip->ip_len) - ip
On 15 January 2014 03:34, Gleb Smirnoff wrote:
[snip]
> Damn, what a mess. I'd like to go towards absolutely unmodified packets
> for the 11-release cycle.
Well, now's the time to _start_ this. :-) Not 6 months before 11.0 :P
-a
___
freebsd-current@
Olivier,
On Tue, Jan 14, 2014 at 05:51:53PM +0100, Olivier Cochard-Labbé wrote:
O> I'm trying to port a PIM sparse-mode daemon (
O> https://github.com/troglobit/pimd/) and I've meet a problem:
O> This daemon compile and run fine on FreeBSD 9.2 but on 10-RC5 this daemon
O> can't understand receiv
Hi all,
I'm trying to port a PIM sparse-mode daemon (
https://github.com/troglobit/pimd/) and I've meet a problem:
This daemon compile and run fine on FreeBSD 9.2 but on 10-RC5 this daemon
can't understand received multicast packets (received from other PIM
neighbors) and display this kind of erro
On 25.05.2010 13:21, Kamigishi Rei wrote
> device pf
> device pflog
> device pfsync
> options ALTQ
> options ALTQ_HFSC
> options DEVICE_POLLING
> options MROUTING
>
Tried reproducing with
options KDB
options DDB
options KDB_UNATTENDED
Hello, hope you're having a nice day,
I have a problem with my single-core amd64 system running FreeBSD
8.0-STABLE #1 r200287; if I try running XORP (or igmpproxy) to route
multicast packets, the system traps after a while - usually less than a
hour since the start of xorp process. This is, basica
Anyone have any good how-to's on how to setup a FreeBSD box to do multicast
routing? Im wanting to setup a FreeBSD gateway that will have a Cable modem
and a DSL modem connected to it. Any traffic on certain ports I want to go
through (out) one interface (dc0) and the rest to go throug
14 matches
Mail list logo