Hmm, that's odd. I'm getting the same problem on eth1 on my OFR. set interfaces ethernet eth1 vif 1024 [edit] [EMAIL PROTECTED] commit [edit] Commit Failed 102 Command failed Interface error on eth1.1024: interface not recognized
I attempted to just create the VLAN interface without IPing it to see if there was some sort of race condition, but that doesn't seem to be the case. I also tried with a higher VLAN id in case that was some sort of issue. This also seems to affect the web interface, as I can't create vif's from the web interface. Maybe I'm doing something wrong though. The weird thing is is that I'm already using VLAN interfaces... Nick On 9/6/07, Rodney Prescott <[EMAIL PROTECTED]> wrote: > > Hi, > > Trying as per the documentation set up VLANs on the Community version > 2.2 > > So here is the problem > > [edit] > [EMAIL PROTECTED] set interfaces ethernet eth1 vif 40 address > 10.10.40.65 prefix-length 24 > [edit] > [EMAIL PROTECTED] commit > [edit] > Commit Failed > [EMAIL PROTECTED] led Interface error on eth1.40: interface not > [EMAIL PROTECTED] > [edit] > > Does it on both the WEB interface and as above on the CLI, gets the > same error message when Commit is used on the web as well > > > HELP, as I need to have VLANs running for the Wireless Gear I am > running, the multi SSIDs need unique VLANS > > Thanks in anticipation > _______________________________________________ > 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
