[ixpmanager] PTR for IPV6

[Jeremy Lebo]

I was able to resolve the issue, and I can confirm that the problem was 
being caused by the trailing space on the IPv6 address.  In order to 
actually get rid of the space I ended up editing the IP address in MySQL 
rather than going through the IXP UI.  Once I deleted the space from 
that field in MySQL I was able to run the command without getting the 
error message.  I can tell you when I was deleting and re-entering 
information via the web interface I did not use any information in a 
drop-down box, I typed in the full address manually and carefully 
checked it before I saved the changes.  As an experiment, I created a 
new IPv6 address with a trailing space and verified I could not delete 
it.  I tried deleting the interface it was assigned to, and also 
assigning it to a different customer, each time typing it in without the 
trailing space, but no matter what I do, if a customer tries to use that 
IP address after it's entered incorrectly, it always defaults back to 
the version with the trailing space until you either edit it or delete 
it within MySQL.  This appears to only be the case with a trailing space 
- other changes I made to intentionally screw up an address can be 
changed back within the UI.  I can place a space in the middle of an 
address and it will generate the Bad Format error, but I am able to 
remove that space successfully without having to go into MySQL.  I can 
also type garbage characters in the middle of an address and remove them.

-Jeremy


On 4/23/2014 2:24 AM, Barry O'Donovan wrote:
>
>
> On 22/04/2014 20:01, Jeremy Lebo wrote:
>> Ok, tried making the edit you suggested to the IPv6.php file, and
>> after changing line 97 we went from the error message "ERROR: Bad
>> IPv6 format" to "ERROR: Bad IPv6 format: 2607:f8b8:fff1:6566::11"
>
> For the life of me I cannot reproduce this error. Can you open a ticket
> on Github with specific step by step instructions to reproduce (assume I
> know nothing).
>
>> so we looked at the specific customer with that IPv6 address.  While
>>  looking at the customer with that IP address I realized that there
>> was a trailing space on the end of the IPv6 address entered in their
>>  VLAN interface.
>
> Right, I've added trim filters but, with and without a space, I could
> still not reproduce.
>
>> I tried to entirely disable IPv6 on their interface by unchecking
>> "IPv6 Enabled" and saving the changes but the IPv6 address still
>> showed up on their interface and the same error was generated.
>
> Checking this box just sets the database field for ipv6enabled. Hiding
> and showing the v6 details is just UI sugar. It's actually useful that
> we keep the v6 settings even if v6 is disabled.
>
>> I then deleted their VLAN interface entirely and at that point the
>> script ran, but when I tried to re-create their VLAN interface that
>> trailing space was again placed on the end of their IPv6 address
>
> Ah yes - this is because this field works in two ways:
>
> 1) shows available v6 addresses from the database (i.e I suspect it 
> was not your browser auto-filling the v6 address but it was already 
> available in the dropdown). Delete the database entry via the IP 
> Addressing option in the left hand menu.
>
> 2) if you enter an address that is not in the database, the field will 
> store it in the database for the selected VLAN.
>
>
>  - Barry
>
>
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> https://www.inex.ie/mailman/listinfo/ixpmanager