On Fri, Aug 22, 2003 at 06:18:57AM -0700, Bill Fenner wrote:
> I think c) (perhaps combined with IP_RECVDSTADDR so that you know
> whether you got a unicast or broadcast) is the correct answer.
> I think binding UDP sockets to tell what interface/address was
> the destination is a historical artifa
Hi, what is the config you are using to test this ? IPSEC ?
FAST_IPSEC ? type of keying ?
---Mike
On Thu, 21 Aug 2003 18:58:20 +0300, in sentex.lists.freebsd.net you
wrote:
>Hi there!
>
>It seems that ipcomp in the tunnel mode is still broken in at
>least 4.x (I cannot test it with two
Maxim Konovalov wrote:
[ CC: trimmed ]
On Wed, 20 Aug 2003, 14:52-0300, Daniel C. Sobral wrote:
[...]
If you get bridge to send/receive packets to/from vlan interfaces
attached to them, I'll be forever grateful.
I've been trying to configure a setup where a firewall is connected to
redundant swi
I think c) (perhaps combined with IP_RECVDSTADDR so that you know
whether you got a unicast or broadcast) is the correct answer.
I think binding UDP sockets to tell what interface/address was
the destination is a historical artifact.
Bill
___
[EMAIL P
>I want to build a network as shown below.
> All devices is in my responsibity except the
> upsteam router. My question is
>
>If I will assign public IP address to all
>interfaces, is it neccessary that I must
>inform the upstream router's administrator
>to add my subnet in
Hi, all
I want to build a network as shown below.
All devices is in my responsibity except the
upsteam router. My question is
If I will assign public IP address to all
interfaces, is it neccessary that I must
inform the upstream router's administrator
to add my subnet in routing
Hi all,
Ok, the broadcast sending problem is solved, as far as I'm concerned.
However, the reception problem isn't:
14766 broadcast/multicast datagrams dropped due to no socket
This despite:
wi0: flags=8843 mtu 1500
inet 1.234.56.78 netmask 0xff00 broadcast 1.255.255.255
udp4
On Thu, Aug 21, 2003 at 10:35:03PM -0700, Wes Peters wrote:
> Your change makes it so that broadcasts sent to 255.255.255.255 will
> be transmitted on all interfaces marked with a ONES_BCAST flag, right?
It really is a very simple addition.
It's a protocol-level socket option, so doesn't interfe
