12:14 p.m.
i am currently using f8 with most of updates install. not sure if ifup/ifdown
is among them.
i have a growing concern about operation of ifup and ifdown.
i am noticing that when i 'ifdown eth0' is still see flashing of ethernet led
on a 2wire 2701hg-b dsl modem.
it was my understanding that using ifup and ifdown that this 2 commands would
bring ethernet connection up and down, but ethernet led on modem is now making
me believe other wise.
just what do commands actually do?
as 'user' what is/are better command or commands to use without 'su' or
'sudo'
to connect ethernet to modem?
tia.
--
tc,hago.
g
.
in a free world without fences, who needs gates.
8:20 a.m.
On Sun, Jun 29, 2008 at 17:14:29 +0000,
g <geleem(a)bellsouth.net> wrote:
i am currently using f8 with most of updates install. not sure if
ifup/ifdown
is among them.
i have a growing concern about operation of ifup and ifdown.
i am noticing that when i 'ifdown eth0' is still see flashing of ethernet led
on a 2wire 2701hg-b dsl modem.
it was my understanding that using ifup and ifdown that this 2 commands would
bring ethernet connection up and down, but ethernet led on modem is now making
me believe other wise.
I don't believe that it is normal to power down the device when ifdown is
run. So the device will still flash is traffic is sent to it.
9:31 p.m.
New subject: ifdown. is it really down? [solved]
Tim wrote:
Just wondering: Are you using NetworkManager?
i was, not now. i had too many problems with it and stopped using it.
i noticed this problem after.
problem is i was blinking when i was looking. as it turned out, flash is a
'heart beat' and is continuous.
'heart beat' did not cross my mind before as i had not noticed interval.
seems that i had not watched long enough to notice that flashing was
occurring at a 20 second interval.
i was having problems with tbird and f8 and a couple other things, so
i decided to do a new install.
i pulled both ethernet and dsl cables and while walking back to desk to check
install, i noticed a double flash. i sat down and started watching led and
tried to not blink or blink after flash. it was then that i realized what was
happening.
having forgotten password for modem, i called tech support to get it reset.
afterwards i asked about blinking and they confirmed.
seems that this modem will flash twice with no ethernet cable plugged in and
single flash with cable plugged in.
--
tc,hago.
g
.
in a free world without fences, who needs gates.
11:03 p.m.
On Tue, 2008-07-01 at 16:21 +0000, g wrote:
i have 2wire configured so that nothing comes in unless i initiate.
running test at grc.com and thru bellsouth.net, i show to be full stealth,
as ping reply is also disabled.
only way, to my understanding, my ip address does not show. i may be wrong,
but i do not know where it leaks, if it does.
if i have nothing up, ie, 'ifdown' has run, or fresh boot, no tbird or ffox,
or any other internet connecting program, i see no flicker. i have sat and
watched for this for 15 - 20 minutes.
if during this time, i run 'yum update' or any derivative, or ping, i get
back a message that ethernet is disconnected or unable to connect.
if i start tbird and still 'ifdown', i will get a flicker from ethernet led
on dsl modem at a 2 minute intervals, as i have it set to check every 2
minutes, and there is no other flicker.
Just wondering: Are you using NetworkManager?
When I installed Fedora 9, and was trying to resolve a problems with
various daemons that needed a working network, I played around with ifup
and ifdown, and noticed that they weren't working properly. A taken
down network was otherwise seen as still up, but not actually working.
And trying to bring a network back up again was hit and miss, it worked,
it didn't work, the network status was correct and incorrect.
--
[tim@localhost ~]$ uname -r
2.6.25.6-55.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
5:47 p.m.
John Cornelius wrote:
I believe that you have to be root to "ifdown"
not true.
because there are other machines on the network.
2wire 2107hg-b is 4 port + wireless. at this time, it occurs with single
user on 1 port, nothing else on line. wireless disabled.
thanks for replying yannie. open to more suggestions.
btw, from where do you acquire last name of 'Cornelius'?
--
tc,hago.
g
.
in a free world without fences, who needs gates.
11:21 a.m.
John Cornelius wrote:
> I think you misunderstood. I was suggesting that normally ifdown
won't
> turn
> a device off, so it will still see ethernet traffic sent to it.
>
Even if it is powered down it is likely that one of the LEDs will flash
when traffic appears on the line. If both LEDs flash then it hasn't come
down and you can be concerned but many NICs' LEDs will flash even if the
computer is powered off if it is attached to an active Ethernet.
You are correct, however, that 'ifdown' does not power the device off,
it only takes the interface down.
i have 2wire configured so that nothing comes in unless i initiate.
running test at grc.com and thru bellsouth.net, i show to be full stealth,
as ping reply is also disabled.
only way, to my understanding, my ip address does not show. i may be wrong,
but i do not know where it leaks, if it does.
if i have nothing up, ie, 'ifdown' has run, or fresh boot, no tbird or ffox,
or any other internet connecting program, i see no flicker. i have sat and
watched for this for 15 - 20 minutes.
if during this time, i run 'yum update' or any derivative, or ping, i get
back a message that ethernet is disconnected or unable to connect.
if i start tbird and still 'ifdown', i will get a flicker from ethernet led
on dsl modem at a 2 minute intervals, as i have it set to check every 2
minutes, and there is no other flicker.
this is where i need something to watch ethernet port. when i used mandriva,
i used 'network monitor' and would like something of this type to watch.
i am considering using wireshark for this and i guess should set it up and let
it run to capture what is happening. but i would like some that uses less
screen space.
my mind is still open for suggestions.
thanks for you help and i will stay with you and this 'problem', mind stumper.
--
tc,hago.
g
.
in a free world without fences, who needs gates.
8:46 a.m.
On Tue, Jul 01, 2008 at 06:27:16 +0000,
g <geleem(a)bellsouth.net> wrote:
my understanding was that 'ifdown' _stopped_ traffic thru port interface.
I tried downing interfaces and the route tables looked to be properly
updated. Maybe there is an issue when you have downed all of the external
interfaces? (I didn't want to down my ppp link at this moment, so I didn't
test that case.)
with 'ifdown eth0'
[geo@argosyiayia ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:07:95:2b:26:23 brd ff:ff:ff:ff:ff:ff
[geo@argosyiayia ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:07:95:2b:26:23 brd ff:ff:ff:ff:ff:ff
Well that didn't really down the device, but it did remove the net block
associated with it, so I wouldn't expect any IP traffic to be sent from it.
It might still respond to external layer 2 packets sent to it. But that
wouldn't explain outbound packets matched up with when you try to run
firefox.
with 'ifup eth0'
[geo@argosyiayia ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:07:95:2b:26:23 brd ff:ff:ff:ff:ff:ff
[geo@argosyiayia ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:07:95:2b:26:23 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.97/24 brd 192.168.1.255 scope global eth0
inet6 fe80::207:95ff:fe2b:2623/64 scope link
valid_lft forever preferred_lft forever
3:53 a.m.
Bruno Wolff III wrote:
On Mon, Jun 30, 2008 at 22:47:54 +0000,
g <geleem(a)bellsouth.net> wrote:
> Bruno Wolff III wrote:
>
>> I don't believe that it is normal to power down the device when ifdown is
>> run. So the device will still flash is traffic is sent to it.
>>
> i do not 'power down'. i just use 'ifdown eth0' in a script.
>
I think you misunderstood. I was suggesting that normally ifdown won't turn
a device off, so it will still see ethernet traffic sent to it.
Even if it is powered down it is likely that one of the LEDs will flash
when traffic appears on the line. If both LEDs flash then it hasn't come
down and you can be concerned but many NICs' LEDs will flash even if the
computer is powered off if it is attached to an active Ethernet.
You are correct, however, that 'ifdown' does not power the device off,
it only takes the interface down.
John Cornelius
2:16 a.m.
g wrote:
i am not sure of modem led, will check manual again after sending
this.
active i see is i do believe from within, as it occurs when i start tbird
or firefox
ok. did not want to comment on modem's leds until i read for sure.
led: state condition
ethernet steady connected
blink traffic
dsl steady connected
blink connecting
internet steady connected
blink connecting
what i was thinking, just i wanted to be sure about dsl and internet they
connected.
knowns:
tbird and ffox do flash ethernet during 'ifdown'
ping and yum do not, with reply that connection is down.
would like:
a dual graphic monitor as 'network monitor' in mandriva.
suggestions?
--
tc,hago.
g
.
in a free world without fences, who needs gates.
1:27 a.m.
Bruno Wolff III wrote:
I think you misunderstood. I was suggesting that normally ifdown
won't turn
a device off, so it will still see ethernet traffic sent to it.
clearer.
my understanding was that 'ifdown' _stopped_ traffic thru port interface.
i am not sure of modem led, will check manual again after sending this.
active i see is i do believe from within, as it occurs when i start tbird
or firefox
This makes it sound like the interface is still active. You can use
the ip
command to get more information about your network devices. ip link will
show you the status of each link and ip addr will show you the addresses
bound to each link. That might help diagnose what's going on.
with 'ifdown eth0'
[geo@argosyiayia ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:07:95:2b:26:23 brd ff:ff:ff:ff:ff:ff
[geo@argosyiayia ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:07:95:2b:26:23 brd ff:ff:ff:ff:ff:ff
with 'ifup eth0'
[geo@argosyiayia ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:07:95:2b:26:23 brd ff:ff:ff:ff:ff:ff
[geo@argosyiayia ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:07:95:2b:26:23 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.97/24 brd 192.168.1.255 scope global eth0
inet6 fe80::207:95ff:fe2b:2623/64 scope link
valid_lft forever preferred_lft forever
[geo@argosyiayia ~]$
will do a 'find' on manual. back in a short.
--
tc,hago.
g
.
in a free world without fences, who needs gates.
12:42 a.m.
On Mon, Jun 30, 2008 at 22:47:54 +0000,
g <geleem(a)bellsouth.net> wrote:
Bruno Wolff III wrote:
> I don't believe that it is normal to power down the device when ifdown is
> run. So the device will still flash is traffic is sent to it.
i do not 'power down'. i just use 'ifdown eth0' in a script.
I think you misunderstood. I was suggesting that normally ifdown won't turn
a device off, so it will still see ethernet traffic sent to it.
also, now thinking about mentioning it, when i bring up thunderbird,
there are
double flashes, 3 to 4 more doubles, sometimes 5 of ethernet led on 2wire.
This makes it sound like the interface is still active. You can use the ip
command to get more information about your network devices. ip link will
show you the status of each link and ip addr will show you the addresses
bound to each link. That might help diagnose what's going on.
5:47 p.m.
Bruno Wolff III wrote:
I don't believe that it is normal to power down the device when
ifdown is
run. So the device will still flash is traffic is sent to it.
i do not 'power down'. i just use 'ifdown eth0' in a script.
also, now thinking about mentioning it, when i bring up thunderbird, there are
double flashes, 3 to 4 more doubles, sometimes 5 of ethernet led on 2wire.
out of curiousness, with fresh boot, no 'ifup', i tried as root,
'yum check-update'
which returned,
'Temporary failure in name resolution')>Trying other mirror.'
then,
'ping 111.11.11.1'
received,
'connect: Network is unreachable'
to me, this shows tbird is doing something to flash led.
thanks for reply, bruno. open to more suggestions.
--
tc,hago.
g
.
in a free world without fences, who needs gates.
10:14 p.m.
g wrote:
i am currently using f8 with most of updates install. not sure if
ifup/ifdown
is among them.
i have a growing concern about operation of ifup and ifdown.
i am noticing that when i 'ifdown eth0' is still see flashing of
ethernet led
on a 2wire 2701hg-b dsl modem.
it was my understanding that using ifup and ifdown that this 2
commands would
bring ethernet connection up and down, but ethernet led on modem is
now making
me believe other wise.
just what do commands actually do?
as 'user' what is/are better command or commands to use without 'su'
or 'sudo'
to connect ethernet to modem?
tia.
I believe that you have to be root to "ifdown" but even after the
interface is down there will be an indication of traffic on the NIC
because there are other machines on the network.
John Cornelius
5784
days inactive
5790
days old
12 comments
4 participants
participants (4)
-
Bruno Wolff III -
g -
John Cornelius -
Tim