Is it possible that the eth3 NIC is not recognized by the kernel or instantiated with a different name. Seems the udev trend is toward consistent names so that eth0 is now bus slot/port (i.e. p17p1).
Do you find eth3 in the output of 'ip link' or 'ifconfig -a'? Seems like Shorewall is saying "it just ain't there". Bill On 12/3/2015 12:04 PM, Laurie Brown wrote: > On 03/12/15 15:58, Tom Eastep wrote: >> On 12/3/2015 6:25 AM, Laurie Brown wrote: >>> On 02/12/15 20:39, Tom Eastep wrote: >>> >>> [SNIP] >>> >>> One potential clue, maybe... When I type 'shorewall dump' and let the >>> output go to stdout, it's fine, but when I type 'shorewall dump > >>> ./shorewall-dump' I get the following error: >>> >>> # shorewall dump > ./shorewall-dump >>> grep: /proc/net/nf_conntrack: No such file or directory >>> >> >> I don't believe that is relevant. > > Fair enough, but it *might* have been, so I mentioned it... > >> Again --- what happens when you execute 'shorewall enable eth3'? > > I answered that in my previous email. Here it is again: > > Hi Tom, > > Thanks for the prompt reply. This is what happens: > > ---- cut here ---- > > # shorewall enable eth3 > WARNING: Interface eth3 is not usable -- Provider VIRG (2) not Started > > ---- cut here ---- > > Cheers, Laurie. > ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
