News: This forum is now permanently frozen.
Pages: [1]
Topic: VLAN on WAN interface  (Read 3802 times)
« on: April 16, 2011, 10:07:52 »
infomediador *
Posts: 8

Hi,

My local telco has offered me an upgrade to fiber, as part of the installation they replace my existing ADSL router with a fiber termination device and a new router. In my current ADSL installation the router is configured as a bridge and I use my M0n0wall to do PPPoE.

With the fiber installation the termination device uses a VLAN and it appears that there is no way to change that. So my question is can I configure M0n0wall to use a VLAN on the WAN interface? M0n0wall is running on a PCEngines WRAP, which appears to have 802.1q support.

For me the router is redundant and I would prefer not to have another device consuming electricity and taking up space.

Any suggestions?

TIA

Alan
« Last Edit: April 16, 2011, 10:35:44 by infomediador »
« Reply #1 on: April 16, 2011, 12:03:48 »
brushedmoss ****
Posts: 446

Yes, look at the assign interface option
« Reply #2 on: April 25, 2011, 20:01:29 »
Јаневски ***
Posts: 153

Yes in the installation You're actually being prompted if You would like to assign VLAN interfaces first so I think it's doable that way, or by manually editing the configuration, You must be careful when using the second option.

« Reply #3 on: May 20, 2011, 21:32:17 »
infomediador *
Posts: 8

OK, so finally the fiber was installed today. I tried assigning the VLAN to the WAN interface. Configured the WAN to PPPoE, reset M0n0wall and it doesn't work.

How can I check to see if my hardware PCEngines WRAP really supports 802.1q VLAN tagging? Also is there any way to see if the VLAN is actually configured?

Thx

Alan
« Reply #4 on: May 21, 2011, 10:50:03 »
Јаневски ***
Posts: 153

Yes it is possible [maybe rarely nowadays] a NIC not to support VLAN tagging at all or maybe just not adding VLAN tags on outgoing packets.
In such scenario I usually use traffic analyzer tapped onto the connection to determine where is the problem.
In my situation I've noticed that the incoming packets are tagged and outgoing are not, that's how I've realized that I have a problem with the VLAN tags being not encapsulated in the packet from my side.
NIC change solved the problem once and for all.
« Last Edit: May 21, 2011, 10:52:03 by Јаневски »

« Reply #5 on: May 21, 2011, 14:17:50 »
infomediador *
Posts: 8

I finally discovered what I was doing wrong; I ha not configured the WAN interface to use the VLAN instead of the SIS0 interface! (Found it after looking through many pages of google results). Once I did that everything worked perfectly. Also gained in response time (ping times are lower) once I eliminated the router.
« Reply #6 on: May 21, 2011, 23:31:51 »
Јаневски ***
Posts: 153

If ping is lower it means that everything is working as expected.
An additional network device with lower processing capabilities is terminated and the link is chained directly to the more powerful one - m0n0.

 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines