On Thursday 30,January,2014 05:24 AM, Andrei POPESCU wrote:
> On Mi, 29 ian 14, 17:42:53, lina wrote:
>>
>> # grep managed /etc/NetworkManager/NetworkManager.conf
>> managed=false
>
> This means it should be safe to simply purge Network Manager unless...
>
>> I don't use wifi, if I need wifi, I
On Mi, 29 ian 14, 17:42:53, lina wrote:
>
> # grep managed /etc/NetworkManager/NetworkManager.conf
> managed=false
This means it should be safe to simply purge Network Manager unless...
> I don't use wifi, if I need wifi, I need "modprobe b43".
...you do need it for wireless. Not exactly sure
Hi.
On Wed, 29 Jan 2014 14:39:37 +0800
lina wrote:
> sorry, I rebooted again after clearing something messy, here is the
> output with the new pid,
>
> # ps -eo pid,ppid,args | grep 2981
>
> 2981 1 dhclient -v -pf /run/dhclient.eth0.pid -lf
> /var/lib/dhcp/dhclient.eth0.leases eth0
> 65
On Wed, 29 Jan 2014 21:44:36 +0800
lina wrote:
> BTW,
>
> :/etc/resolvconf# more interface-order
> # interface-order(5)
> lo.inet*
> lo.dnsmasq
> lo.pdnsd
> lo.!(pdns|pdns-recursor)
> lo
> tun*
> tap*
> hso*
> em+([0-9])?(_+([0-9]))*
> p+([0-9])p+([0-9])?(_+([0-9]))*
> eth*
> ath*
> wlan*
> ppp*
BTW,
:/etc/resolvconf# more interface-order
# interface-order(5)
lo.inet*
lo.dnsmasq
lo.pdnsd
lo.!(pdns|pdns-recursor)
lo
tun*
tap*
hso*
em+([0-9])?(_+([0-9]))*
p+([0-9])p+([0-9])?(_+([0-9]))*
eth*
ath*
wlan*
ppp*
*
These things seems so big for me to get a fully understanding.
--
To UNSUBSCRI
On Wednesday 29,January,2014 05:03 PM, Andrei POPESCU wrote:
> On Mi, 29 ian 14, 14:39:37, lina wrote:
>>
>> # dpkg -l 'network-manager*'
>
> Just for you info, you don't need root for this command (generally any
> command that just provides information).
>
>> Desired=Unknown/Install/Remove/Purg
On Mi, 29 ian 14, 14:39:37, lina wrote:
>
> # dpkg -l 'network-manager*'
Just for you info, you don't need root for this command (generally any
command that just provides information).
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig
> Why, there's new output. Instead of 3 dhclients you've got 2.
:)
> PIDs are different from the last time too. That's a start, at least.
>
>
>> I don't know how to check further, the /proc/3321/ and /proc/3125 give
>> me no clue.
>
> ps -eo pid,ppid,args | grep 3321
> ps -eo pid,ppid,args |
On Wed, 29 Jan 2014 13:57:01 +0800
lina wrote:
> I tried this, to get a better guarantee, I rebooted late, here is the
> new output:
>
> udp0 0 0.0.0.0:68 0.0.0.0:*
> 3321/dhclient
> udp0 0 0.0.0.0:68 0.0.0.0:*
> 3125/dhclient
On Wednesday 29,January,2014 12:56 PM, Reco wrote:
> Hi.
>
> On Wed, 29 Jan 2014 11:55:52 +0800
> lina wrote:
>
>> I comment the last
>> iface eth0 inet dhcp
>
> Correct /etc/network/interfaces would be (notice that 'allow-hotplug'
> is above 'iface eth0'):
>
> # The loopback network interfac
Hi.
On Wed, 29 Jan 2014 11:55:52 +0800
lina wrote:
> I comment the last
> iface eth0 inet dhcp
Correct /etc/network/interfaces would be (notice that 'allow-hotplug'
is above 'iface eth0'):
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-h
On Wednesday 29,January,2014 11:15 AM, lina wrote:
>>> >> tcp6 0 0 :::143 :::*
>>> >> LISTEN 2731/couriertcpd
>> >
>> > Running IMAP server on a desktop is an uncommon thing.
>> > Do you really need it?
> I have no much idea how did I introduce this at the first pl
>> 2] I don't know why the dhclient occupy several ports to listen, and
>> what's a little annoying is that seems my IP address barely changed even
>> I reboot after one night.
>
>> tcp6 0 0 :::143 :::*
>> LISTEN 2731/couriertcpd
>
> Running IMAP server on a deskt
On Tue, 28 Jan 2014 15:00:43 +0800
lina wrote:
> 1] about port 631, can I turn it off? since I only print very
> occasionally, I don't know the real purpose of cupsd;
As others said, listening port 631 on loopback interface is not a
problem.
>
> 2] I don't know why the dhclient occupy several
On Tue, Jan 28, 2014 at 09:53:05PM +0800, lina wrote:
>
> >
> > STOP NTP!
> > ntpd is currently abused as a DDOS attack vector.
> > If your ntpd responds to ntpdc -n -c monlst
>
> Oh it responds, responds badly:
>
> $ ntpdc -n -c monlst < 172.21.100.159 >
> bash: syntax error near unexpected t
On Tuesday 28,January,2014 09:32 PM, Sven Hartge wrote:
> Just check if the following lines are present and active in your
> ntp.conf:
>
> restrict -4 default kod nomodify notrap nopeer noquery
> restrict -6 default kod nomodify notrap nopeer noquery
Thanks, they are.
# more ntp.conf | grep rest
>
> STOP NTP!
> ntpd is currently abused as a DDOS attack vector.
> If your ntpd responds to ntpdc -n -c monlst
Oh it responds, responds badly:
$ ntpdc -n -c monlst < 172.21.100.159 >
bash: syntax error near unexpected token `newline'
$ ntpdc -n -c 172.21.100.159
***Command `172.21.100.159' u
Henning Follmann wrote:
> On Tue, Jan 28, 2014 at 01:43:17PM +0800, lina wrote:
>> I read something online, and wonder:
>> 1] shall I close the port 123
>> 2] disable ipv6
>>
>> Shall I follow the advice from https://wiki.debian.org/DebianIPv6 to
>> turn off the ipv6 in wheezy as in squeeze,
>
On Tue, Jan 28, 2014 at 01:43:17PM +0800, lina wrote:
> Hi,
>
> I read something online, and wonder:
> 1] shall I close the port 123
> 2] disable ipv6
>
> Shall I follow the advice from https://wiki.debian.org/DebianIPv6 to
> turn off the ipv6 in wheezy as in squeeze,
>
> Thanks,
>
STOP NTP!
Hi
On Tue, Jan 28, 2014 at 03:00:43PM +0800, lina wrote:
> >> I read something online, and wonder:
> >> 1] shall I close the port 123
> >
> > Probably you should, unless you're providing ntp to some other hosts.s
>
> I have disabled the ntp. Here is other two things:
>
> 1] about port 631, can
On 28/01/14 18:00, lina wrote:
>>> I read something online, and wonder:
>>> 1] shall I close the port 123
>>
>> Probably you should, unless you're providing ntp to some other hosts.s
>
> I have disabled the ntp. Here is other two things:
>
> 1] about port 631, can I turn it off? since I only prin
>> I read something online, and wonder:
>> 1] shall I close the port 123
>
> Probably you should, unless you're providing ntp to some other hosts.s
I have disabled the ntp. Here is other two things:
1] about port 631, can I turn it off? since I only print very
occasionally, I don't know the real
Hi.
On Tue, 28 Jan 2014 13:43:17 +0800
lina wrote:
> Hi,
>
> I read something online, and wonder:
> 1] shall I close the port 123
Probably you should, unless you're providing ntp to some other hosts.
> 2] disable ipv6
Is there something malfunctioning on this host? Or is there any service
t
23 matches
Mail list logo
