Thanks, Mark.

I've taken a closer look at this by logging into my switch management
console (which had not yet been set up at my last email).  I was
mistaken:  Packets are coming in from the BEE2, but are being tagged as
"discarded" in the switch, and are not getting transmitted to the
destination machine.  (When it works, of course, packets are not
"discarded", and that is easily seen).  As a note, I have tried setting
the BEE2 to the 10.5 subnet, and packets go through fine then (proof of
concept that it's *possible* to get packets from A-to-B).

 

The subnet mask on the receiving interface is /16.  I tried to configure
the receiver to /8 as a test, but that didn't seem to help.

 

Any thoughts as to why the switch might discard packets in this way?

 

Thanks,

Billy

 

 

________________________________

From: Mark Wagner [mailto:mwag...@eecs.berkeley.edu] 
Sent: Thursday, October 14, 2010 12:25 AM
To: Barott, William Chauncey
Cc: casper@lists.berkeley.edu
Subject: Re: [casper] 10Gbe yellow block outside of subnet?

 

Hi Billy,

 

I'm not aware of the 10Gbe being specific to certain subnets.  Are you
sure it's a generating packets issue and not a receiving packets?

 

Have you tried looking for packets using something like wireshark or
tcpdump?  

 

Also, if you run ifconfig, what is your subnet mask set to?

 

Mark

 

 

On Wed, Oct 13, 2010 at 6:23 PM, Barott, William Chauncey
<baro...@erau.edu> wrote:

Hi all,

 

I'm running version 7 of the toolflow compiling for BEE2s.  Have run
into a difficulty with the 10Gbe yellow block.

I can quite successfully generate packets within the same subnet - e.g.
the BEE2 on 10.4.0.100 and a receiver computer on 10.4.0.101.  However,
I've not been successful in trying to generate packets outside of the
/24 subnet.  With the same 10.4.0.100 BEE2 address, I cannot get packets
delivered to 10.5.0.101, for example (note the 4 changed to 5).  I've
not been able to find a subnet configuration for the BEE2 10gbe block -
maybe I've missed it, nor have I found anything about such a limitation
in the documentation.  It could also be a peculiarity of my network
setup (though it's all quite out of the box), but difficult to diagnose
at this stage.

 

Has someone out there successfully done what I'm trying to do?  Or know
that it's not possible?

Any info is appreciated.  Thanks!

 

Billy

 

 

 

 

Reply via email to