Dear Seah, no, we really can't, since we don't understand what you're doing.
Please deliver an overview of what you are trying to implement. In my experience, a drawing (just a quick drawing on a piece of paper will do!) is often very, very helpful at illustrating complex systems like what you seem to be doing. Best regards, Marcus On 10/04/2017 12:02 AM, seah chong wrote: > hi, could you suggest any coding to implement a full protocol and > handshaking between the USRP N210. > > > On Tue, Oct 3, 2017 at 9:01 PM, Leandro Echevarría > <leoechevar...@gmail.com <mailto:leoechevar...@gmail.com>> wrote: > > Seah, are you saying that you're trying to get a wireless link > working between both USRP devices? If that is the case, and you > are not implementing a full protocol and handshaking between them > in the RF domain, they will not behave as intended (i.e., as a > pair of wireless CPEs, such as Ubiquiti Nanostations, to give an > example). > > On Tue, Oct 3, 2017 at 8:59 AM Marcus Müller via USRP-users > <usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>> > wrote: > > Sorry, I still don't understand – what circle are we talking > about? > > > On 03.10.2017 06:50, seah chong wrote: >> sorry about that, the coverage networking is weak. IP Address >> PC A is 192.168.10.1 netmask 255.255.255.0. what i means with >> Omnidirectional is actually the communication between >> the USRP is propagate within the circle. >> >> On Fri, Sep 29, 2017 at 11:31 AM, seah chong >> <seahchon...@gmail.com <mailto:seahchon...@gmail.com>> wrote: >> >> hi >> the computer connected to the device of USRP N210 using >> Communication System Toolbox Support Packages. the >> device connected using the ethernet Cable. The first and >> second USRP will communicate within omnidirectional. >> >> >> />*> findsdru >> Checking radio connections... >> >> ans = >> >> Platform: 'N200/N210/USRP2' >> IPAddress: '192.168.10.2' >> SerialNum: 'F5E4FF'*/* >> Status: 'Success'* >> >> Both USRP N210 are successfully connected to the PC but >> unable to communicate to each other. >> I also try ip route get >> >> */root@seah-Precision-T1700:~# ip route get 192.168.20.2 >> 192.168.20.2 via 20.20.20.20 dev wlan1 src 20.20.20.103 >> cache >> root@seah-Precision-T1700:~# ip route add 192.168.20.2 >> via 20.20.20.20/* >> * >> //* >> */root@seah-Precision-T1700:~# route -n >> Kernel IP routing table >> Destination Gateway Genmask Flags >> Metric Ref Use Iface >> 0.0.0.0 20.20.20.20 0.0.0.0 UG >> 0 0 0 wlan1 >> 20.20.20.0 0.0.0.0 255.255.255.0 U >> 9 0 0 wlan1 >> 192.168.10.0 0.0.0.0 255.255.255.0 U >> 0 0 0 eth0 >> 192.168.20.2 20.20.20.20 255.255.255.255 UGH >> 0 0 0 wlan1 >> /* >> * >> //* >> */root@seah-Precision-T1700:~# ping 192.168.20.2 >> PING 192.168.20.2 (192.168.20.2) 56(84) bytes of data. >> ^C >> --- 192.168.20.2 ping statistics --- >> 17 packets transmitted, 0 received, 100% packet loss, >> time 16128ms >> >> root@seah-Precision-T1700:~# ping 20.20.20.20 >> PING 20.20.20.20 (20.20.20.20) 56(84) bytes of data. >> 64 bytes from /**/20.20.20.20/* <http://20.20.20.20/>*/: >> icmp_seq=1 ttl=64 time=149 ms >> 64 bytes from /**/20.20.20.20/* <http://20.20.20.20/>*/: >> icmp_seq=3 ttl=64 time=160 ms >> 64 bytes from /**/20.20.20.20/* <http://20.20.20.20/>*/: >> icmp_seq=4 ttl=64 time=0.899 ms >> ^C >> --- 20.20.20.20 ping statistics --- >> 4 packets transmitted, 3 received, 25% packet loss, time >> 3002ms >> rtt min/avg/max/mdev = 0.899/103.625/160.323/72.769 ms/* >> * >> | I attach figure how the computer connected. I hope >> someone can enlighten me and can give me the solutions.| >> * >> *||* >> >> |Regards, | >> >> |ChongSeah| >> >> >> >> <https://mail.google.com/mail/?ui=2&ik=3bd8e0bae3&view=att&th=15ecbad4df75fc18&attid=0.1&disp=safe&realattid=f_j85c79vy0&zw> >> >> On Wed, Sep 27, 2017 at 1:30 PM, seah chong >> <seahchon...@gmail.com <mailto:seahchon...@gmail.com>> wrote: >> >> hi >> the computer connected to the device of USRP N210 >> using Communication System Toolbox Support Packages. >> the device connected using the ethernet Cable. The >> first and second USRP will communicate within >> omnidirectional. >> >> >> />*> findsdru >> Checking radio connections... >> >> ans = >> >> Platform: 'N200/N210/USRP2' >> IPAddress: '192.168.10.2' >> SerialNum: 'F5E4FF'*/* >> Status: 'Success'* >> >> Both USRP N210 are successfully connected to >> the PC but unable to communicate to each other. >> >> * >> |I hope someone can enlighten me and can give me the >> solutions.| >> ||* >> >> |Regards, | >> >> |ChongSeah| >> >> >> On Tue, Sep 26, 2017 at 9:14 PM, Leandro Echevarría >> <leoechevar...@gmail.com >> <mailto:leoechevar...@gmail.com>> wrote: >> >> Hello ChongSeah, >> >> Can you explain a little more about what your >> network configuration looks like? Maybe a drawing >> of all the network interfaces with their >> respective IPs and subnet masks may help us >> understand the problem better. >> >> How are the computers connected? And how are the >> N210s connected to them? >> >> Regards, >> >> Leo. >> >> On Tue, Sep 26, 2017 at 6:00 AM seah chong via >> USRP-users <usrp-users@lists.ettus.com >> <mailto:usrp-users@lists.ettus.com>> wrote: >> >> hi all, >> >> i have two Pc with device USRP N210. At PC A >> the IP address "192.168.10.1 netmask >> 255.255.255.0 and at PC B the IP address >> "192.168.20.1 netmask 255.255.255.0. >> i also route add at the PC A using ip route >> add 192.168.20.0/24 <http://192.168.20.0/24> >> via 192.168.10.2 and at the PC B using ip >> route add 192.168.10.0/24 >> <http://192.168.10.0/24> via 192.168.20.2.But >> i cannot ping to PC B and same too goes to PC A. >> >> >> the error comes out like below >> >> /*root@seah-Precision-T1700:~# ping 192.168.20.2 >> PING 192.168.20.2 (192.168.20.2) 56(84) bytes >> of data. >> ^C >> --- 192.168.20.2 ping statistics --- >> 3 packets transmitted, 0 received, 100% >> packet loss, time 2016ms*/ >> >> |I hope someone can enlighten me and can give >> me the solutions. | >> >> |Regards, | >> >> |ChongSeah | >> >> _______________________________________________ >> USRP-users mailing list >> USRP-users@lists.ettus.com >> <mailto:USRP-users@lists.ettus.com> >> >> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >> >> <http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com> >> >> >> >> > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com <mailto:USRP-users@lists.ettus.com> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > <http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com> > >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
