--On February 18, 2008 5:56:21 PM -0400 "Chris Mason (Lists)" 
<[EMAIL PROTECTED]> wrote:

> My telco is moving to feeding me over fiber, breaking out with a media
> converter to one Ethernet interface. At present, I am retaining the
> static feed over copper on eth0, and taking the two new feeds via vlans
> on eth1. I have configured the static IP feed on eth1:790 as vlan 790,
> and that seems to be fine, and eth1:780 as the PPPOE feed, and brought
> up PPPOE to give me an IP, that is configured as interface ppp0.
> The ppp0 feed works fine. I have trouble understanding how to refer to
> eth1:790 in the configuration files. Should I just call it eth1 or can I
> refer to it as eth1:790?

That looks like an alias, not a vlan.  Vlan interfaces are provided by the 
8021q driver for 802.1q encapsulated vlan's and begin with vlan (unless you 
rename them), they're also full devices in their own right.  But this 
requires 802.1q capable switches and that you're actually getting traffic 
handed off with 802.1q encapsulation.  Since it's working at all, this 
probably isn't the case.

In any event, what you need to do depends on context.  eth1, refers to the 
ip address on that device, or to all aliases on that device, depending on 
context.  (In the interface context, it means all, in the address context 
it would mean the IP that is on eth1).  In the case of defining an 
interface for which traffic will traverse, you can't identify an alias 
there, as it's not an interface.  I think in most cases inside of shorewall 
you'll be referring to the interface, as it's asking about an interface, 
not an alias.

Aliases aren't really devices in and of themselves.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to