-
-
Notifications
You must be signed in to change notification settings - Fork 28
IP-Tag Redesign #172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@MickLesk Yes, no problem, I'll try to fix this error now. |
looks better for me. @community-scripts/contributor has everyone the old script installed and can test the new ? |
I do, gimme hour or two to get back home. |
Nothing gets tagged @MickLesk @DesertGamer |
@tremor021 Can you send me a screenshot of your services, since I personally use my service and everything works fine, are you sure you uploaded the latest version? |
Also, please provide the output of the command: |
|
There is a CIDR_LIST in the config, where you need to enter the internal IP address of the machines, perhaps it differs in format, which is why the script does not try to set tags for you. |
And not just the internal one, but any IP mask so that you can be assigned tags only for the right vms. |
why would i need to enter any IPs there? isn't the purpose of the script to find the ip of the lxc/vm and set it as a tag? |
this is the command used to install |
Btw, my ip range is in 192.168.0.0/16 range |
This parameter is also available in the original script and allows you not to assign an IP, for example, if you use a large number of interfaces for 1 machine, then here you specify 192.168.0.0/24, but on your car, for example, "pihole" there is also an interface with 192.168.1.0/24, then you will not see the tag from this interface, but only from what you need. You just need to specify the IP mask, and then the script will find out the IP itself and set the tags. |
I'm very confused by your logs, because you don't have an important line about the system finding LXC and VM. It should be like this
|
I have one LXC with IP of 192.168.1.11 and one VM with IP of 192.168.1.10 and both are not getting tagged.
thats more of a question for you i guess :) |
service restart gives the same error. update_all_tags does not exist |
Well, that's right, you don't have this range in your config, you need to specify 192.168.1.0/16. Add it
|
I initially explained that you should set the IP range yourself so that the script can assign tags to you. |
192.168.1.0/24 is in 192.168.0.0/16... its either my english or i'm not getting this at all |
Wait a second, I'm going to check the mask verification algorithm, it's good that you noticed this) |
Update got it to tag the LXC
VM is not getting tagged tho |
I actually found a small error, fixed it, try it, everything worked as it should. This must be uploaded to /opt/iptag/iptag
|
VM is not tagged though |
Can you tell me, please, is the VM running? Does it have an interface? |
Oh, you provided the logs above and the script apparently thinks that you have an empty IP address for the machine, I have now processed this exception, let's see what the logs will give.
|
I will clarify in advance that I never caught this error during my tests and am surprised that it happened at all. I also saw that according to your previous logs, you had the XXX.XXX format, and now XXX, have you changed it? If you changed it in the iptag.conf file, then try using a different format, for example last_two_octets, maybe then this error won't happen and it's about the format. |
@DesertGamer can you push all latest changes into live PR? |
@MickLesk I'm sorry, I don't understand much English and the word "PR" is unclear to me, can you explain what I need to do? |
Push all of your Changes from VED in VE in your Draft PR (Pull Request): community-scripts/ProxmoxVE#3531 |
@MickLesk Thanks for explaining, I sent the commit. |
First Update:
Second Execute:
@DesertGamer can you take a look?
The text was updated successfully, but these errors were encountered: