Thanks for the response
The CLI gives the following for both types of address assignment - no errors
login as: vyatta
[EMAIL PROTECTED]'s password:
Linux vyatta 2.6.20 #1 Thu Aug 23 12:25:11 PDT 2007 i686
Welcome to Vyatta.
This system is open-source software. The exact distribution terms for
each module comprising the full system are described in the individual
files in /usr/share/doc/*/copyright.
Welcome to Vyatta on r1
[EMAIL PROTECTED]> configure
Entering configuration mode.
There are no other users in configuration mode.
[EMAIL PROTECTED] set interfaces ethernet eth0 address 2000::1 {
[edit]
> prefix-length 64
[edit]
> }
[edit]
[EMAIL PROTECTED] set interfaces ethernet eth1 address
2000:0000:0000:0001:0000:0000:0000:0001 {
[edit]
> prefix-length 64
[edit]
> }
[edit]
[EMAIL PROTECTED] commit
[edit]
OK
[EMAIL PROTECTED] save
[edit]
Save done.
====
So lets show what we set
====
[EMAIL PROTECTED] show interfaces ethernet eth0
description: "internet"
hw-id: 00:0C:29:59:23:87
address 2000::1 {
prefix-length: 64
}
[edit]
[EMAIL PROTECTED] show interfaces ethernet eth1
hw-id: 00:0C:29:59:23:91
address 2000:0000:0000:0001:0000:0000:0000:0001 {
prefix-length: 64
}
[edit]
[EMAIL PROTECTED]
====
All looks OK - no errors
Looking at the config.boot file
====
ethernet eth0 {
disable: false
discard: false
description: "internet"
hw-id: 00:0C:29:59:23:87
duplex: "auto"
speed: "auto"
}
ethernet eth1 {
disable: false
discard: false
description: ""
hw-id: 00:0C:29:59:23:91
duplex: "auto"
speed: "auto"
address 2000:0000:0000:0001:0000:0000:0000:0001 {
prefix-length: 64
disable: false
}
}
====
So it looks like the config file does not match what the CLI thinks
But what ever - lets reboot
====
In this particular case, the system hangs with "Starting router manager:"
spinning its wheel on the
Screen and never gets to the login prompt.
I can use SSH though and ifconfig shows eth1 set properly but not eth0
====
eth0 Link encap:Ethernet HWaddr 00:0C:29:59:23:87
inet6 addr: fe80::20c:29ff:fe59:2387/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
Interrupt:18 Base address:0x2000
eth1 Link encap:Ethernet HWaddr 00:0C:29:59:23:91
inet6 addr: 2000:0:0:1::1/64 Scope:Global
inet6 addr: fe80::20c:29ff:fe59:2391/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:746 (746.0 b)
Interrupt:19 Base address:0x2080
====
Not only that but now the following errors appear in /var/log/messages
====
Sep 20 00:53:12 vyatta xorp_rib: [ 2007/09/20 00:53:12 WARNING xorp_rib
LIBFEACLIENT ] NetlinkHead::io_event(), iface is empty
Sep 20 00:53:12 vyatta last message repeated 5 times
Sep 20 00:53:12 vyatta xorp_rib: [ 2007/09/20 00:53:12 WARNING xorp_rib
XrlFeaIfmgrMirrorTarget ] Handling method for fea_ifmgr_mirror/0.1/ipv6_add
failed: XrlCmdError 102 Command failed Local dispatch error
Sep 20 00:53:12 vyatta xorp_fea: [ 2007/09/20 00:53:12 FATAL xorp_fea:4366
LIBFEACLIENT +88
/home/autobuild/builds/master/2007-08-23-1113/ofr/xorp/xorp/libfeaclient/ifm
gr_xrl_replicator.cc xrl_cb ] Remote and local trees out of sync.
Programming bug.
Sep 20 00:53:12 vyatta xorp_rtrmgr: [ 2007/09/20 00:53:12 ERROR
xorp_rtrmgr:4302 LIBXORP +741
/home/autobuild/builds/master/2007-08-23-1113/ofr/xorp/xorp/libxorp/run_comm
and.cc done ] Command "/opt/vyatta/libexec/xorp/xorp_fea": terminated with
signal 6; aborted with a core dump.
====
When I was just setting eth0 and not eth1 as well, I got a totally different
set of symptoms
====
-----Original Message-----
From: Justin Fletcher [mailto:[EMAIL PROTECTED]
Sent: Thursday, 20 September 2007 9:33 AM
To: [EMAIL PROTECTED]
Cc: vyatta-users@mailman.vyatta.com
Subject: Re: [Vyatta-users] Cannot get an IPv6 address assigned to an
interface
Can you try this through the CLI and see if any messages are generated?
Also, try 2000::1 for the IPv6 address; it may or may not make a difference.
btw, this is successful with the latest source version --
Justin
On 9/19/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
>
> I have spent hours trying to get an IPv6 address entered for an interface.
I
> have read all the manuals
> but just cannot get it working. The most annoying thing I find is that
when
> there is a PARSE error in
> the config.boot file, everything in config.boot fails. This means SSH
won't
> work, the GUI won't work,
> you can't even log on to run the CLI.
> I configured the IPv6 via the GUI and commit it and there is no error,
> rebooting fails.
> The config.boot fragment is:
> interfaces {
> restore: false
> loopback lo {
> description: ""
> }
> ethernet eth0 {
> disable: false
> discard: false
> description: "internet"
> hw-id: 00:0C:29:59:23:87
> address: 2000:0000:0000:0000:0000:0000:0000:0001 {
> prefix-length: 64
> }
> duplex: "auto"
> speed: "auto"
> }
> I am running the liveCD community version 2.2 with no hard disk under
> vmware.
> Interestingly I have been able to enter IPv6 addresses without problems in
> an XORP liveCD release
>
> regards
> Ian
> _______________________________________________
> 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
