> 1. Is VIF support NIC specific? I have a test box, with one built-in
> 100Mb/s forcedeth (NForce2) interface, and a couple of cheap Realtek
8169
> PCI 1000Mb/s interfaces. All work fine without VIFs, but when I try to
> add a VIF to the r8169 cards, the commit fails (and all subsequent
commits
> of any type until a reboot). Adding VIFs to the onboard Nforce NIC
works
> fine. Is there a list somewhere of what cards work with VIFs or is this
> perhaps something else?
Could you try the vif command from the linux shell instead to see if it
gives you a error message on that nic. For example, try creating eth1.101
with:
vDUT-stig:~# vconfig add eth1 101
Added VLAN with VID == 101 to IF -:eth1:-
vDUT-stig:~# ifconfig eth1.101
eth1.101 Link encap:Ethernet HWaddr 00:0C:29:EF:FC:25
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> 2. Also, are there any plans for a web service interface as an
> alternative to the CLI. The scenario would be wanting to control the
> router(s) externally from another custom management app. For instance,
> I'd like to be able to connect to the router via a secure channel from
my
> app, and create a new VIF and a few NAT and FW rules for it, etc. I can
> see how this might be hacked by reverse engineering the inputs to xgcgi
in
> your existing web interface and feeding it with curl or something
similar
> over https, but a standard web services interface would be much nicer.
> Does libxorp already have something like this?
There is a web interface that can be enabled with "set service webgui".
>
> 3. After I get the VIFs working properly, I'm going to test the VRRP
> stuff. One question that doesn't seem to be covered in the VRRP
> documentation that I've been wondering about - do the configs auto
update
> between master and slave(s) or is the user responsible for manually
> editing the configs on all machines in the group to keep things in sync?
The standard vrrp feature as described by rfc2338 does not have any config
sync'ing.
stig
>
> Thanks, Jeff
> _______________________________________________
> 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
