09-12-2002
Check out this
post and the link to
SCO Default router. This should give you a clue on how to do it.
As far as loopback, all systems have it. It's the localhost (127.0.0.1), a way for the server to connect to itself (part of the kernel). It isn't part of your problem of getting traffic from one card to the other.
10 More Discussions You Might Find Interesting
1. SCO
I have got a Sco Unix Server, i want to connect some windows workstations. What configurations do i need to make on server and or workstation? (1 Reply)
Discussion started by: tpurazi1
1 Replies
2. Solaris
Hi,
I'm looking for a command to be able to list all my network cards available on my server.
With the command "ifconfig - a", I can only see to configured network card(s)
Any idea ? :confused:
Thanks a lot for your help,
Fabien (5 Replies)
Discussion started by: unclefab
5 Replies
3. SCO
Hello Guys,
We have an old PC running on SCO Unix V. Is there any sites where i can get manual/procedures on how to install and configure Network. Thanks (2 Replies)
Discussion started by: nrcuevas
2 Replies
4. AIX
The title speaks for itself. I have never attempted this but understand there is a way to use two network cards (en0 and en1) with the same IP address so as to load balance the traffic flow through both cards. Anyone know the answer? (4 Replies)
Discussion started by: johnf
4 Replies
5. Solaris
Hi all,
I have a server running with Solaris and I have 2 Pci cards installed on this server (since a while), 1 with 4 coppers connections output and one with a Fiber network connection output.
Today, this server is using the on board network connection (Ce0).
How can I find the other... (7 Replies)
Discussion started by: unclefab
7 Replies
6. Solaris
Hi All,
Hope you are all doing good.
In MY unix box i have 2 network cards. I want to know what if one network card fails. Does the second one will automatically take all the traffic or how it is supposed to work. Also in my logs i am seeing below errors . Can you throw some light of this qfe... (3 Replies)
Discussion started by: Krrishv
3 Replies
7. Solaris
Hi all
I hate networking, I hate everything to do with it. Its something I do in anger in one contract, then forget. This is more of a question / than a problem.
So, on a solaris 10 server, using older qfe cards, Ive got a sun truck with 4 nics (qfe0,3,4,7), and a ipmp pair (hemo0,qfe1).... (2 Replies)
Discussion started by: sbk1972
2 Replies
8. Hardware
Hello everybody,
I'm having troubles with Slackware 13.1 and network cards.
I have one on-board Ethernet card (which is recognized and works okay) and a PCI Ethernet card (which is also recognized, but doesn't appear in 'ifconfig -a'). If i run a 'lspci', i can see the kernel recognized the... (5 Replies)
Discussion started by: semash!
5 Replies
9. SCO
hi
i installed sco unix open server 5.0.7 on virtual machine vmware and runing it,
its work perfect and good.
now how i can configuare network at scoadmin that i able to access nework ?
---------- Post updated at 08:56 AM ---------- Previous update was at 01:47 AM ----------
nobody can... (2 Replies)
Discussion started by: farzad226
2 Replies
10. SCO
hi .I've installed an operating system SCO in HP Z400 and network cards ZyXEL model FN312 with Chipset RTL8139D put it on .network card installed but do not display network card with command ifconfig -a in list and just show loopback.
show message :
dlpid:unable to open network adapter driver... (14 Replies)
Discussion started by: moein.mojtaba
14 Replies
LEARN ABOUT POSIX
systemd-networkd.service
SYSTEMD-NETWORKD.SERVICE(8) systemd-networkd.service SYSTEMD-NETWORKD.SERVICE(8)
NAME
systemd-networkd.service, systemd-networkd - Network manager
SYNOPSIS
systemd-networkd.service
/lib/systemd/systemd-networkd
DESCRIPTION
systemd-networkd is a system service that manages networks. It detects and configures network devices as they appear, as well as creating
virtual network devices.
To configure low-level link settings independently of networks, see systemd.link(5).
systemd-networkd will create network devices based on the configuration in systemd.netdev(5) files, respecting the [Match] sections in
those files.
systemd-networkd will manage network addresses and routes for any link for which it finds a .network file with an appropriate [Match]
section, see systemd.network(5). For those links, it will flush existing network addresses and routes when bringing up the device. Any
links not matched by one of the .network files will be ignored. It is also possible to explicitly tell systemd-networkd to ignore a link by
using Unmanaged=yes option, see systemd.network(5).
When systemd-networkd exits, it generally leaves existing network devices and configuration intact. This makes it possible to transition
from the initrams and to restart the service without breaking connectivity. This also means that when configuration is updated and
systemd-networkd is restarted, netdev interfaces for which configuration was removed will not be dropped, and may need to be cleaned up
manually.
CONFIGURATION FILES
The configuration files are read from the files located in the system network directory /lib/systemd/network, the volatile runtime network
directory /run/systemd/network and the local administration network directory /etc/systemd/network.
Networks are configured in .network files, see systemd.network(5), and virtual network devices are configured in .netdev files, see
systemd.netdev(5).
SEE ALSO
systemd(1), systemd.link(5), systemd.network(5), systemd.netdev(5), systemd-networkd-wait-online.service(8)
systemd 237 SYSTEMD-NETWORKD.SERVICE(8)