Project

General

Profile

Actions

Bug #1178

closed

Unable to select VLAN in PPPs interfaces

Added by Xavier Romain over 13 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/07/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

VLAN interfaces does not appear in PPPs link interfaces.

I have two physical interfaces:
- le0 (used for LAN)
- le1 (used for two WANs)

I have configured two VLAN:

- le1_vlan101
- le1_vlan102

I would like to use pppoe0 with le1_vlan101 and pppoe1 with le1_vlan102 but these interfaces don't appear in "Link interface(s)" (in PPPs configuration page)

Using 2.0-BETA5 (i386) built on Thu Jan 6 02:06:43 EST 2011


Files

pfsense.localdomain_-_Interfaces_PPPs_Edit_-_Mozilla_Firefox_2011-01-07_23-17-48.png (17.9 KB) pfsense.localdomain_-_Interfaces_PPPs_Edit_-_Mozilla_Firefox_2011-01-07_23-17-48.png Xavier Romain, 01/07/2011 05:19 PM
pfsense.localdomain_-_Interfaces_PPPs_Edit_-_Mozilla_Firefox_2011-01-07_23-18-02.png (17.8 KB) pfsense.localdomain_-_Interfaces_PPPs_Edit_-_Mozilla_Firefox_2011-01-07_23-18-02.png Xavier Romain, 01/07/2011 05:19 PM
pfsense.localdomain_-_Interfaces_VLAN_-_Mozilla_Firefox_2011-01-07_23-14-58.png (6.73 KB) pfsense.localdomain_-_Interfaces_VLAN_-_Mozilla_Firefox_2011-01-07_23-14-58.png Xavier Romain, 01/07/2011 05:19 PM
pfsense.localdomain_-_Interfaces_Assign_network_ports_-_Mozilla_Firefox_2011-01-07_23-14-24.png (9.21 KB) pfsense.localdomain_-_Interfaces_Assign_network_ports_-_Mozilla_Firefox_2011-01-07_23-14-24.png Xavier Romain, 01/07/2011 05:19 PM
pfsense.localdomain_-_Interfaces_Assign_network_ports_-_Mozilla_Firefox_2011-01-07_23-15-53.png (8.49 KB) pfsense.localdomain_-_Interfaces_Assign_network_ports_-_Mozilla_Firefox_2011-01-07_23-15-53.png Xavier Romain, 01/07/2011 05:19 PM
pfsense.localdomain_-_Interfaces_Assign_network_ports_-_Mozilla_Firefox_2011-01-07_23-16-13.png (9.67 KB) pfsense.localdomain_-_Interfaces_Assign_network_ports_-_Mozilla_Firefox_2011-01-07_23-16-13.png Xavier Romain, 01/07/2011 05:19 PM
pfsense.localdomain_-_Interfaces_Assign_network_ports_-_Mozilla_Firefox_2011-01-07_23-17-23.png (9.77 KB) pfsense.localdomain_-_Interfaces_Assign_network_ports_-_Mozilla_Firefox_2011-01-07_23-17-23.png Xavier Romain, 01/07/2011 05:19 PM
pfsense.localdomain_-_Interfaces_PPPs_-_Mozilla_Firefox_2011-01-07_23-17-34.png (6.78 KB) pfsense.localdomain_-_Interfaces_PPPs_-_Mozilla_Firefox_2011-01-07_23-17-34.png Xavier Romain, 01/07/2011 05:19 PM
Kernel_Panic.png (23.9 KB) Kernel_Panic.png Xavier Romain, 01/07/2011 05:33 PM
Actions #1

Updated by Ermal Luçi over 13 years ago

  • Target version deleted (2.0)

For 2.0 you have either to assign vlan and on interfaces->$assignedone choose pppoe.
Or assign the vlan and then on ppps screen you can configure it for pppoe.

Having this in 2.0 would need changes to make sure that we always have the vlan ready for pppoe and it would take some.

Actions #2

Updated by Xavier Romain over 13 years ago

Some screenshots may help you to understand my problem...

Actions #3

Updated by Xavier Romain over 13 years ago

When I select WAN interface in PPP editor for pppoe0, I get a kernel panic.

Actions #4

Updated by Marcus Brown over 13 years ago

You've fallen prey to excess complexity. :) The UI is admittedly not intuitive.

Here are the steps to follow.

)create VLANs (example vl1 and vl2) on you leX interfaces.
)Assign those vlans to OPT1 and OPT2 (or OPTx) and enable them.
)Go to Interfaces_PPPs and select OPT1 or OPT2 for the Interface that you're using for PPPoE
)Go to Interfaces_Assign and select the newly create PPPoE(vl1) for your WAN link. If you have Dual WAN, then create OPT3 and assign the PPPoE(vl2) interface to it.
)Done. WAN should come up then.

In your posted pics, when you see "PPPoE0()" with empty parentheses that means you have a problem. There should always be something in there or it won't work.

Actions #5

Updated by Jim Pingle almost 11 years ago

  • Status changed from New to Closed

Fixed on 2.1, see #1767 and 7807664d

Actions

Also available in: Atom PDF