Re: [pox-dev] Riplpox with large topology

[Amer]

Thank you Murphy
Yes, it is working correctly with the default number of host (i.e., 16 hosts).

Best regards,
Amer 

Sent from my iPhone

> On Sep 3, 2015, at 4:00 AM, Murphy McCauley  wrote:
> 
> Did it work correctly with a smaller number of hosts before modification?
> 
>> On Wednesday, September 2, 2015, Amer  wrote:
>> Dear All
>> 
>> The default number of hosts in riplpox is 16. I modified some commands in 
>> dctopo.py in ripl folder to get the needed number of hosts. Accordingly, the 
>> riplpox recognize this increase and inserts the required flow-entries when I 
>> run it in proactive mode. Unfortunately, the added hosts can't ping each 
>> other. For example, hosts 0_0_2 can't ping the added host 0_0_4, at the same 
>> time, host 0_0_2 can ping 0_0_3.
>> The flow-entries of all the hosts are installed in the flow-table, when I 
>> checked the flow-table of the switches. Also, I tried with reactive and the 
>> same problem was faced.
>> 
>> Any body has a suggestion to solve this issue.
>> 
>> Best regards,
>> Amer

Re: [pox-dev] Riplpox with large topology

[Murphy McCauley]

Well, IIRC, riplpox stuffs topology-specific addresses into the VLAN header.  
It's possible that at larger sizes, there aren't enough bits (or that they're 
not allocated correctly).

-- Murphy

On Sep 2, 2015, at 7:47 PM, Amer  wrote:

> Thank you Murphy
> Yes, it is working correctly with the default number of host (i.e., 16 hosts).
> 
> Best regards,
> Amer 
> 
> Sent from my iPhone
> 
> On Sep 3, 2015, at 4:00 AM, Murphy McCauley  wrote:
> 
>> Did it work correctly with a smaller number of hosts before modification?
>> 
>> On Wednesday, September 2, 2015, Amer  wrote:
>> Dear All
>> 
>> The default number of hosts in riplpox is 16. I modified some commands in 
>> dctopo.py in ripl folder to get the needed number of hosts. Accordingly, the 
>> riplpox recognize this increase and inserts the required flow-entries when I 
>> run it in proactive mode. Unfortunately, the added hosts can't ping each 
>> other. For example, hosts 0_0_2 can't ping the added host 0_0_4, at the same 
>> time, host 0_0_2 can ping 0_0_3.
>> The flow-entries of all the hosts are installed in the flow-table, when I 
>> checked the flow-table of the switches. Also, I tried with reactive and the 
>> same problem was faced.
>> 
>> Any body has a suggestion to solve this issue.
>> 
>> Best regards,
>> Amer

[pox-dev] Riplpox with large topology

[Amer]

Dear All

The default number of hosts in riplpox is 16. I modified some commands in 
dctopo.py in ripl folder to get the needed number of hosts. Accordingly, the 
riplpox recognize this increase and inserts the required flow-entries when I 
run it in proactive mode. Unfortunately, the added hosts can't ping each other. 
For example, hosts 0_0_2 can't ping the added host 0_0_4, at the same time, 
host 0_0_2 can ping 0_0_3. 
The flow-entries of all the hosts are installed in the flow-table, when I 
checked the flow-table of the switches. Also, I tried with reactive and the 
same problem was faced.

Any body has a suggestion to solve this issue.

Best regards,
Amer

[pox-dev] ARP opcode

[AMER]

Dear All

I read some of the OpenFlow documentations about ARP and I only found few ARP 
opcodes are available, like ARP replay and respond and RARP two messages. I 
need to add others in my research. May you please help me in doing so.
As a first step is adding them in 


  RouteFlow/pox/pox/lib/packet/arp.py

like doing this

class arp (packet_base):

MIN_LEN = 28
HW_TYPE_ETHERNET = 1
PROTO_TYPE_IP= 0x0800
REQUEST = 1 # ARP
REPLY   = 2 # ARP
REV_REQUEST = 3 # RARP
REV_REPLY   = 4 # RARP
IN_REQUEST = 5 # INARP #< --- example
IN_REPLY   = 6 # INARP # <--- example


  
What should I do after that? may you please help me.

Best regards,   

Eng Amer Alghadhban

COE

SANS-GCFW

CEH, SCNP, CCNA