RARE user and assistance email list

[mc36 <>]

tbh i stopped looking at your issue when i saw the tunnel and the static 
routes...
it's you who should know which route is where...
i never ever enter a static route i like routing protocols a lot... 
especially bgp...
thanks,
cs

On 8/29/22 10:52, mc36 wrote:
> so let's rewind and start from here.... frederic, did geant finished the 
> work? and what changed?
> and i well know that i could written these cryptic jsons but let's assume 
> that i did not...
> then what about the question that ping seemingly works fine from par0101 ?
>
> so i also lost a dpdk node during the process but the new image compiled for 
> dpdk21.11 is out:
>
> noti#show ipv4 lsrp 1 software | include freeRouter/22.8.29-cur | count
> info userReader.cmdEnter:userReader.java:1087 command noti#show ipv4 lsrp 1 software | 
> include freeRouter/22.8.29-cur | count   from local:telnet <loop> 23 -> 
> 127.0.0.1 48434
> 2022-08-29 10:44:25
> category | value
> lines       | 21
> words       | 105
> chars       | 930
>
> noti#show ipv4 lsrp 1 software | exclude freeRouter/22.8.29-cur | count
> info userReader.cmdEnter:userReader.java:1087 command noti#show ipv4 lsrp 1 software | 
> exclude freeRouter/22.8.29-cur | count   from local:telnet <loop> 23 -> 
> 127.0.0.1 48434
> 2022-08-29 10:44:26
> category | value
> lines       | 12
> words       | 60
> chars       | 559
>
> noti#
>
>
> my nodes voted that it's fine and please understand that some of these are on 
> day=sun some on hour=22, and so on..
>
> regarding the recovery of the lost my lost node, there are several ways:
>
> 1) i tar my favorite node's /var/apt/cache/ and untar at the failed node (if 
> you answered no at your home box during the last upgrade as i advice in mail 
> then be that in your case)
>
> 2) but a full os reinstall and restore from the config arcihe is usually 
> easier here, i'll go that way...
>
> 3) a hackish what if you
> 3a) tar the /rtr/
> 3b) reinstall the sid
> 3c) activate dpdk but p4emu-->p4dpdk should to something nowadays :)
> 3d) restore the /rtr/ from the tar but, without the binary blobs: *.bin 
> rtr.jar and rtr.zip...
> 3e) one thing to note there is if you had a trustworthy rtr.ver beforehand, 
> restore that file too
> 3f) flash simulate should print things
> 3g) if that's ok and did not complained then flash upgrade it does nothing...
>
> maybe i missed some other possibilities like 4, 5, 6....
>
> thanks,
> cs
>
>
>
> On 8/28/22 08:00, mc36 wrote:
> > clearly frederic the fuck are you doing?!?!?!?!?!
> >
> >
> > {"date":"2022-08-25T11:31:40.000Z","who":"fl","text":"BTW PAR0101 is down, GEANT moved their cage physcally in PAROS and 
> > obviously forgot things","flags":["incoming"],"remoteId":""}
> > {"date":"2022-08-25T11:31:43.000Z","who":"mc36","text":"hmm, then imho you'll send and i'll 
> > receive","flags":["outgoing"],"remoteId":""}
> > {"date":"2022-08-25T11:32:11.000Z","who":"mc36","text":"par0101 it'll recover later 
> > right?","flags":["outgoing"],"remoteId":""}
> > {"date":"2022-08-25T11:32:17.000Z","who":"fl","text":"I'm working with GEANT NOC in order to resolve that 
> > issue","flags":["incoming"],"remoteId":""}
> >
> >
> >
> >
> > On 8/28/22 07:57, mc36 wrote:
> > > okkk, btw at that point im pretty sure it was not geant btw.... :))))))))))
> > >
> > > On 8/28/22 07:39, mc36 wrote:
> > > > well, so the box will die for sure as geant recovers but if you used
> > > > client proxy clearnet
> > > > instead of
> > > > client proxy oob
> > > > which, is a wg to poznan then you wouldn't have to reinstall it from 
> > > > scratch...
> > > > clearly, what you had here is not oob but a tunneled one...
> > > >
> > > >
> > > > On 8/28/22 07:34, mc36 wrote:
> > > > > well it cannot be a routing issue :))))))))))))))))))))))))
> > > > >
> > > > > PAR0101#ping 1.1.1.1 vrf CLEARNET
> > > > > pinging 1.1.1.1, src=null, vrf=CLEARNET, cnt=5, len=64, df=false, tim=1000, 
> > > > > gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, sweep=false, multi=false
> > > > > !!!!!
> > > > > result=100.0%, recv/sent/lost/err=5/5/0/0, took 41, min/avg/max/dev 
> > > > > rtt=8/8.0/8/0.0, ttl 58/58.0/58/0.0, tos 164/164/164/0.0
> > > > > PAR0101#ping 195.111.97.109 vrf CLEARNET
> > > > > pinging 195.111.97.109, src=null, vrf=CLEARNET, cnt=5, len=64, df=false, 
> > > > > tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, sweep=false, 
> > > > > multi=false
> > > > > !!!!!
> > > > > result=100.0%, recv/sent/lost/err=5/5/0/0, took 157, min/avg/max/dev 
> > > > > rtt=31/31.4/32/0.2, ttl 249/249/249/0.0, tos 0/0.0/0/0.0
> > > > > PAR0101#
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 8/28/22 07:33, mc36 wrote:
> > > > > > my bad, i accidentally pinged in the wrong vrf, here is the good one:
> > > > > >
> > > > > > PAR0101#show ipv4 route CLEARNET
> > > > > > typ     prefix                                         metric     iface       
> > > > > >                       hop                                         time
> > > > > > S             0.0.0.0/0                             1/0                 
> > > > > > sdn1.666                 62.40.109.30     00:09:39
> > > > > > C             10.10.10.0/30             0/0                 hairpin6661     
> > > > > > null                                     11d19h
> > > > > > LOC     10.10.10.1/32             0/1                 hairpin6661     null    
> > > > > >                                  11d19h
> > > > > > C             62.40.109.30/31     0/0                 sdn1.666                
> > > > > >  null                                     00:09:39
> > > > > > LOC     62.40.109.31/32     0/1                 sdn1.666                 null 
> > > > > >                                     00:09:39
> > > > > >
> > > > > > PAR0101#
> > > > > > PAR0101#ping 62.40.109.30 vrf CLEARNET
> > > > > > pinging 62.40.109.30, src=null, vrf=CLEARNET, cnt=5, len=64, df=false, 
> > > > > > tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, sweep=false, 
> > > > > > multi=false
> > > > > > !!!!!
> > > > > > result=100.0%, recv/sent/lost/err=5/5/0/0, took 4, min/avg/max/dev 
> > > > > > rtt=0/0.6/1/0.2, ttl 64/64.0/64/0.0, tos 0/0.0/0/0.0
> > > > > > PAR0101#
> > > > > >
> > > > > > so from this point, i cannot say a word.... well i could.... :)
> > > > > >
> > > > > >
> > > > > > On 8/28/22 07:25, mc36 wrote:
> > > > > > > so helping to the irc question of you, that geant is unable to provide 
> > > > > > > internet access for 12 days now...
> > > > > > > fortunately the inband mgmt still works so you can help them find the issue 
> > > > > > > with the vlan666...
> > > > > > > seemingly we have some traffic and the good arp entry so it must be a routing 
> > > > > > > or acl issue at geant mx...:)))))))))
> > > > > > > bad news is that as today i unhold the dpdk21 packages and the box haven't 
> > > > > > > got the dpdk21.11 so it'll self destruct as geant recovers.... :(
> > > > > > >
> > > > > > >
> > > > > > > PAR0101#show platform
> > > > > > > freeRouter v22.7.26-cur, done by cs@nop.
> > > > > > >
> > > > > > > name: PAR0101
> > > > > > > hwid: Dell Inc. PowerEdge R430/0CN7X8
> > > > > > > hwsn: null
> > > > > > > uptime: since 2022-08-16 11:33:15, for 11d19h
> > > > > > > reload: code#2=upgrade finished
> > > > > > > rwpath: /rtr/
> > > > > > > hwcfg: /rtr/rtr-hw.txt
> > > > > > > swcfg: /rtr/rtr-sw.txt
> > > > > > > cpu: 40*amd64
> > > > > > > mem: free=519m, max=1073m, used=1073m
> > > > > > > host: Linux v5.17.0-2-amd64
> > > > > > > java: Debian v19-ea @ /usr/lib/jvm/java-19-openjdk-amd64
> > > > > > > jspec: Oracle Corporation (Java Platform API Specification) v19
> > > > > > > vm: Debian (OpenJDK 64-Bit Server VM) v19-ea+32-Debian-1
> > > > > > > vmspec: Oracle Corporation (Java Virtual Machine Specification) v19
> > > > > > > class: v63.0 @ /rtr/rtr.jar
> > > > > > >
> > > > > > > PAR0101#show interfaces summary
> > > > > > > interface                     state     tx                         rx         
> > > > > > >                                 drop
> > > > > > > template1                     admin     0                             0       
> > > > > > >                                       588
> > > > > > > template666             admin     0                             0             
> > > > > > >                                 0
> > > > > > > loopback0                     up                 2402                 0       
> > > > > > >                                       0
> > > > > > > loopback20965     up                 0                             0          
> > > > > > >                                    0
> > > > > > > ethernet0                     up                 45335             115091610  
> > > > > > >            0
> > > > > > > ethernet1                     up                 780                     4004 
> > > > > > >                                 4004
> > > > > > > hairpin6661             up                 486+0             486+0            
> > > > > > >                  0+0
> > > > > > > hairpin6662             up                 486+0             486+0            
> > > > > > >                  0+0
> > > > > > > sdn1                                         up                 44351+0     
> > > > > > > 114894232+0     0+0
> > > > > > > sdn1.102                         up                 3628+0         3958+0     
> > > > > > >                     0+0
> > > > > > > sdn1.103                         up                 26429+0     16116+0       
> > > > > > >               0+0
> > > > > > > sdn1.666                         up                 11930+0     114479534+0   
> > > > > > >   0+0
> > > > > > > sdn2                                         admin     0+0                    
> > > > > > >  0+0                                     0+0
> > > > > > > tunnel123                     up                 670+0             0+0        
> > > > > > >                              0+0
> > > > > > > tunnel2075                 up                 5462+0         4238+0           
> > > > > > >               0+0
> > > > > > >
> > > > > > > PAR0101#
> > > > > > > PAR0101#show running-config interface sdn1.666
> > > > > > > interface sdn1.666
> > > > > > >        description AMT RLY INTERNET facing interface
> > > > > > >        monitor-buffer 8192000
> > > > > > >        vrf forwarding CLEARNET
> > > > > > >        ipv4 address 62.40.109.31 255.255.255.254
> > > > > > >        ipv6 address 2001:798:dd:6::6 ffff:ffff:ffff:ffff:ffff:ffff:ffff:fffc
> > > > > > >        ipv6 enable
> > > > > > >        no shutdown
> > > > > > >        no log-link-change
> > > > > > >        exit
> > > > > > > !
> > > > > > >
> > > > > > > PAR0101#show ipv4 arp sdn1.666
> > > > > > > mac                                                 address                   
> > > > > > >       time                     static
> > > > > > > a8d0.e5f7.8717     62.40.109.30     00:00:11     false
> > > > > > >
> > > > > > > PAR0101#
> > > > > > > PAR0101#ping 62.40.109.30 vrf oob
> > > > > > > pinging 62.40.109.30, src=null, vrf=oob, cnt=5, len=64, df=false, tim=1000, 
> > > > > > > gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, sweep=false, multi=false
> > > > > > > .....
> > > > > > > result=0.0%, recv/sent/lost/err=0/5/5/0, took 5001, min/avg/max/dev 
> > > > > > > rtt=10000/0.0/0/0.0, ttl 256/0.0/0/0.0, tos 256/0.0/0/0.0
> > > > > > > PAR0101#
> > > > >
> > > > >
> > > > > -=-=-=-=-=-=-=-=-=-=-=-
> > > > > Groups.io Links: You receive all messages sent to this group.
> > > > > View/Reply Online (#645): https://groups.io/g/freertr/message/645
> > > > > Mute This Topic: https://groups.io/mt/93302745/6006518
> > > > > Group Owner: 
> > > > > Unsubscribe: https://groups.io/g/freertr/unsub []
> > > > > -=-=-=-=-=-=-=-=-=-=-=-