[RPKI] Fwd: Routinator memory usage

[Stavros Konstantaras]

Hi Martin,

For Junos the state should be “UP” and show the uptime of the connection instead of “connect.

@Yasir, can you check on your Juniper router the ACL of your management interface to see if you allow the IP + port of your Routinator instance ? If that looks good, can you check your iptables config on your Routinator’s server for any misconfiguration? 


Best regards,

Stavros Konstantaras | NOC Engineer | AMS-IX 
M +31 (0) 620 89 51 04 | T +31 20 305 8999
ams-ix.net

> On 23 Oct 2019, at 14:01, Martin Hoffmann <martin at nlnetlabs.nl> wrote:
> 
> Hi Yasir,
> 
> this looks like everything is working as expected? Router is connected
> and Routinator is listening on 3323?
> 
> Kind regards,
> Martin
> 
> Muhammad Yasir Shamim wrote:
>> Hi
>> 
>> On Junos its showing in connect state.
>> 
>> validation {
>>    group rpki {
>>        session 124.29.243.110 {
>>            refresh-time 30;
>>            port 3323;
>> 
>> show validation session
>> Session                                  State   Flaps     Uptime
>> #IPv4/IPv6 records
>> 124.29.243.110                           Connect     0            0/0
>> 
>> whereas on the server it is listening on on port 3323.
>> 
>> tcp        0      0 124.29.243.110:3323     0.0.0.0:*
>> LISTEN -
>> 
>> Please assist.
>> 
>> Regards
>> Yasir
>> 
>> On Wed, Oct 23, 2019 at 2:11 AM Muhammad Yasir Shamim <
>> muhammadyasirshamim at gmail.com> wrote:  
>> 
>>> Hi Martin
>>> 
>>> I verify it and nothing have been listening on that port, only the
>>> server IP is listening the DNS queries on port 53. Due to limited
>>> access I wouldn't be able to share the output. What are the other
>>> possibilities of having an os error 98.
>>> 
>>> Regards
>>> Yasir
>>> 
>>> On Tue, Oct 22, 2019 at 5:24 PM Martin Hoffmann
>>> <martin at nlnetlabs.nl> wrote:
>>> 
>>>> Hi,
>>>> 
>>>> Muhammad Yasir Shamim wrote:  
>>>>>> 
>>>>>> I am getting an error while establishing a session between with
>>>>>> Routinator.
>>>>>> 
>>>>>> routinator server --rtr 124.29.243.110:3323 --refresh=300  
>>>>>> -------------------------------------> 124.29.243.110:3323  is
>>>>>> the routinator server IP. Failed to bind RTR listener
>>>>>> 124.29.243.110:3323: Address already in use (os error 98)  
>>>> 
>>>> This typically means that there is already something on your
>>>> machine listening on that port. You can find out the process ID of
>>>> that by running "netstat -lntp" as root.
>>>> 
>>>> HTH and kind regards,
>>>> Martin
>>>> 
>>> 
>>> 
>>> 
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>>
>>> Virus-free. www.avast.com <http://www.avast.com/>
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>>
>>> <#m_-3477448137726928605_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>> 
> 
> -- 
> RPKI mailing list
> RPKI at nlnetlabs.nl <mailto:RPKI at nlnetlabs.nl>
> https://www.nlnetlabs.nl/mailman/listinfo/rpki <https://www.nlnetlabs.nl/mailman/listinfo/rpki>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/rpki/attachments/20191023/1e0ec356/attachment.htm>