0n Tue, May 01, 2007 at 11:31:58AM +0800, Wilkinson, Alex wrote:
>0n Mon, Apr 30, 2007 at 10:58:18AM +0100, Robert Watson wrote:
>
>>One of the big selling points of IPFW is integration with DUMMYNET,
which
>>offers bandwidth management facilities not present in
0n Mon, Apr 30, 2007 at 10:58:18AM +0100, Robert Watson wrote:
>One of the big selling points of IPFW is integration with DUMMYNET, which
>offers bandwidth management facilities not present in the other systems.
I
>understand there may be efforts afoot to add DUMMYNET support
Synopsis: [netinet] potentially a bug for inet_aton in
sys/netinet/libalias/alias_proxy.c
State-Changed-From-To: open->patched
State-Changed-By: maxim
State-Changed-When: Mon Apr 30 20:22:26 UTC 2007
State-Changed-Why:
Fixed in HEAD. Thanks!
Responsible-Changed-From-To: freebsd-net->maxim
Res
Abraham K. Mathen wrote:
Is it possible to successfully sendto() on a UDP socket
with 127.255.255.255 as the destination address? If yes,
how can that be done.
No, because in FreeBSD, lo(4) is not implemented as a broadcast
interface. It is a multicast capable software loopback interface. I
Abraham K. Mathen wrote:
> NOTE : A copy of this message was sent to freebsd-hackers also.
> Apologies for the separate mails.
>
> Hello freebsd-net,
> I wrote a short program (on FreeBSD 6.0), that attempts
> to call sendto() on a UDP socket, with 127.255.255.255 as
> the destination a
On Mon, 30 Apr 2007, Peter Jeremy wrote:
On 2007-Apr-30 10:58:18 +0100, Robert Watson <[EMAIL PROTECTED]> wrote:
One of the big selling points of IPFW is integration with DUMMYNET, which
offers bandwidth management facilities not present in the other systems.
I thought altq(4) could also do
On 2007-Apr-30 10:58:18 +0100, Robert Watson <[EMAIL PROTECTED]> wrote:
>One of the big selling points of IPFW is integration with DUMMYNET, which
>offers bandwidth management facilities not present in the other systems.
I thought altq(4) could also do most of what dummynet(4) does but
based on a
Current FreeBSD problem reports
Critical problems
Serious problems
S Tracker Resp. Description
a kern/38554 netchanging interface ipaddress doesn't seem to work
s kern/39937 netipstealth
NOTE : A copy of this message was sent to freebsd-hackers also.
Apologies for the separate mails.
Hello freebsd-net,
I wrote a short program (on FreeBSD 6.0), that attempts
to call sendto() on a UDP socket, with 127.255.255.255 as
the destination address. It failed - with errno 49 (EAD
On Sun, 29 Apr 2007, Peter Jeremy wrote:
On 2007-Apr-28 07:08:18 -0500, Jack Barnett <[EMAIL PROTECTED]> wrote:
I plan on using NAT so both internal networks can get to the internets.
In the FreeBSD documentation I see there are 3 firewalls, IPFIREWALL,
IPFILTER and PF (BF?). I just need to
10 matches
Mail list logo
