Project

General

Profile

Actions

Bug #7040

closed

Issue when disabling an interface

Added by Alexandre Paradis about 7 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
12/26/2016
Due date:
% Done:

0%

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

Description

I am using the interfaces like this :

ix0
ix0_vlan1
ix0_vlan35

I just want to disable only ix0, but still having the vlan 1 & 35 working.

Instead the physical interface is being shutdown completely.

I did a cold start on the pfsense box, and the system was working as intended (ix0 disabled, vlan 1 & 35 working).

i'm using :
2.3.3-DEVELOPMENT (amd64)
built on Sun Dec 25 22:21:09 CST 2016

Actions #1

Updated by Alhusein Zawi over 1 year ago

  • Status changed from New to Resolved

Disabling the parent interface will stop the connectivity to all connected networks/VLANs , the vlan is up and you can ping the vlan interface inside pfsense but it will not be able to communicate.

I can ping the vlan interface 10.100.100.1 when the parent interface is down :

C:\Users\I>ping 10.100.100.1 -t

Pinging 10.100.100.1 with 32 bytes of data:
Reply from 10.100.100.1: bytes=32 time=21ms TTL=64
Reply from 10.100.100.1: bytes=32 time=3ms TTL=64
Reply from 10.100.100.1: bytes=32 time=6ms TTL=64

while the client 10.100.100.100 in same vlan is not reachable:

C:\Users\I>ping 10.100.100.100 -t

Pinging 10.100.100.100 with 32 bytes of data:
Reply from 192.168.254.200: Destination host unreachable.
Reply from 192.168.254.200: Destination host unreachable.
Reply from 192.168.254.200: Destination host unreachable.
Reply from 192.168.254.200: Destination host unreachable.

this is a normal behavior in most Switches/Routers .

Actions

Also available in: Atom PDF