date:20160322

Re: [tipc-discussion] Please, help - no connection

2016-03-22 Thread Jon Maloy

Hi Leon,
No wonder it  wasn't working ;) 
Yes, -be is obligatory. That is how you tell TIPC which interface(s) to use for 
communication with other nodes.
But again, -netid is not needed.

///jon


From: Leon Pollak [mailto:le...@plris.com] 
Sent: Tuesday, 22 March, 2016 08:31
To: Jon Maloy
Cc: Richard Alpe; tipc-discussion@lists.sourceforge.net
Subject: Re: [tipc-discussion] Please, help - no connection

On Tuesday 22 March 2016 12:27:07 Jon Maloy wrote:
> Hi Leon,
> Netid was never obligatory. It has a default value of 4711, and will use 
> that if no other value is explicitly set. Personally, I practically never 
> set it.
> So, to me it sounds like you still have a problem.
 
As for now, the system seems to work as required.
The change was to use:
tipc-config -netid=1234 -addr=1.1.X -be=eth:eth0
instead of non-working variant:
tipc-config -addr=1.1.X
 
>From what you say the '-be' is obligatory in my case?
 
-- 
Leon

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
___
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion

Re: [tipc-discussion] tipc nametable update problem

2016-03-22 Thread Rune Torgersen

Still having nametable update problems (Using TIPC_CLUSTER_SCOPE)

Here is an except of tipc-config -nt on both systems:
address 1.1.1:

1041025   1025   <1.1.1:3540751351> 3540751351  cluster
10465537  65537  <1.1.1:4046699456> 4046699456  cluster
104131073 131073 <1.1.2:59828181>   59828181cluster
10416777984   16777984   <1.1.1:3135589675> 3135589675  cluster
10433555200   33555200   <1.1.2:2193437365> 2193437365  cluster

Address 1.1.2:
104131073 131073 <1.1.2:59828181>   59828181cluster
10433555200   33555200   <1.1.2:2193437365> 2193437365  cluster

So in this case 1 sees all address 2 has published, while 2 is not seeing the 
addesses from 1.
2 was rebooted to make this happen.

Is tere a possibility I'm calling tipc-config too early, and the interface is 
not yet up, or is this still the same roblem I saw before.

There is nome dropped nametable update messages in kernel:

Mar 22 10:34:34 mitchelltelctrl2 kernel: Dropping name table update (0) of {0, 
0, 0} from <1.1.1> key=0
Mar 22 10:34:34 mitchelltelctrl2 kernel: Dropping name table update (0) of {0, 
0, 0} from <1.1.1> key=0
Mar 22 10:34:34 mitchelltelctrl2 kernel: Dropping name table update (0) of {0, 
0, 0} from <1.1.1> key=0
Mar 22 10:34:34 mitchelltelctrl2 kernel: Dropping name table update (0) of {0, 
0, 0} from <1.1.1> key=0
Mar 22 10:34:34 mitchelltelctrl2 kernel: Dropping name table update (0) of {0, 
0, 0} from <1.1.1> key=0
Mar 22 10:34:34 mitchelltelctrl2 kernel: Dropping name table update (0) of {0, 
0, 0} from <1.1.1> key=0
Mar 22 10:34:34 mitchelltelctrl2 kernel: Dropping name table update (0) of {0, 
0, 0} from <1.1.1> key=0
Mar 22 10:34:34 mitchelltelctrl2 kernel: Dropping name table update (0) of {0, 
0, 0} from <1.1.1> key=0
Mar 22 10:34:34 mitchelltelctrl2 kernel: Dropping name table update (0) of {0, 
0, 0} from <1.1.1> key=0
Mar 22 10:34:34 mitchelltelctrl2 kernel: Dropping name table update (0) of {0, 
0, 16600} from <1.1.1> key=4294915584

but they do not mention port 104.

If I restart the application on 1 having 104:1025 open, it shows up on 2.

-Original Message-
From: Rune Torgersen [mailto:ru...@innovsys.com] 
Sent: Monday, March 21, 2016 12:17 AM
To: Jon Maloy; Erik Hugne
Cc: tipc-discussion@lists.sourceforge.net
Subject: Re: [tipc-discussion] tipc nametable update problem

Using TIPC_CLUSTER_SCOPE will work.
This was new system bring-up, and code was ported from older system, which used 
TIPC 1.7.7 driver.
A quick search and replace of TIPC_ZONE_SCOPE is not a bad workaround.

From: Jon Maloy [jon.ma...@ericsson.com]
Sent: Saturday, March 19, 2016 10:57 AM
To: Erik Hugne
Cc: tipc-discussion@lists.sourceforge.net
Subject: Re: [tipc-discussion] tipc nametable update problem

Maybe not completely trivial, but not very complex either. I know I failed to 
describe this verbally to you at one moment, but I can put it on paper, and you 
will realize it is not a big deal.
If you or anybody else are interested I can make an effort to describe this 
next week. I don't have time to implement it myself at the moment.

///jon

From: Erik Hugne [mailto:erik.hu...@gmail.com]
Sent: Friday, 18 March, 2016 12:38
To: Jon Maloy
Subject: RE: [tipc-discussion] tipc nametable update problem

Agree.
But implementing a new lookup mechanism is not trivial.. :)

@Rune afaik there is no functional limitation on using cluster scoped 
publications, so i hope that's an acceptable workaround for you.

//E
On Mar 18, 2016 16:46, "Jon Maloy" 
mailto:jon.ma...@ericsson.com>> wrote:
Still weird that this starts happening now, when this issue is supposed to be 
remedied, and not earlier, when it wasn't.
We really need that "permit overlapping publications"  solution I have been 
preaching about.

Br
///jon

> -Original Message-
> From: Rune Torgersen [mailto:ru...@innovsys.com]
> Sent: Friday, 18 March, 2016 10:25
> To: 'Erik Hugne'
> Cc: 
> tipc-discussion@lists.sourceforge.net
> Subject: Re: [tipc-discussion] tipc nametable update problem
>
> Yes I have.
> There are quite a few at the same time like this:
>
> Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of 
> {1853110816,
> 1952998688, 1801810542} from <1.1.1> key=1633905523
> Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of 
> {542000723,
> 544613732, 544437616} from <1.1.1> key=167800175
> Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of 
> {544239474,
> 1953325424, 543582572} from <1.1.1> key=1930035237
> Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of 
> {1933189232,
> 1869771885, 1634738291} from <1.1.1> key=1768843040
> Mar 17 20:08:58 restarttv kernel: Dropping name table update (0) of 
> {1717660012,
> 1701054976, 628308512} from <1.1.1

Re: [tipc-discussion] TIPC nametable NULL ptr kernel crash

2016-03-22 Thread Parthasarathy Bhuvaragan

Hi,

This bug is fixed in commit: 
d4091899c9bbfd6695449c6b09517ceb45bb379d "(tipc: hold subscriber->lock for 
tipc_nametbl_subscribe())", which is in v4.5-rc2-216..

Your kernel version is 4.4.0-14-generic, so this fix is missing.

regards
Partha

From: Rune Torgersen [ru...@innovsys.com]
Sent: 22 March 2016 15:33
To: tipc-discussion@lists.sourceforge.net
Subject: [tipc-discussion] TIPC nametable NULL ptr kernel crash

Hi, I've experienced a few reboots lately, and filally got a crash kernel going 
to catch the cause.
Not sure how this happens, but I got a NULL ptr derefenrece in the tipc 
nametable.

[72369.896602] BUG: unable to handle kernel NULL pointer dereference at 
00b7
[72369.896742] IP: [] tipc_nametbl_unsubscribe+0x72/0x100 
[tipc]
[72369.896851] PGD 0
[72369.896928] Oops: 0002 [#1] SMP
[72369.897043] Modules linked in: tipc ip6_udp_tunnel udp_tunnel ip_vs 
nf_conntrack cls_fw sch_sfq sch_htb xt_CLASSIFY xt_multiport iptable_mangle 
ip_tables x_tables ipmi_devintf ipmi_ssif x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd sb_edac serio_raw 
edac_core input_leds joydev lpc_ich mei_me mei ioatdma dca ipmi_si shpchp 
8250_fintek ipmi_msghandler mac_hid quota_v2 quota_tree lp parport autofs4 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid psmouse 
isci ahci libsas e1000e libahci scsi_transport_sas ptp pps_core wmi fjes
[72369.900205] CPU: 0 PID: 4129 Comm: kworker/u24:2 Not tainted 
4.4.0-14-generic #30-Ubuntu
[72369.900271] Hardware name: Supermicro X9SRL-F/X9SRL-F, BIOS 3.2 01/16/2015
[72369.900325] Workqueue: tipc_rcv tipc_recv_work [tipc]
[72369.900407] task: 880c43720dc0 ti: 8801ee78c000 task.ti: 
8801ee78c000
[72369.900471] RIP: 0010:[]  [] 
tipc_nametbl_unsubscribe+0x72/0x100 [tipc]
[72369.900603] RSP: 0018:880c4f203e10  EFLAGS: 00010246
[72369.900675] RAX: 8804648c2080 RBX: 8804648c2000 RCX: 00af
[72369.900737] RDX:  RSI: 00ce RDI: 880c34ab7998
[72369.900800] RBP: 880c4f203e30 R08: 880c4f216d40 R09: 0001
[72369.900883] R10: 0005 R11:  R12: 880c34ab7960
[72369.900946] R13: 880c459df120 R14: 880c34ab7998 R15: 8804648c2000
[72369.901010] FS:  () GS:880c4f20() 
knlGS:
[72369.901089] CS:  0010 DS:  ES:  CR0: 80050033
[72369.901159] CR2: 00b7 CR3: 01e0a000 CR4: 001406f0
[72369.901222] Stack:
[72369.901276]  8804648c2000 880c459de000 880101613348 
c044dd90
[72369.901510]  880c4f203e50 c044d77f 8804648c2000 
880101613340
[72369.901731]  880c4f203e78 c044ddd5 880c4f20dd00 
8804648c2030
[72369.901963] Call Trace:
[72369.902019]  
[72369.902079]  [] ? tipc_subscrb_shutdown_cb+0xc0/0xc0 [tipc]
[72369.902195]  [] tipc_subscrp_delete+0x2f/0x80 [tipc]
[72369.902261]  [] tipc_subscrp_timeout+0x45/0x70 [tipc]
[72369.902334]  [] call_timer_fn+0x35/0x120
[72369.902410]  [] ? tipc_subscrb_shutdown_cb+0xc0/0xc0 [tipc]
[72369.902475]  [] run_timer_softirq+0x23a/0x2f0
[72369.902544]  [] __do_softirq+0x101/0x290
[72369.902606]  [] irq_exit+0xa3/0xb0
[72369.902682]  [] smp_apic_timer_interrupt+0x42/0x50
[72369.902749]  [] apic_timer_interrupt+0x82/0x90
[72369.902811]  
[72369.902854]  [] ? _raw_spin_unlock_irqrestore+0x15/0x20
[72369.902982]  [] mod_timer+0x10f/0x240
[72369.903046]  [] tipc_subscrb_rcv_cb+0x1c0/0x390 [tipc]
[72369.903112]  [] tipc_receive_from_sock+0xc2/0x120 [tipc]
[72369.903192]  [] tipc_recv_work+0x2b/0x60 [tipc]
[72369.903260]  [] process_one_work+0x162/0x480
[72369.903322]  [] worker_thread+0x4b/0x4c0
[72369.903388]  [] ? process_one_work+0x480/0x480
[72369.903450]  [] ? process_one_work+0x480/0x480
[72369.903514]  [] kthread+0xd8/0xf0
[72369.903575]  [] ? kthread_create_on_node+0x1e0/0x1e0
[72369.903639]  [] ret_from_fork+0x3f/0x70
[72369.903700]  [] ? kthread_create_on_node+0x1e0/0x1e0
[72369.903762] Code: ff ff 48 85 c0 74 56 4c 8d 70 38 49 89 c4 4c 89 f7 e8 03 
d9 3c c1 48 8b 8b 80 00 00 00 48 8b 93 88 00 00 00 48 8d 83 80 00 00 00 <48> 89 
51 08 48 89 0a 48 89 83 80 00 00 00 48 89 83 88 00 00 00
[72369.906299] RIP  [] tipc_nametbl_unsubscribe+0x72/0x100 
[tipc]
[72369.906430]  RSP 
[72369.906486] CR2: 00b7

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
___
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourcef

[tipc-discussion] TIPC nametable NULL ptr kernel crash

2016-03-22 Thread Rune Torgersen

Hi, I've experienced a few reboots lately, and filally got a crash kernel going 
to catch the cause.
Not sure how this happens, but I got a NULL ptr derefenrece in the tipc 
nametable.

[72369.896602] BUG: unable to handle kernel NULL pointer dereference at 
00b7
[72369.896742] IP: [] tipc_nametbl_unsubscribe+0x72/0x100 
[tipc]
[72369.896851] PGD 0 
[72369.896928] Oops: 0002 [#1] SMP 
[72369.897043] Modules linked in: tipc ip6_udp_tunnel udp_tunnel ip_vs 
nf_conntrack cls_fw sch_sfq sch_htb xt_CLASSIFY xt_multiport iptable_mangle 
ip_tables x_tables ipmi_devintf ipmi_ssif x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd sb_edac serio_raw 
edac_core input_leds joydev lpc_ich mei_me mei ioatdma dca ipmi_si shpchp 
8250_fintek ipmi_msghandler mac_hid quota_v2 quota_tree lp parport autofs4 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid psmouse 
isci ahci libsas e1000e libahci scsi_transport_sas ptp pps_core wmi fjes
[72369.900205] CPU: 0 PID: 4129 Comm: kworker/u24:2 Not tainted 
4.4.0-14-generic #30-Ubuntu
[72369.900271] Hardware name: Supermicro X9SRL-F/X9SRL-F, BIOS 3.2 01/16/2015
[72369.900325] Workqueue: tipc_rcv tipc_recv_work [tipc]
[72369.900407] task: 880c43720dc0 ti: 8801ee78c000 task.ti: 
8801ee78c000
[72369.900471] RIP: 0010:[]  [] 
tipc_nametbl_unsubscribe+0x72/0x100 [tipc]
[72369.900603] RSP: 0018:880c4f203e10  EFLAGS: 00010246
[72369.900675] RAX: 8804648c2080 RBX: 8804648c2000 RCX: 00af
[72369.900737] RDX:  RSI: 00ce RDI: 880c34ab7998
[72369.900800] RBP: 880c4f203e30 R08: 880c4f216d40 R09: 0001
[72369.900883] R10: 0005 R11:  R12: 880c34ab7960
[72369.900946] R13: 880c459df120 R14: 880c34ab7998 R15: 8804648c2000
[72369.901010] FS:  () GS:880c4f20() 
knlGS:
[72369.901089] CS:  0010 DS:  ES:  CR0: 80050033
[72369.901159] CR2: 00b7 CR3: 01e0a000 CR4: 001406f0
[72369.901222] Stack:
[72369.901276]  8804648c2000 880c459de000 880101613348 
c044dd90
[72369.901510]  880c4f203e50 c044d77f 8804648c2000 
880101613340
[72369.901731]  880c4f203e78 c044ddd5 880c4f20dd00 
8804648c2030
[72369.901963] Call Trace:
[72369.902019]   
[72369.902079]  [] ? tipc_subscrb_shutdown_cb+0xc0/0xc0 [tipc]
[72369.902195]  [] tipc_subscrp_delete+0x2f/0x80 [tipc]
[72369.902261]  [] tipc_subscrp_timeout+0x45/0x70 [tipc]
[72369.902334]  [] call_timer_fn+0x35/0x120
[72369.902410]  [] ? tipc_subscrb_shutdown_cb+0xc0/0xc0 [tipc]
[72369.902475]  [] run_timer_softirq+0x23a/0x2f0
[72369.902544]  [] __do_softirq+0x101/0x290
[72369.902606]  [] irq_exit+0xa3/0xb0
[72369.902682]  [] smp_apic_timer_interrupt+0x42/0x50
[72369.902749]  [] apic_timer_interrupt+0x82/0x90
[72369.902811]   
[72369.902854]  [] ? _raw_spin_unlock_irqrestore+0x15/0x20
[72369.902982]  [] mod_timer+0x10f/0x240
[72369.903046]  [] tipc_subscrb_rcv_cb+0x1c0/0x390 [tipc]
[72369.903112]  [] tipc_receive_from_sock+0xc2/0x120 [tipc]
[72369.903192]  [] tipc_recv_work+0x2b/0x60 [tipc]
[72369.903260]  [] process_one_work+0x162/0x480
[72369.903322]  [] worker_thread+0x4b/0x4c0
[72369.903388]  [] ? process_one_work+0x480/0x480
[72369.903450]  [] ? process_one_work+0x480/0x480
[72369.903514]  [] kthread+0xd8/0xf0
[72369.903575]  [] ? kthread_create_on_node+0x1e0/0x1e0
[72369.903639]  [] ret_from_fork+0x3f/0x70
[72369.903700]  [] ? kthread_create_on_node+0x1e0/0x1e0
[72369.903762] Code: ff ff 48 85 c0 74 56 4c 8d 70 38 49 89 c4 4c 89 f7 e8 03 
d9 3c c1 48 8b 8b 80 00 00 00 48 8b 93 88 00 00 00 48 8d 83 80 00 00 00 <48> 89 
51 08 48 89 0a 48 89 83 80 00 00 00 48 89 83 88 00 00 00 
[72369.906299] RIP  [] tipc_nametbl_unsubscribe+0x72/0x100 
[tipc]
[72369.906430]  RSP 
[72369.906486] CR2: 00b7

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
___
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion

Re: [tipc-discussion] Please, help - no connection

2016-03-22 Thread Leon Pollak

On Tuesday 22 March 2016 12:27:07 Jon Maloy wrote:
> Hi Leon,
> Netid was never obligatory.  It has a default value of 4711, and will use 
> that if no other value is explicitly set. Personally, I practically never 
> set it.
> So, to me it sounds like you still have a problem.

As for now, the system seems to work as required.
The change was to use:
tipc-config -netid=1234 -addr=1.1.X -be=eth:eth0
instead of non-working variant:
tipc-config -addr=1.1.X

>From what you say the '-be' is obligatory in my case?

-- 
Leon
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
___
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion

Re: [tipc-discussion] Please, help - no connection

2016-03-22 Thread Jon Maloy

Hi Leon,
Netid was never obligatory.  It has a default value of 4711, and will use that 
if no other value is explicitly set. Personally, I practically never set it.
So, to me it sounds like you still have a problem.

///jon


From: Leon Pollak [mailto:le...@plris.com]
Sent: Tuesday, 22 March, 2016 04:39
To: Jon Maloy
Cc: Richard Alpe; tipc-discussion@lists.sourceforge.net
Subject: Re: [tipc-discussion] Please, help - no connection


Thank you very much both Richard and Jon.



I found the problem - it was that I missed the netid parameter in tipc-config 
call.

I did not notice that I need it in the manual example, while my all previous 
development worked fine inside the same machine.



May be it will be useful to add some kind of control for this parameter absence 
in the tool - it's necessity/obligatory is not obvious...



Again, thanks a lot for the help!!!





On Monday 21 March 2016 13:27:55 Jon Maloy wrote:

> Richard, this is kernel 2.6.37. I doubt very much that the 'tipc' tool will 
> work with that kernel version. Correct me if I am wrong.

> Anyway, I am pretty sure that the choice of tool is not the issue here; to 
> try changing it would just cause him unnecessary extra work.

>

>

> Leon, just a control question: since you are indicating your IP addresses, I 
> hope this doesn't mean you are trying to configure an IP bearer. This isn't 
> supported in the TIPC version you are using; it came a lot later.

>

> I would start doing the following:

> What does tipc-config say about the bearers? Have they been correctly 
> enabled? Do the nodes have the addresses you have set?

> Does Wireshark show that the discovery messages are transferred and responded 
> to as they should ?

> If not, since you are anyway hacking the code, why not throw in a couple of 
> printouts to verify what happens to those messages in the code. It is the 
> disabling of the disc_domain test that makes me suspicious. I this test 
> replaced bay an unconditional "true" (it should be) ?

>

> Try this, and chances are good you will find what is missing.

>

> Regards

> ///jon

>

> > -Original Message-

> > From: Richard Alpe [mailto:richard.a...@ericsson.com]

> > Sent: Monday, 21 March, 2016 04:06

> > To: Leon Pollak; 
> > tipc-discussion@lists.sourceforge.net

> > Subject: Re: [tipc-discussion] Please, help - no connection

> >

> > Hi Leon,

> >

> > On 2016-03-20 13:32, Leon Pollak wrote:

> > > I have 2 Linux 2.6.37 embedded ARM computers with TIPC compiled-in.

> > >

> > > IP1=192.168.1.1

> > > TIPC1=1.1.1

> > >

> > > IP2=192.168.1.2

> > > TIPC2=1.1.2

> > >

> > > Both addresses were assigned with tipc-config utility, which was cross-

> > > compiled for the case. Compilation failed at first (because of kernel

> > > version?) with the errors, which were solved as following:

> > > - function show_stat() was masked out;

> > > - function enable_bearer() reference to the field disk_domain was 
> > > commented

> > > out.

> > This tool is deprecated. I would suggest using the "tipc" tools present in 
> > the

> > iproute2 package.

> >

> > > Running connection-demo on each one of the computers works fine.

> > > Running client on 2 and server on 1 fails with timeout.

> > > Ping, obviously, works between them.

> > Can you try running the PTTS test?

> >

> > Regards

> > Richard

> >

--

Leon
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
___
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion

[tipc-discussion] tipcutils build fixes

2016-03-22 Thread Jean Parpaillon

Dear all,
I have fixed some bugs in the production of tipcutils releases. Now,
the utils pass the 'make distcheck' test.

I have put my changes in a separate repos:
https://github.com/jeanparpaillon/tipcutils

How can we merge the changes ?

Regards,##SELECTION_END##
-- 
Jean Parpaillon
--
Director @ OW2 Consortium
OCCIware Strategic Orientation Committee Chairman
Research Engineer @ Inria
--
Phone: +33 6 30 10 92 86
im: jean.parpail...@gmail.com
skype: jean.parpaillon
linkedin: http://www.linkedin.com/in/jeanparpaillon/en
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
___
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion

Re: [tipc-discussion] Please, help - no connection

2016-03-22 Thread Leon Pollak

Thank you very much both Richard and Jon.

I found the problem - it was that I missed the netid parameter in tipc-config 
call.
I did not notice that I need it in the manual example, while my all previous 
development worked fine inside the same machine.

May be it will be useful to add some kind of control for this parameter 
absence in the tool - it's necessity/obligatory is not obvious...

Again, thanks a lot for the help!!!


On Monday 21 March 2016 13:27:55 Jon Maloy wrote:
> Richard, this is kernel 2.6.37.  I doubt very much that the 'tipc' tool will 
work with that kernel version. Correct me if I am wrong.
> Anyway, I am pretty sure that the choice of tool is not the issue here; to 
try changing it would just cause him unnecessary extra work.
> 
> 
> Leon, just a control question: since you are indicating your IP addresses, I 
hope this doesn't mean you are trying to configure an IP bearer. This isn't 
supported in the TIPC version you are using; it came a lot later.
> 
> I would start doing the following:
> What does tipc-config say about the bearers? Have they been correctly 
enabled? Do the nodes have the addresses you have set?
> Does Wireshark show that the discovery messages are transferred and 
responded to as they should ?
> If not, since you are anyway hacking the code, why not throw in a couple of 
printouts to verify what happens to those messages in the code. It is the 
disabling of the disc_domain test that makes me suspicious. I this test 
replaced bay an unconditional "true" (it should be) ?
> 
> Try this, and chances are good you will find what is missing.
> 
> Regards
> ///jon
> 
> > -Original Message-
> > From: Richard Alpe [mailto:richard.a...@ericsson.com]
> > Sent: Monday, 21 March, 2016 04:06
> > To: Leon Pollak; tipc-discussion@lists.sourceforge.net
> > Subject: Re: [tipc-discussion] Please, help - no connection
> > 
> > Hi Leon,
> > 
> > On 2016-03-20 13:32, Leon Pollak wrote:
> > > I have 2 Linux 2.6.37 embedded ARM computers with TIPC compiled-in.
> > >
> > > IP1=192.168.1.1
> > > TIPC1=1.1.1
> > >
> > > IP2=192.168.1.2
> > > TIPC2=1.1.2
> > >
> > > Both addresses were assigned with tipc-config utility, which was cross-
> > > compiled for the case. Compilation failed at first (because of kernel
> > > version?) with the errors, which were solved as following:
> > > - function show_stat() was masked out;
> > > - function enable_bearer() reference to the field disk_domain was 
commented
> > > out.
> > This tool is deprecated. I would suggest using the "tipc" tools present in 
the
> > iproute2 package.
> > 
> > > Running connection-demo on each one of the computers works fine.
> > > Running client on 2 and server on 1 fails with timeout.
> > > Ping, obviously, works between them.
> > Can you try running the PTTS test?
> > 
> > Regards
> > Richard
> > 
-- 
Leon
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
___
tipc-discussion mailing list
tipc-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tipc-discussion

Re: [tipc-discussion] Please, help - no connection

Re: [tipc-discussion] tipc nametable update problem

Re: [tipc-discussion] TIPC nametable NULL ptr kernel crash

[tipc-discussion] TIPC nametable NULL ptr kernel crash

Re: [tipc-discussion] Please, help - no connection

Re: [tipc-discussion] Please, help - no connection

[tipc-discussion] tipcutils build fixes

Re: [tipc-discussion] Please, help - no connection

8 matches

Site Navigation

Mail list logo

Footer information