Project

General

Profile

Actions

Bug #1767

closed

Unable to modify pppoe interface which is linked to a vlan via WebGUI

Added by Willy Tenner over 10 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Category:
Web Interface
Target version:
Start date:
08/10/2011
Due date:
% Done:

100%

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

Description

In Germany our VDSL provider (T-Com) is using VLAN id 7 for connecting to the internet. So I created VLAN 7 with parent interface sis0. Then I assigned the newly created network port sis0_vlan7 to the WAN interface. Next I changed the interface type of the WAN to PPPoE, entering all necessary login information. The WAN interface is coming up and everything worked fine for me.

But when I try to change the properties of the pppoe0 interface I have no chance to select the correct link interface (sis0_vlan7) because it is not shown in the list of link interfaces. (Yes, I have scrolled down the whole list!). This is really a problem because some other providers need the option "Configure a NULL Service name" and there is no other way to configure this via the WebGUI.

Is this a bug? See my attached screenshots.

I am currently using version: 2.0-RC3 (i386) built on Sun Jul 24 19:56:21 EDT 2011


Files

pfsense-pppoe-vlan-1.jpg (142 KB) pfsense-pppoe-vlan-1.jpg WAN interface assigned to PPPOE0 Willy Tenner, 08/10/2011 06:30 AM
pfsense-pppoe-vlan-2.jpg (86 KB) pfsense-pppoe-vlan-2.jpg Interfaces: PPPs: pppoe0 linked to sis0_vlan7 Willy Tenner, 08/10/2011 06:30 AM
pfsense-pppoe-vlan-3.jpg (158 KB) pfsense-pppoe-vlan-3.jpg Cannot change properties of pppoe0 Willy Tenner, 08/10/2011 06:30 AM
Actions #1

Updated by Jim Pingle over 10 years ago

Not that it matters to the real bug here, but "configure a null service name" is now the default behavior if the service name is left blank, so it's no longer necessary to explicitly check that box.

Actions #2

Updated by Oliver Loch over 10 years ago

Hi,

IMHO it's not a real bug - it's just the way it's configured. You create a VLAN and then you assign the VLAN interface to the WAN "interface" on the assign page. After that you change the type from none to pppoe and start configuring the device.

As you never assigned the vlan interface a name (like opt5 or something), it can't show up in the list.

IMHO it's a configuration error (I made the same mistake) - that could be blocked by the WebUI.

Btw. Since when is T-Online using tagged packets for internet access?

KR,

Grimeton

Actions #3

Updated by Willy Tenner over 10 years ago

Hi Oliver,

from the view of the WAN interface sis0_vlan7 is a network port and the name of this network port was created automatically by pfsense. So there is only the option to rename an interface but not a network port.

Since two years T-Com is offering VDSL and for separating the traffic for IPTV and normal network traffic T-Com is using different VLANs: VLAN ID 8 for IPTV and VLAN ID 7 for normal internet traffic, at least here in Berlin.

Regards,
Willy Tenner

Actions #4

Updated by Ermal Luçi over 10 years ago

  • Target version changed from 2.0 to 2.1

This is not expected to work on 2.0.

The way you should do is assign the vlan and then go and create a PPP type link from the GUI and selecting the assigned vlan.

After 2.0 this needs fixing.

Actions #5

Updated by Renato Botelho almost 9 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #6

Updated by Renato Botelho almost 9 years ago

  • Assignee set to Renato Botelho
  • Affected Architecture All added
  • Affected Architecture deleted (i386)
Actions #7

Updated by Chris Buechler over 8 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF