07/04/12 19:37, Nikolay Denev пишет:
On Jul 4, 2012, at 6:08 PM, Budnev Vladimir wrote:
Good day to all.
What is the correct way to distinguish udp packets that obtained by application
and were send on 255.255.255.255 ip addr from those that were send to unicast
ip?
Seems it is impossible w
On Jul 4, 2012, at 6:08 PM, Budnev Vladimir wrote:
> Good day to all.
>
> What is the correct way to distinguish udp packets that obtained by
> application and were send on 255.255.255.255 ip addr from those that were
> send to unicast ip?
>
> Seems it is impossible with read/recvfrom so we'v
Good day to all.
What is the correct way to distinguish udp packets that obtained by
application and were send on 255.255.255.255 ip addr from those that
were send to unicast ip?
Seems it is impossible with read/recvfrom so we'v made that with
libpcap. It coul be done with directly bpf api w
On Tuesday 15 July 2003 04:49 pm, Chuck Swiger wrote:
> Wes Peters wrote:
> [ ... ]
>
> > The idea is, we have listener on each ethernet interface listening
> > via a bpf. The listener listens for an 'appliance discovery'
> > packet which is broadcast by the console application running on the
> >
On Tue, Jul 15, 2003 at 03:48:48PM -0700, Wes Peters wrote:
>
> It's a broadcast, the socket isn't bound to an interface. ;^)
>
> The idea is, we have listener on each ethernet interface listening via a
> bpf. The listener listens for an 'appliance discovery' packet which is
> broadcast by th
Wes Peters wrote:
[ ... ]
The idea is, we have listener on each ethernet interface listening via a
bpf. The listener listens for an 'appliance discovery' packet which is
broadcast by the console application running on the admin's
workstation. When we receive this discovery packet, we're suppos
On Tuesday 15 July 2003 10:09, Matthew Grooms wrote:
> Hmmm,
>
> >What we observed on our embedded system is the packet gets sent on
> > all attached interfaces, with dest IP 255.255.255.255, and a src IP
> > of the local address that has the default route. If there isn't a
> > default route, send
Hmmm,
>What we observed on our embedded system is the packet gets sent on all
>attached interfaces, with dest IP 255.255.255.255, and a src IP of the
>local address that has the default route. If there isn't a default
>route, sending to 255.255.255.255 fails with "no route to host."
>
Maybe I am
> -Original Message-
> From: Wes Peters [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 11, 2003 5:03 PM
> To: Sreekanth; 'Don Lewis'
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: broadcast udp packets ...
>
>
> On Friday 11 July 2003 14:21, Sreekant
On Friday 11 July 2003 14:21, Sreekanth wrote:
> Couldn't it be done just by executing the following command ?
> #route add 255.255.255.255 -net 255.255.255.255 -ifp [primary
> interface]
>
> I know it is kind of crude but it works in my case :-)
In our case, it's being run before *any* interface
On Friday 11 July 2003 14:09, Don Lewis wrote:
> On 11 Jul, Wes Peters wrote:
> > What we observed on our embedded system is the packet gets sent on
> > all attached interfaces, with dest IP 255.255.255.255, and a src IP
> > of the local address that has the default route. If there isn't a
> > def
Wes Peters wrote:
On Tuesday 01 July 2003 12:01, Chuck Swiger wrote:
If you have multiple interfaces, a broadcast to 255.255.255.255
should go out on all of them. That being said, the all-ones
broadcast address means "all local networks", and most routers will
block such traffic from passing on in
TED] On Behalf Of Don Lewis
> Sent: Friday, July 11, 2003 2:10 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: broadcast udp packets ...
>
>
> On 11 Jul, Wes Peters wrote:
>
>
> > What we observed on our embedded system
On 11 Jul, Wes Peters wrote:
> What we observed on our embedded system is the packet gets sent on all
> attached interfaces, with dest IP 255.255.255.255, and a src IP of the
> local address that has the default route. If there isn't a default
> route, sending to 255.255.255.255 fails with "n
On Tuesday 01 July 2003 12:01, Chuck Swiger wrote:
> Matthew Grooms wrote:
> > Is there any way to generate a udp broadcast ( all routes
> > 255.255.255.255 ) packet using a standard sendto() without it being
> > translated into a local network broadcast? Is this just not
> > "allowed"?
>
> Ar
The short answer is no, you can't, in_pcb turns 255.255.255.255 into
the "primary" interface's broadcast address.
I doubt this is actually useful behavior, but that's not what you
asked =)
Bill
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.
Hey,
Thanks for the response. I will look into netgraph then. I was thinking
it could be useful to have flexable utility that could be used to bridge
distant broadcast domains ( w/filtering ). The home-grown thingy is an
exercise to learn more about unix programming. Most of my experience is
you can use netgraph to make a "virtual bridge"
see /usr/share/examples/netgraph for an example of a single bridge.
attach one of the bridge hooks on each site to an ng_socket node that
has made a udp vpn..
see the vpn example for that..
by combining both the bridge and vpn examples you can hook
On Tue, Jul 01, 2003 at 09:46:33PM +, Matthew Grooms wrote:
>
> In any case, I wrote a quick little program to generate a broadcast
> message for use with testing the relay daemon ( I got tired of waiting for
> bootp requests to be picked up by my cable modem as a test case ).
> Unfortuna
Well,
Ok, sounds stupid right, well here is a bit of background. My friend and
I have an IPSEC tunnel in between our two private networks connected by BSD
firewalls w/ cable modems. Without going into too much detail, certain
programs ( win32 games ) use all-routes broadcasts to advertise th
Matthew Grooms wrote:
Is there any way to generate a udp broadcast ( all routes
255.255.255.255 ) packet using a standard sendto() without it being
translated into a local network broadcast? Is this just not "allowed"?
Are you trying to use 255.255.255.255 to reach something not on a local sub
One more question,
Is there any way to generate a udp broadcast ( all routes
255.255.255.255 ) packet using a standard sendto() without it being
translated into a local network broadcast? Is this just not "allowed"?
-Matthew
___
[EMAIL PROTECTED] m
22 matches
Mail list logo
