n/egg problem.
>>
>>
>
> Having the same IP in more than one place (on the router) is the thing that
> I'd
> like to avoid in the first place. Otherwise, there is no problem putting it
> in
> hdcpd.conf.
>
A secondary DNS server could also help,
myself although I plan to give it a
spin sometime.
This is just a suggestion from a more practical point of view, without
any consideration on which one is the superior protocol/tool.
--
Guido Falsi
___
freebsd-net@freebsd.org mailing list
https
but I can't pinpoint it with much more precision.
Thanks for your feedback!
--
Guido Falsi
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
chip=0x15b88086
rev=0x31 hdr=0x00
--
Guido Falsi
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
On 07/01/16 16:20, Andrey V. Elsukov wrote:
> On 30.06.16 13:05, Guido Falsi wrote:
>> While testing the new firewall functionality on head I stumbled in this:
>>
>> root@sensei:~ [0]# ipfw table foo create type number
>>
>> ipfw: Table creation failed: Operation n
While testing the new firewall functionality on head I stumbled in this:
root@sensei:~ [0]# ipfw table foo create type number
ipfw: Table creation failed: Operation not supported
root@sensei:~ [71]#
The ipfw man page states this should work, am I missing something?
--
Guido Falsi
e to do what you are asking for.
--
Guido Falsi
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
HZ setting can be done in loader.conf at boot time, no need for
recompilation.
>
> And, in general, is it still needed to compile a custom kernel for dummynet
> to work more precisely?
I think at present it can work fine with the HZ=1000 default. To know if
that's ok for your work
be *perfect*. Something like the output of pciconf
> -lv for the card and the "how do I reproduce this" instructions.
>
Filed as bug 208343
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208343
Thanks!
--
Guido Falsi
___
freebsd-net
t; b.
What do you need in the testcase? The only data I'm sure about is the
chipset I have (PCI IDs) and the fact that I'm using head r297146. Is
any further information needed?
--
Guido Falsi
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
ter shutdown, while it works if
turning off the machine from the BIOS (obviously appropriate flags in
the BIOS are turned on) with the power button.
Am I missing something obvious? Any further information is needed?
Thanks in advance.
--
Guido Fa
On 01/15/16 20:43, Gerrit Kühn wrote:
> On Fri, 15 Jan 2016 16:54:04 +0100
> Guido Falsi wrote:
>
> GF> I forget one thing, Are the mindlna and mediatomb installed in a
> GF> jail?
>
> No jails involved here, they are both running on a plain machine.
>
> I jus
ill never receive multicasts and so, never
reply, since multicasts which are not forwarded to jailed IPs. You'll
have to install them on the main machine.
I've also read this can be worked around using vimage, but I have never
tried that
--
Guido Falsi
_
On 01/15/16 16:00, Gerrit Kühn wrote:
> On Fri, 15 Jan 2016 15:44:42 +0100 Guido Falsi
> wrote about Re: upnp/dlna:
>
> GF> Could you try the patch here:
> GF> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205430
>
> I'll try and report back, thanks for the
u're seeing that same issue.
--
Guido Falsi
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
hat uses many stateful
>> rules, but some people prefer stateless firewalling, which requires
>> rules for both inbound and outbound traffic.
>
> Yeah, I could do stateless and require both inbound and outbound rules
> but that&#
correctly this setup requires one_pass=1 to
work, I'm not completely sure this is your problem though. I think it's
worth a try.
Please note that my structure is just an example, there are many other
ways to organize your firewall. I have a setup that uses many stateful
rules, but some peo
On 06/12/15 10:07, Ian Smith wrote:
> On Fri, 12 Jun 2015 08:59:40 +0200, Guido Falsi wrote:
>
> > > looks correct, assuming xl0 is your internal interface (better put it in
> > > a variable and use the variable in your rules imho)
> >
> > Forgot one th
On 06/12/15 08:49, Guido Falsi wrote:
> On 06/12/15 04:49, John Reynolds wrote:
>>
>> I have a situation where I need to just simply "block all traffic" from
>> some teenagers' mobile devices after a certain period of the day (don't
>> ask teena
at I'm hoping for? I currently don't have any
> real FW to speak of--ipfw is there but the type is "open," so I'm trying
> to learn as I go along in order to setup an actual firewall for this box
> @ the same time.
looks correct, assuming xl0 is your internal
the port sysutils/cmdwatch with ipfw, like this:
cmdwatch "ipfw -d show | sed -n -e '/## Dynamic rules/,\$p'"
It's a little crude but works quite fine.
Needs to run as root, obviously.
--
Guido Falsi
___
freebsd-net@freebs
On 09/11/13 02:15, Yonghyeon PYUN wrote:
On Wed, Sep 11, 2013 at 01:31:49AM +0200, Guido Falsi wrote:
Hi,
This patch shows the same behavior as the unpatched kernel:
[...]
I'd like to note that if I perform a tcpdump from the other machine
(which is also the dns server) I do se
On 09/10/13 04:15, Yonghyeon PYUN wrote:
On Fri, Sep 06, 2013 at 10:42:56PM +0200, Guido Falsi wrote:
On 09/06/13 08:15, Yonghyeon PYUN wrote:
On Wed, Jul 10, 2013 at 07:47:01PM +0200, Guido Falsi wrote:
On 07/10/13 09:04, Yonghyeon PYUN wrote:
On Tue, Jul 09, 2013 at 10:28:29PM +0200, Guido
On 09/06/13 08:15, Yonghyeon PYUN wrote:
On Wed, Jul 10, 2013 at 07:47:01PM +0200, Guido Falsi wrote:
On 07/10/13 09:04, Yonghyeon PYUN wrote:
On Tue, Jul 09, 2013 at 10:28:29PM +0200, Guido Falsi wrote:
Hi,
I have a PC with an integrate re ethernet interface, pciconf identifies
it like this
On 07/19/13 03:58, Chris H wrote:
On 07/10/13 19:47, Guido Falsi wrote:
On 07/10/13 09:04, Yonghyeon PYUN wrote:
On Tue, Jul 09, 2013 at 10:28:29PM +0200, Guido Falsi wrote:
Hi,
I have a PC with an integrate re ethernet interface, pciconf identifies
it like this:
re0@pci0:3:0:0: class
On 07/10/13 19:47, Guido Falsi wrote:
On 07/10/13 09:04, Yonghyeon PYUN wrote:
On Tue, Jul 09, 2013 at 10:28:29PM +0200, Guido Falsi wrote:
Hi,
I have a PC with an integrate re ethernet interface, pciconf identifies
it like this:
re0@pci0:3:0:0: class=0x02 card=0x11c01734 chip=0x816810ec
On 07/10/13 09:04, Yonghyeon PYUN wrote:
On Tue, Jul 09, 2013 at 10:28:29PM +0200, Guido Falsi wrote:
Hi,
I have a PC with an integrate re ethernet interface, pciconf identifies
it like this:
re0@pci0:3:0:0: class=0x02 card=0x11c01734 chip=0x816810ec rev=0x07
hdr=0x00
I'm running Fr
27;t know much about FreeBSD network drivers so i can't make theories
about this. I hope someone has an idea what the problem could be.
I'm available for any further information needed, test, experiment and
so on.
Thanks in advance!
--
Guido Falsi
_
is is just my opinion, obviously. As stated I don't know much about
launchd, and it is quite possible that I have misconceptions about it,
so please don't flame me if I insulted it!
Thank you for your effort and work to bring this to the masses!
--
Guido Falsi
tered it while trying to configure a wlan(with WPA2) failsafe
lagg with the cabled ethernet.
Any news on that front?
Sorry if I could not be of any more help and thanks for any answers to
my query.
P.S. I'm also CCing freebsd-net@, since the problems seems to be
appropriate there.
--
Guido
30 matches
Mail list logo
