Tom Eastep wrote: > > > Those two vlans would be referred to in Shorewall as vlan179 and vlan152 > respectively. Another common naming convention would be eth0.179 and > eth0.152. > > So I have not seen another case of what you are apparently doing. Small typo in my last email. My vlans follow the naming convention you detail above. Given that, how do I refer to them in Shorewall?
12: eth1.790: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue link/ether 00:03:47:95:9d:66 brd ff:ff:ff:ff:ff:ff inet 207.42.133.74/30 brd 207.42.133.75 scope global eth1.790 inet6 fe80::203:47ff:fe95:9d66/64 scope link valid_lft forever preferred_lft forever 14: eth1.780: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue link/ether 00:03:47:95:9d:66 brd ff:ff:ff:ff:ff:ff inet6 fe80::203:47ff:fe95:9d66/64 scope link valid_lft forever preferred_lft forever 15: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1492 qdisc pfifo_fast qlen 3 link/ppp inet 209.59.77.67 peer 69.57.237.1/32 scope global ppp0 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------------------------------------------------------------------------- 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