On 03/12/15 17:18, Bill Shirley wrote:
> 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
Hi Bill,
The interface is definitely up.
# ip link
[SNIP]
5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP mode DEFAULT group default qlen 1000
link/ether 00:30:18:a1:22:bd brd ff:ff:ff:ff:ff:ff
# ifconfig -a
eth3 Link encap:Ethernet HWaddr 00:30:18:a1:22:bd
inet addr:82.9.127.74 Bcast:255.255.255.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:163 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:25004 (25.0 KB) TX bytes:1020 (1.0 KB)
Cheers, Laurie.
--
---------------------------------------------------------------------
www.convergent-ict.com
You manage your business.
We manage your IT.
---------------------------------------------------------------------
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
