On Sun, 2016-08-21 at 11:59 -0700, Samuel Sieb wrote:
> Where do you get the gigabit from?
Misread the data...
--
tim@localhost ~]$ uname -rsvp
Linux 3.19.8-100.fc20.i686 #1 SMP Tue May 12 17:42:35 UTC 2015 i686
All mail to my mailbox is automatically deleted, there is no point trying
to
On 08/20/2016 08:29 AM, Tim wrote:
Allegedly, on or about 20 August 2016, Angelo Moreschini sent:
wlp3s0: flags=4163 mtu 1500
inet 10.0.0.4 netmask 255.255.255.0 broadcast 10.0.0.255
inet6 fe80::d253:49ff:fe32:3254 prefixlen 64 scopeid 0x20
ether
gt; in order to use the ssh services, I looked for the internet address of
> > my computer, and the ifconfig command gave the following output that I
> > have difficulty 'to interpret :
> >
> > ---
> >
> > [angelo_dev@localhost ~]$ sudo ifconfig
> >
>
Allegedly, on or about 20 August 2016, Angelo Moreschini sent:
> enp4s0: flags=4099 mtu 1500
> ether 60:02:92:2d:2a:1f txqueuelen 1000 (Ethernet)
Going by the device name, enp4s0 would be wired ethernet, but not in use
(because it had no assigned addresses, that string of
Le 20/08/2016 12:09, Angelo Moreschini a écrit :
> Hi,
>
> in order to use the ssh services, I looked for the internet address of
> my computer, and the ifconfig command gave the following output that I
> have difficulty 'to interpret :
>
> ---
>
> [an
hi
enp4s0 is wire NIC and wlp3s0 is wireless NIC
On Sat, Aug 20, 2016 at 2:39 PM, Angelo Moreschini <
mrangelo.fed...@gmail.com> wrote:
> Hi,
>
> in order to use the ssh services, I looked for the internet address of my
> computer, and the ifconfig command gave the follo
Den 2016-08-20 kl. 12:09, skrev Angelo Moreschini:
> Hi,
>
> in order to use the ssh services, I looked for the internet address of
> my computer, and the ifconfig command gave the following output that I
> have difficulty 'to interpret :
>
> ---
>
> [an
Hi,
in order to use the ssh services, I looked for the internet address of my
computer, and the ifconfig command gave the following output that I
have difficulty
'to interpret :
---
[angelo_dev@localhost ~]$ sudo ifconfig
enp4s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether
Hello,
I am using a 3G connection, ie ppp0
I wish to have information about this interface (by using ifconfig)
when I connect and disconnect to the network. However, when it
disconnect the network, the interface is already gone when
I make the ifconfig.
I use /etc/NetworkManager/dispatcher.d
Once upon a time, Paul Allen Newell pnew...@cs.cmu.edu said:
Problem is solved as far as I am concerned, even though I am certain
there is probably some way to get a unique token. Since my goal is to
get the machine up and running so I can be a user on it, I learned from
all the material
on my part or a potential problem
I have three F16 machines, one x86_64 and two i383/686. If I run /sbin/ifconfig
on
them, I get (short summary of):
x86_64: eth0
i686: em1
Looking in /etc/sysconfig/network-scripts, I can see only ifcfg-em1 and no
ifcfg-eth0 on all the machines (x86_64 and i686
Am 27.05.2012 14:59, schrieb Bill Davidsen:
The problem with naming is that for every server run by experienced sysadmins
experienced sysadmins should not have a problem to open
/etc/udev/rules.d/70-persistent-net.rules and define
eth0
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
On 05/27/2012 08:59 PM, Bill Davidsen wrote:
I really want to be able to put any card in any slot and match the label on
the
cable to the label on the NIC, and have scripts which don't have to be
needlessly
complex to discover the name of the interface
OK, but you do realize that you are
On Sun, 27 May 2012 23:39:06 +0800
Ed Greshko wrote:
If,
for example, you (or someone who works for you) change a network card whose
cable was
labeled eth0 you will need to remember to edit the 70-persistent-net.rules.
That always seemed dumb to me. It can tell (or make a good guess)
if the
On 5/27/2012 5:59 AM, Bill Davidsen wrote:
I think he wants the single, known interface to have a single known
name, and not some random characters determined by the whichness of what.
Bill (and Reindl, Ed, and Tom who replied to Bill):
Thanks for the addition comments.
The statement
issue.
All that aside If you have a system with a single interface you can always
do
[egreshko@meimei test]$ /sbin/ifconfig | grep 'inet ' | grep -v '127.0.0.1' |
cut -d
: -f 2 | awk '{ print $1}'
192.168.0.18
Ed:
With all due respect, its become clear to me that ifconfig is obsolete
on system architecture. That seems to be your main
issue.
All that aside If you have a system with a single interface you can
always
do
[egreshko@meimei test]$ /sbin/ifconfig | grep 'inet ' | grep -v '127.0.0.1'
| cut -d
: -f 2 | awk '{ print $1}'
192.168.0.18
Ed:
With all
On 5/22/2012 11:33 PM, Ed Greshko wrote:
Maybe the question you should be asking is this? I don't like the
names that have been assigned to my network interfaces. How can I
change them to be what I want them to be?
Ed:
Okay, that's a good question that I hadn't considered. So do you happen
On 05/23/2012 02:46 PM, Paul Allen Newell wrote:
Okay, that's a good question that I hadn't considered. So do you happen to
know how
to change the names?
No. Not something that I've needed or wanted to do.
--
Never be afraid to laugh at yourself, after all, you could be missing out on
Am 23.05.2012 08:17, schrieb Paul Allen Newell:
With all due respect, its become clear to me that ifconfig is obsolete and a
solution which uses it doesn't have a
future. Can you try to get the ip address with command ip on a i686 and
x86_64 system without having to run a
different
On 5/23/2012 1:07 AM, Reindl Harald wrote:
edit /etc/udev/rules.d/70-persistent-net.rules (ONE LINE, replace MAC with
yours)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*, ATTR{address}==00:50:56:bd:00:27,
ATTR{dev_id}==0x0,
ATTR{type}==1, KERNEL==eth*, NAME=eth0
__
this
On 05/22/2012 09:12 PM, Paul Allen Newell wrote:
Hello:
As I continue dealing with iptables, another issue has come up that I
can't tell is a mis-understanding on my part or a potential problem
I have three F16 machines, one x86_64 and two i383/686. If I run
/sbin/ifconfig on them, I get
[comments inline]
On 5/23/2012 1:53 PM, Phil Meyer wrote:
Just to add fuel to the fire:
Soon more and more systems will have UEFI as well as, or instead of
the old BIOS. On most newer sever class systems, the traditional BIOS
is *emulated* in the EUFI.
The EUFI, and, therefore, newer
x86_64 and two i383/686. If I run
/sbin/ifconfig on them, I get (short summary of):
x86_64: eth0
i686: em1
Looking in /etc/sysconfig/network-scripts, I can see only ifcfg-em1
and no ifcfg-eth0 on all the machines (x86_64 and i686).
The closest bugzilla I can see if 784314 but it looks like
or a potential problem
I have three F16 machines, one x86_64 and two i383/686. If I run
/sbin/ifconfig on
them, I get (short summary of):
x86_64: eth0
i686: em1
Looking in /etc/sysconfig/network-scripts, I can see only ifcfg-em1 and no
ifcfg-eth0 on all the machines (x86_64 and i686
this?
[egreshko@meimei net]$ /sbin/ifconfig p128p1 | grep 'inet ' | cut -d : -f 2 |
awk '{
print $1}'
192.168.0.18
Maybe if you posted the output of commands on your system and asked questions
based
on the output it would make more senseat least to me.
Ed:
Thanks for reply.
First problem
]$ /sbin/ifconfig | grep 'inet ' | grep -v '127.0.0.1' |
cut -d
: -f 2 | awk '{ print $1}'
192.168.0.18
--
Never be afraid to laugh at yourself, after all, you could be missing out on
the joke
of the century. -- Dame Edna Everage
--
users mailing list
users@lists.fedoraproject.org
I have got inconsistent eth devices between what Fedora Gnome Desktop
is telling me and what ifconfig is telling me and what 'service
network restart' is telling me.
Do I have to do a reinstall or is there some way of resetting things ?
Many thanks in advance,
Aaron
--
users mailing list
users
count.
Also, two device interfaces, eth0 and ra0 calculate two different
broadcast addresses even when given the exact same netmask and ip
address? (as reported by ifconfig). Are these computed by the kernel or
the driver?
Anyone seen something similar in the past?
Thank You
Fred Farleigh
29 matches
Mail list logo