Bug#898672: iodine: iodine-client-start reports local address in seconds, e.g. as "7128sec"

2018-05-15 Thread gregor herrmann
On Tue, 15 May 2018 18:00:42 +0200, gregor herrmann wrote: > On Tue, 15 May 2018 16:51:30 +0100, Barak A. Pearlmutter wrote: > > Okay, I pushed another fix to avoid all use of ifconfig and instead use ip. > > Please let me know if it's okay. > Thanks, works perfectly for me. > > Axel, maybe you

Bug#898672: iodine: iodine-client-start reports local address in seconds, e.g. as "7128sec"

2018-05-15 Thread gregor herrmann
On Tue, 15 May 2018 16:51:30 +0100, Barak A. Pearlmutter wrote: > Okay, I pushed another fix to avoid all use of ifconfig and instead use ip. > Please let me know if it's okay. Thanks, works perfectly for me. Axel, maybe you could try https://github.com/barak/iodine-client-start as and check if

Bug#898672: iodine: iodine-client-start reports local address in seconds, e.g. as "7128sec"

2018-05-15 Thread Barak A. Pearlmutter
Okay, I pushed another fix to avoid all use of ifconfig and instead use ip. Please let me know if it's okay.

Bug#898672: iodine: iodine-client-start reports local address in seconds, e.g. as "7128sec"

2018-05-15 Thread gregor herrmann
On Tue, 15 May 2018 11:22:24 +0200, Axel Beckert wrote: > > Maybe "-oneline" would be helpful? > > > > % ip -4 -oneline addr show dev eth0 scope global > > I've put -oneline into that line which starts with "addr=$(" and > changed $2 to $4 in the awk command. That sufficed to fix the display >

Bug#898672: iodine: iodine-client-start reports local address in seconds, e.g. as "7128sec"

2018-05-15 Thread gregor herrmann
On Tue, 15 May 2018 13:01:47 +0100, Barak A. Pearlmutter wrote: > Okay, I switched to ip -oneline throughout the script, see > https://github.com/barak/iodine-client-start Thank you, much appreciated! Do you also have an idea for the other issue, mentioned in my reply from yesterday: |

Bug#898672: iodine: iodine-client-start reports local address in seconds, e.g. as "7128sec"

2018-05-15 Thread Barak A. Pearlmutter
Okay, I switched to ip -oneline throughout the script, see https://github.com/barak/iodine-client-start I would have tried to push a fix, but the packaging repo is not on salsa but another place. Written with a git: URL but when I switched to https: it worked fine, so maybe the lintian override

Bug#898672: iodine: iodine-client-start reports local address in seconds, e.g. as "7128sec"

2018-05-15 Thread Axel Beckert
Hi gregor, gregor herrmann wrote: > % ip -4 addr show dev eth0 scope global | tail -1 | awk '{print $2}' > forever > > "forever" doesn't sound like a typical IPv4 address either but it > somehow matches your 7128sec (in the sense that it's a duration, and > my static vs. your (probably) DHCP

Bug#898672: iodine: iodine-client-start reports local address in seconds, e.g. as "7128sec"

2018-05-14 Thread gregor herrmann
Control: tag -1 + confirmed On Mon, 14 May 2018 22:43:52 +0200, Axel Beckert wrote: Hi Axel, and thanks for your bug report. I'm putting Barak in the loop as the author of the iodine-client-start helper script. > But what is odd is what iodine-client-start reports to me when starting > up: >

Bug#898672: iodine: iodine-client-start reports local address in seconds, e.g. as "7128sec"

2018-05-14 Thread Axel Beckert
Package: iodine Version: 0.7.0-7 Hi, I can't get any iodine connection working with a wifi where DNS seems to report the correct addresses for at least one of my machines. It may be caused by some restrictions of that network, so this is not a "does not work at all" report. (And I currently