ifup has different output than expected by the "parse_ifup_output()"
Opened this issue · 10 comments
ifup --version
ifup version 0.7~beta2ubuntu11.1
The output of ifup looks like something in below:
ssh stop/waiting
ssh start/running, process 3899
If I understand correctly, parse_ifup_output() expect "ip_address". In this case, parse_ifup_output() will always return error because there is no ip_address print out even the interface is running.
woah,
that's weird.
Here's my ifup version:
$ sudo ifup --version
ifup version 0.7.44
Copyright (c) 1999-2007 Anthony Towns
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or (at
your option) any later version.
Do you have any special configuration in your /etc/network/interfaces? I don't know why ifup is running ssh. Are you running a VPN?
Hi, Thanks for quick response.
I run the ifup manually. More detailed output in below:
root@prodtest-198-59:/home/prodtest# /sbin/ifup wlan0=wlan0-test -o wpa-psk=b34735bcb1c245d002648ffc31c7b4b67162d8871ce6b0608d1e50dc56094fb1 -o wpa-ssid=GNX30FB80 -o wireless-channel=auto
ssh stop/waiting
ssh start/running, process 15648
I do NOT have VPN running. But I do ssh access to this PC. There are NO special configurations in /etc/network/interfaces.
I don't really know the reason why ifup is running ssh. What I understand is when the new network interface is up, ssh deamon will active and add it. Maybe that is why we see ssh stop and start again. But if it is true, you should also see this output as well. So puzzel~~~.
hi @luan0ma,
I'm sorry, I really don't have any idea what could be causing that sort of output. I suppose we should add support for that into wifi. Just for the record, when you do connect like that, does it actually work? Are you connected to the wifi network?
Hi @luan0ma,
I have created a pull request that changes how Scheme determines whether the connection was successful or not. Can you try them out? The pull request is #44.
Thanks.
Hi,
The wifi works even the ifup output doesn't. I have got ip address and can ping to it.
I will test your fix and let you know ASAP. Thanks for the fix anyway.
Hi,
I have pull the branch "status_command" and test it. It seems working fine now. Thanks.
Just want to weigh in here. Could this be caused by the fact that @luan0ma is using a beta version of ifup? Hence it might have bugs in it...
Have you experienced the same bug?
-rocky
2014年9月15日 上午8:52于 "GusBricker" notifications@github.com写道：
Just want to weigh in here. Could this be caused by the fact that @luan0ma
https://github.com/luan0ma is using a beta version of ifup? Hence it
might have bugs in it...—
Reply to this email directly or view it on GitHub
#43 (comment).
@rockymeza Nope, just find it odd that @luan0ma has a beta version of ifup and is lodging a bug based on its output. However I guess it could be argued that the output could be parsed in a way that makes it disregard anomalies like this (to a certain extent).
I hope that is the issue. @luan0ma, are you still experiencing this problem?
-rocky
On Mon, Sep 15, 2014 at 12:21 AM, GusBricker notifications@github.com
wrote:
@rockymeza https://github.com/rockymeza Nope, just find it odd that
@luan0ma https://github.com/luan0ma has a beta version of ifup and is
lodging a bug based on its output. However I guess it could be argued that
the output could be parsed in a way that makes it disregard anomalies like
this (to a certain extent).—
Reply to this email directly or view it on GitHub
#43 (comment).