Re: Socket bound to 0.0.0.0 never receives broadcasts with non-zero IP source address

On 04/08/2015 19:59, John Howie wrote: > Still at 35000’ (literally), trying to get to where I am going! Oh, you are flying! I first didn't understand what 35000' meant. Have a safe rest of the flight! Yuri ___ freebsd-net@freebsd.org mailing list http

Re: [BUG?] dhclient sends packets with source IP address that has been deleted

On Wed, Apr 8, 2015 at 1:03 AM, J.R. Oldroyd wrote: > On Tue, 7 Apr 2015 14:53:54 + Brooks Davis wrote: > > > > On Mon, Apr 06, 2015 at 08:13:56PM -0700, Yuri wrote: > > > I am observing what dhclient sends to the server. Source IP of the > > > packet it sends is the previous DHCP lease. Thi

Re: Socket bound to 0.0.0.0 never receives broadcasts with non-zero IP source address

Hi Yuri, No need to apologize! Sometimes it takes a dispassionate person to review the problem to help you find the solution. You found it, not me. I just helped you get there… Still at 35000’ (literally), trying to get to where I am going! Regards, John On 4/8/15, 9:43 PM, "Yuri" wrote: >O

Re: Socket bound to 0.0.0.0 never receives broadcasts with non-zero IP source address

On 04/08/2015 16:07, John Howie wrote: Have you tried using a static IP address for the host and VM, and disabling DHCP? The DHCP client will bind to and use 0.0.0.0 to get an IP address. The SO_REUSEADDR rule is that every tuple (proto, src ip, src port, dst ip, dst prt) must be unique. I am won

Re: Socket bound to 0.0.0.0 never receives broadcasts with non-zero IP source address

Hi Yuri, Have you tried using a static IP address for the host and VM, and disabling DHCP? The DHCP client will bind to and use 0.0.0.0 to get an IP address. The SO_REUSEADDR rule is that every tuple (proto, src ip, src port, dst ip, dst prt) must be unique. I am wondering if that is where your pr

Re: Socket bound to 0.0.0.0 never receives broadcasts with non-zero IP source address

On 04/08/2015 15:31, John Howie wrote: Is your machine a router or gateway, or have a firewall? Are you trying to capture all broadcast packets, or just UDP targeted and broadcast packets to a particular port? No, it isn't a gateway or router, and no firewall. Trying to capture all broadcast U

Re: [BUG?] dhclient sends packets with source IP address that has been deleted

On 04/08/2015 01:03, J.R. Oldroyd wrote: From RFC2131, section 4.1: DHCP messages broadcast by a client prior to that client obtaining its IP address must have the source address field in the IP header set to 0. Note the "must" there. So the current behavior looks like an error, t

Re: Socket bound to 0.0.0.0 never receives broadcasts with non-zero IP source address

Hi Yuri, Is your machine a router or gateway, or have a firewall? Are you trying to capture all broadcast packets, or just UDP targeted and broadcast packets to a particular port? Regards, John On 4/8/15, 5:21 PM, "Yuri" wrote: >On 04/08/2015 05:32, Daniel Corbe wrote: >> If nobody answers th

Re: Socket bound to 0.0.0.0 never receives broadcasts with non-zero IP source address

On 04/08/2015 05:32, Daniel Corbe wrote: If nobody answers this question by the time I get home I'll try and help; however, in the mean time I do have a couple of suggestions. Have you tried writing the equivalent program in C using the sockets API? IE is this a python specific problem or a soc

Re: RTT and TCP Window size doubts, bandwidth issues

On 04/07/15 15:10, Marek Salwerowicz wrote: > Hi list, > > I am trying to find correct setup of sysctl's for following machines > (VMs under Vmware Workstation 8) to test large TCP window size: > > > There are 2 boxes, each of them has following setup: > - % uname -a > FreeBSD freeA 10.1-RELEASE

Re: RTT and TCP Window size doubts, bandwidth issues

On Wed, 8 Apr 2015 00:10:51 +0200, Marek Salwerowicz wrote: > Hi list, > > I am trying to find correct setup of sysctl's for following machines (VMs > under Vmware Workstation 8) to test large TCP window size: > > > There are 2 boxes, each of them has following setup: > - % uname -a > F

Re: Socket bound to 0.0.0.0 never receives broadcasts with non-zero IP source address

If nobody answers this question by the time I get home I'll try and help; however, in the mean time I do have a couple of suggestions. Have you tried writing the equivalent program in C using the sockets API? IE is this a python specific problem or a sockets problem in general? The second thing

Netmap usage in Freebsd10

Hi Netmap developers, In very simple application, I am using two freebsd10 vm's spawned using Qemu. About my environment, Underlying host os is linux, freebsd10 vm's are guest vms. These two bsd10 vm's are connected using em interface (which again Qemu emulated). |== 10.10.10.1 (em)

ipfw / dummynet does not hit the rules?

Hi all, I have simple VM ('freeC') with 3 NICs: - em0 connected to NAT (acces to SSH) - em1 connected to "segment 1" - em2 connected to "segment 2" there are 2 other VMs: - freeA connected to "segment 1", 10.0.0.1/24 - freeB connected to "segment 2", 10.0.0.2/24 Idea: Create a L2 bridge on f

Re: [BUG?] dhclient sends packets with source IP address that has been deleted

On Tue, 7 Apr 2015 14:53:54 + Brooks Davis wrote: > > On Mon, Apr 06, 2015 at 08:13:56PM -0700, Yuri wrote: > > I am observing what dhclient sends to the server. Source IP of the > > packet it sends is the previous DHCP lease. This address doesn't exist > > any more, because I manually delet