Stig I found that the root mode routing table was completely missing and a lot of RIB errors being continuously reported VC3 seems to not like serial ports being deleted and recreated. Another issue is that Ethernet NICs that are not actually connected during installation seem to be overlooked during the route creation I solved my problem by formatting and starting again with cisco-hdlc encapsulation
Regards David Stig Thormodsrud wrote: >> I have two PCs linked by an E1 link wit Sangoma A101 cards >> PC1 >> eth0 10.0.0.0/24 >> wan0 >> local 192.168.0.1 >> remote 192.168.0.2 >> prefix-length 24 >> >> PC2 >> eth0 10.9.1.0/24 >> wan0 >> local 192.168.0.2 >> remote 192.168.0.1 >> prefix-length 24 >> >> show route does not show the wan ports and I cannot ping them locally >> > > Do the connected routes show up in "show route system forward"? > Can you ping the remote end of the wan link (often you can't ping the > local end of a non-broadcast media). > > stig > > > >> Looking at PC1 /var/log/wan0.1.log I see >> "Peer is not authorized to use remote address 192.168.0.2" and >> equivalent also on PC2 >> >> The wan link is in PPP mode with authentication type set to none >> _______________________________________________ >> Vyatta-users mailing list >> Vyatta-users@mailman.vyatta.com >> http://mailman.vyatta.com/mailman/listinfo/vyatta-users >> > > > _______________________________________________ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
