Thread: XA2 - microG - Sailfish signature spoofing
View Single Post
N9x3 is offline N9x3
2019-05-18 , 02:13
Posts: 4 | Thanked: 5 times | Joined on Jan 2016
#4
Update:
The problems below was due to Docker interface being down or not working (lack of reset after installation).

Make sure you have this interface on linux after Docker installation:
Code:
docker0   Link encap:Ethernet  HWaddr 02:42:93:fb:54:4a  
          inet addr:172.17.0.1  Bcast:172.17.255.255  Mask:255.255.0.0
          inet6 addr: fe80::42:93ff:fefb:544a/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:92860 errors:0 dropped:0 overruns:0 frame:0
          TX packets:208931 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:110839908 (110.8 MB)  TX bytes:305974375 (305.9 MB)
Dear Aspergerguy,

Thank you for posting here your experience with activating signature-spoofing on XA2.

I have tried to follow your steps, and it seems, that I get stuck at connecting via rsync, which is very frustrating as I can see, that I could PING the XA2, and PING Kubuntu from XA2, but when I run docker I get rsync failed to connect:

Code:
rsync: failed to connect to 192.168.2.15 (192.168.2.15): No route to host (113)
rsync error: error in socket IO (code 10) at clientserver.c(125) [Receiver=3.1.2]
I have this regardless whether I use USB or WiFi.

Code:
krzys@kLatitude-E6430:/media/krzys/c959b919-34c0-4a1f-8e76-da927fb5a488/Sailfish_backup/sailfish-signature-spoofing-lxc$ ping 192.168.2.15
PING 192.168.2.15 (192.168.2.15) 56(84) bytes of data.
64 bytes from 192.168.2.15: icmp_seq=1 ttl=64 time=3.59 ms
64 bytes from 192.168.2.15: icmp_seq=2 ttl=64 time=4.26 ms
64 bytes from 192.168.2.15: icmp_seq=3 ttl=64 time=3.92 ms
^C
--- 192.168.2.15 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 3.599/3.930/4.265/0.271 ms
krzys@kLatitude-E6430:/media/krzys/c959b919-34c0-4a1f-8e76-da927fb5a488/Sailfish_backup/sailfish-signature-spoofing-lxc$ sudo docker run --rm -ti --env SAILFISH=192.168.2.15 --env LXC=1 haystack
[**] 1. Fetch files via RSYNC
rsync: failed to connect to 192.168.2.15 (192.168.2.15): No route to host (113)
rsync error: error in socket IO (code 10) at clientserver.c(125) [Receiver=3.1.2]
I don't know how to dig deeper into this..

Would you be so kind to put here console log of the all steps, when you will be redoing this signature spoofing after Hossa upgrade?

I have no idea, how to debug the problems with rsync inside docker.
Last edited by N9x3; 2019-05-18 at 08:01.
 

The Following 3 Users Say Thank You to N9x3 For This Useful Post: