Re: [Vyatta-users] installation
You use the VC3 live cd, login as user=root/password=vyatta to enter normal linux mode. type install-system If you already have linux partitions on your hard drive, installation may fail. You can remove them first with cfdisk David -Original Message- From: [EMAIL PROTECTED] on behalf of John Jolet Sent: Thu 08/11/2007 11:06 To: [EMAIL PROTECTED] Cc: Subject:[Vyatta-users] installation I'm a little confused on the issue of installing vyatta. I'm looking at community edition 3, and it's available as a vm and as a live cd iso. So I want to install this on a machine to use as a router, but I don't see anywhere how to actually get it onto the hard driveCan someone point me to where in the documentation this action is mentioned? Thanks. ___ 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
Re: [Vyatta-users] subnet move/add/change misbehavior [grrrrr!]
The routes were missing from the system table and the Linux "root mode" table My hardware was ancient Compaq PII 266 with Intel eepro NIC and a Celeron 768 with Realtek NIC, so I don't think your problem is caused by your fast hardware Regards David Aubrey Wells wrote: > Sounds like we have the same issue then. Do your routes show up > correctly in the system routing table? What kind of hardware are you > using? I'm running a dell 1950 with dual dual-core 3.0 Xeons and 8 gig > of ram. No PCI cards, all onboard broadcom NICs. > > > -- > Aubrey Wells > Senior Engineer > Shelton | Johns Technology Group > 404.478.2790 > www.sheltonjohns.com > > > > On Nov 6, 2007, at 5:58 AM, David Pearce wrote: > >> I have found that VC3 is very fussy about adding routes. Changing an >> interface and deleting the node followed by recreating it with new >> settings leads to no routing table entries for me. >> I have found that the only way to get a correct table is to start from a >> clean format >> >> David >> >> Aubrey Wells wrote: >>> It is the next hop. To give you one of the scenarios: >>> >>> Added 8.17.X.253 /30 to eth0 vif 1180 >>> >>> subnet doesnt show up in vyatta's routing table (show route) but does >>> show up in the system table (route -n) and I can ping the other side >>> (8.17.X.254) both from within xorp and from the unix shell. >>> >>> So then I add a static route for 3 subnets pointing to the (directly >>> connected) route of the other side of that /30 (8.17.X.254). show >>> route from xorp says its next hop is my default route. show >>> configuration shows that I didnt screw up i did in fact do what i >>> meant to. the system routing table (route -n) says the same thing as >>> the xorp table (that i configured it to be the same as the default >>> route). So the route doesnt work, and what's worse, is if I try to >>> delete it from the config (delete protocols static 216.32.X.0/20 next- >>> hop 8.17.X.254) it tells me I cant delete a non-existant route. If I >>> try to put what it thinks the route is, it says the node doesnt >>> exist. I have to delete the offending line from the config file with >>> vi and reboot (or load config.boot now that I know that) to get it >>> back to a state where I can work with it. And this pesky line shows >>> up in the log. I dont see anything interesting in any other logs that >>> I know about: >>> >>> >>>> Nov 4 01:49:47 vyatta xorp_fea: [ 2007/11/04 01:49:47 WARNING >>>> xorp_fea FEA >>>> ] Got update for address no in lib >>>> feaclient tree: eth0.1180/eth0.1180/8.17.X.253 >>>> >>> >>> >>> THe other scenario: >>> IP 8.17.X.113 /28 exists on eth1 vif 1192. I remove it and commit. >>> Its gone out of both the system and xorp routing tables. i read it as >>> 8.17.X.113 /29 and commit. It doesnt show up in the xorp table, but >>> it is in the system table. I get the same log message as above and my >>> system hates me for it. The route works (i can ping the other side) >>> but I can't configure any services to use it. :-( >>> >>> >>> *sigh* Any ideas? >>> >>> I searched bugzilla, and only came up with bug 1602, which appears to >>> be the exact opposite of my issue. I'm going to try to reproduce on a >>> dev box and use my subscription support to see if one of you guys can >>> log in to it and poke around. >>> >>> >>> -- >>> Aubrey Wells >>> Senior Engineer >>> Shelton | Johns Technology Group >>> A Vyatta Ready Partner >>> www.sheltonjohns.com >>> >>> >>> >>> >>> On Nov 6, 2007, at 12:08 AM, Justin Fletcher wrote: >>> >>> >>>> No problem - I know exactly how you feel some days! >>>> >>>> And I'd missed the point that it didn't make into the system route >>>> table, so the >>>> first question I'd ask is whether the next hop you're specifying is >>>> directly connected? >>>> If it isn't, try using the IP address of the directly connected >>>> next hop router. >>>> >>>> If it is, well, there's a bit more to figure out, as I've never seen >>>> that behavior. >>>> >>>> To try a rephrase on the load config command, it'll
Re: [Vyatta-users] Static routing and E1 serial
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
Re: [Vyatta-users] subnet move/add/change misbehavior [grrrrr!]
I have found that VC3 is very fussy about adding routes. Changing an
interface and deleting the node followed by recreating it with new
settings leads to no routing table entries for me.
I have found that the only way to get a correct table is to start from a
clean format
David
Aubrey Wells wrote:
> It is the next hop. To give you one of the scenarios:
>
> Added 8.17.X.253 /30 to eth0 vif 1180
>
> subnet doesnt show up in vyatta's routing table (show route) but does
> show up in the system table (route -n) and I can ping the other side
> (8.17.X.254) both from within xorp and from the unix shell.
>
> So then I add a static route for 3 subnets pointing to the (directly
> connected) route of the other side of that /30 (8.17.X.254). show
> route from xorp says its next hop is my default route. show
> configuration shows that I didnt screw up i did in fact do what i
> meant to. the system routing table (route -n) says the same thing as
> the xorp table (that i configured it to be the same as the default
> route). So the route doesnt work, and what's worse, is if I try to
> delete it from the config (delete protocols static 216.32.X.0/20 next-
> hop 8.17.X.254) it tells me I cant delete a non-existant route. If I
> try to put what it thinks the route is, it says the node doesnt
> exist. I have to delete the offending line from the config file with
> vi and reboot (or load config.boot now that I know that) to get it
> back to a state where I can work with it. And this pesky line shows
> up in the log. I dont see anything interesting in any other logs that
> I know about:
>
>
>> Nov 4 01:49:47 vyatta xorp_fea: [ 2007/11/04 01:49:47 WARNING
>> xorp_fea FEA
>> ] Got update for address no in lib
>> feaclient tree: eth0.1180/eth0.1180/8.17.X.253
>>
>
>
> THe other scenario:
> IP 8.17.X.113 /28 exists on eth1 vif 1192. I remove it and commit.
> Its gone out of both the system and xorp routing tables. i read it as
> 8.17.X.113 /29 and commit. It doesnt show up in the xorp table, but
> it is in the system table. I get the same log message as above and my
> system hates me for it. The route works (i can ping the other side)
> but I can't configure any services to use it. :-(
>
>
> *sigh* Any ideas?
>
> I searched bugzilla, and only came up with bug 1602, which appears to
> be the exact opposite of my issue. I'm going to try to reproduce on a
> dev box and use my subscription support to see if one of you guys can
> log in to it and poke around.
>
>
> --
> Aubrey Wells
> Senior Engineer
> Shelton | Johns Technology Group
> A Vyatta Ready Partner
> www.sheltonjohns.com
>
>
>
>
> On Nov 6, 2007, at 12:08 AM, Justin Fletcher wrote:
>
>
>> No problem - I know exactly how you feel some days!
>>
>> And I'd missed the point that it didn't make into the system route
>> table, so the
>> first question I'd ask is whether the next hop you're specifying is
>> directly connected?
>> If it isn't, try using the IP address of the directly connected
>> next hop router.
>>
>> If it is, well, there's a bit more to figure out, as I've never seen
>> that behavior.
>>
>> To try a rephrase on the load config command, it'll make your running
>> configuration
>> match the configuration in the file (usually :-) )
>>
>> Justin
>>
>> On Nov 5, 2007 8:52 PM, Aubrey Wells <[EMAIL PROTECTED]> wrote:
>>
>>> Thanks for the response - sorry for my impatience. :-)
>>>
>>> I dont mind the viewing discrepancy, its the fact that vyatta doesn't
>>> recognize the existance of the routes - so I can't do anything
>>> with them. So
>>> you're saying load config.boot should fix the problem? Will that
>>> cause any
>>> downtime while it rereads the config, or should it be seamless?
>>>
>>> Also... maybe its just because its been a really long day, but
>>> this sentence
>>> doesn't make any sense:
>>>
>>> "it'll remove everything that's not in the current configuration
>>> that's in
>>> the config file, and add the new commands from the config file."
>>>
>>> Could you possibly rephrase for me? :-)
>>>
>>>
>>>
>>> --
>>> Aubrey Wells
>>> Senior Engineer
>>> Shelton | Johns Technology Group
>>>
>>> www.sheltonjohns.com
>>>
>>>
>>>
>>>
>>>
>>> On Nov 5, 2007, at 11:31 PM, Justin Fletcher wrote:
>>>
>>> Good questions - I think you're just seeing a synchronization issue.
>>>
>>> If you see it in the system route table ("route -n" from the Linux
>>> shell or "show route system forward" from the CLI) it's really in the
>>> system RIB as the forwarding information base is updated from the
>>> RIB.
>>> However, "show route" looks at a different table, and can be somewhat
>>> out of sync.
>>>
>>> So - if you see the route from "show route system forward" it made it
>>> into the route tables correctly - you're just seeing a viewing
>>> discrepancy issue.
>>>
>>> Also, you can load the configuration using "load config.boot" in
>>> config mode; it'll remove everyth
[Vyatta-users] Static routing and E1 serial
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 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
Re: [Vyatta-users] Basic frame relay setup
Thanks I changed to serial i/f to ppp encapsulation and now the link comes up and packets are flowing I already have one end internal clock and the other external. Now to learn how to set up routing so that I can use it David Robyn Orosz wrote: > Hi David, > > PPP or HDLC will work back to back with a cross-over cable as you have > it. You may need to set one side of the connection for internal > clocking as Paul has stated. > > For frame-relay, you need to set one side as the DCE which can't > currently be done via the CLI. You'll need to edit the > /etc/wanpipe/wanpipe1.conf file by changing the "Station" value to > "Station = NODE" and changing the "SIGNALLING" value from auto to > something else like ANSI - ex: "SIGNALLING = ansi". This value should > be listed under the [wan0.fr] section of the wanpipe conf file. Once > you've edited this file, you'll need to run the command 'wanrouter > restart' from the bash shell. > > An enhancement has been created to add this feature to the CLI: > > https://bugzilla.vyatta.com/show_bug.cgi?id=2253 > > Thanks, > > Robyn > > virtualsystems-org wrote: >> David, >> >> Years ago when I used to do these back-to-back configs on Cisco gear, I >> had to apply internal clock source to bring the T1/E1 up. I think by >> default, these facilities rely on external clock (the telco) to bring >> the link up. >> >> Is there an option for internal clock source? >> >> Paul >> >> >> -Original Message- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of David >> Pearce >> Sent: Monday, November 05, 2007 6:29 AM >> To: [EMAIL PROTECTED] >> Subject: [Vyatta-users] Basic frame relay setup >> >> I am a Vyatta beginner trying to set up a very simple static network >> with two pcs and a E1 link between them using Sangoma A101 cards. >> I have set up the frame relay encapsulation and local and remote >> addresses with vif 16. >> The wan cards are linked by a E1 pins 1,2 to 4,5 crossover cable that >> I have made up >> Nothing I do seems to bring the E1 link up and I see errors about >> wlan0.1 which I presume is the (unused) ppp vif >> >> Any known problems here? >> >> David >> ___ >> 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 >> > ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
[Vyatta-users] Basic frame relay setup
I am a Vyatta beginner trying to set up a very simple static network with two pcs and a E1 link between them using Sangoma A101 cards. I have set up the frame relay encapsulation and local and remote addresses with vif 16. The wan cards are linked by a E1 pins 1,2 to 4,5 crossover cable that I have made up Nothing I do seems to bring the E1 link up and I see errors about wlan0.1 which I presume is the (unused) ppp vif Any known problems here? David ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
