ges from a routing socket.
> When I'm adding an IPv4 address to the tun interfaces, I receive
> a RTM_NEWADDR routing message with the added address. However, I
> do NOT receive one, when I'm adding an IPv6 address.
> When deleting an IPv4 or IPv6 address, I do receive the cor
Dear all,
I'm using a tun interface with the IFF_BROADCAST | IFF_MULTICAST mode.
I can use ifconfig to add an IPv4 or IPv6 address. So far so good.
I'm running a program which gets all messages from a routing socket.
When I'm adding an IPv4 address to the tun interfaces, I receiv
On Wed, Oct 24, 2001 at 11:14:54AM -0200, Daniel C. Sobral wrote:
> After a long time looking into this, I have finally understood what's
> the problem. RTM_NEWADDR is generated sometimes yes, sometimes no. I
> have absolutely no idea what makes the difference, particularly bec
After a long time looking into this, I have finally understood what's
the problem. RTM_NEWADDR is generated sometimes yes, sometimes no. I
have absolutely no idea what makes the difference, particularly because
I have absolutely no idea where the relevant code portions is located.
As f
<
said:
> I was wondering about RTM_NEWADDR. I have noticed that no such message
> is generated when you add a new address to an interface with ifconfig.
This may or may not be a bug. I'm inclined to say that it is a bug; a
routing process should probably be informed when a
I was wondering about RTM_NEWADDR. I have noticed that no such message
is generated when you add a new address to an interface with ifconfig.
So I have two questions: is that what is expected? And how can I receive
events whenever a new address is set on an interface?
--
Daniel C. Sobral
