You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running hits on my router using entware. It looks like the script is getting stuck on line 115.
while [ $route_set = 1 ]; do
route_set=$(curl -4 -s "https://network.feral.io/looking-glass?action=traceroute&host=$ext_IP" | grep -c "$old_route")
done
I manually added some echos for those variables, and it looks like route_set is not getting set properly. I then ran the curl and grep commands manually with the variables filled in properly. It looks like grep returns the expected 0 value (so the script can move on), BUT, curl then outputs additional text, clobbering the results. Essentially it looks like this:
I did some Googling and was trying to see if someone else had run into curl being strange. In some futile attempts to fix this, I was able to workaround it by adding a syntax error to curl. Curl continued to run as expected, but reported a warning message.. That was apparently enough for it to continue on in the rest of the script though.
The text was updated successfully, but these errors were encountered:
i could probably put in another check in there to ensure that the step actually does what it is supposed to do... It is a bit of a weird check to begin with... I will try to come up with a better method. I have been busy lately, but I will let you know if i come up with something...
It seems like it is more with how curl is returning information. It is clobbering the rest of the output. I will try and tinker with it a bit to see if I can find a way to code around it.
I am running hits on my router using entware. It looks like the script is getting stuck on line 115.
I manually added some echos for those variables, and it looks like route_set is not getting set properly. I then ran the curl and grep commands manually with the variables filled in properly. It looks like grep returns the expected 0 value (so the script can move on), BUT, curl then outputs additional text, clobbering the results. Essentially it looks like this:
I did some Googling and was trying to see if someone else had run into curl being strange. In some futile attempts to fix this, I was able to workaround it by adding a syntax error to curl. Curl continued to run as expected, but reported a warning message.. That was apparently enough for it to continue on in the rest of the script though.
The text was updated successfully, but these errors were encountered: