iptables

[JD]

On 12/07/2012 03:13 PM, Tom H wrote:
> On Fri, Dec 7, 2012 at 4:25 PM, JD <jd1008 at gmail.com> wrote:
>> On 12/07/2012 10:33 AM, Tom H wrote:
>>> On Fri, Dec 7, 2012 at 11:43 AM, JD <jd1008 at gmail.com> wrote:
>>>> I just ran nm-tool and it reports - Device: wlan0 
>>>> ---------------------------------------------------------------- 
>>>> Type: 802.11 WiFi Driver: ath9k State: unmanaged Default: no HW 
>>>> Address: 00:23:80:00:03:0A So how is it that NM no longer manages 
>>>> wlan0? And why is it set to default to no? It was coming up just 
>>>> fine before In installed ufw and enabled it. In fact, I was on wifi 
>>>> connection when a respondent to my question re: iptables, suggested 
>>>> I use ufw. 
>>> Do you have any NIC other than "lo" defined in 
>>> "/etc/network/interfaces"? 
>> The is the default interfaces file that came with the installation of 
>> 12.10 or it was inherited from 12.04: auto lo eth0 wlan0 
>> allow-hotplug eth0 iface lo inet loopback 
> 1) "allow-hotplug" isn't used in Ubuntu, which uses "allow-auto" (or 
> its shorter equivalent, "auto"). 
Thanx Tom, But, I did not add the "allow-hotplug"
So why is it there in the first place?
> 2) If you don't set "managed=true" in the "ifupdown" section of 
> "/etc/NetworkManager/dispatcher.d/01ifupdown", NM won't manage a NIC 
> defined in "/etc/network/interfaces". 
But the file /etc/NetworkManager/dispatcher.d/01ifupdown
does  not even have
managed=false
and it comes from the full install.
So, why would it require the userto add
managed=true

It seems to me that ubuntu truly is lacking in rubust NM and network 
interfaces management software.
They user should NEVER have to edit these system files.
Much too dangerous and very prone to error.
It should all be done by gui software with drop-down menus/choices ...etc.
I am new to ubuntu, and I was hooping that it's system admin software 
was not left
up to the user to edit such files, but rather to configure their content 
via a
gui configuration tool.