05-10-2010
Thanks for the replies guys. Turns out adding the entries to the sco_ip/routes file did the trick.
The machines can't ping to the new VLAN but that's not an issue. Thanks again for the help guys.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I need some help adding routes in sco.
I am using SCO Openserver 5.0.4.
Basically I have 2 gateways here. The first is 10.15.1.1 and allows me access to the rest of the computers in the office and in other offices.
The other gateway is 10.15.10.2 and is the sonicwall that will allow access... (3 Replies)
Discussion started by: cstovall
3 Replies
2. Debian
Ok, I made changes to my routing tables..... which file do I modify to make the routes initialize correctly when the machine boots up? I work with all flavours of Unix/Linux... but this is an older box...
Linux, Release 2.2.14-5.0.
I did a grep for the default route in /etc, but didnt find... (2 Replies)
Discussion started by: djsal
2 Replies
3. SCO
Hi,
I add following routes manually each time system reboots:
#route add 192.168.1.0 -gateway 192.168.0.90
#route add 192.168.200.0 -gateway 192.168.0.200
Is there any way in SCO 7.1.1 to automate this route add process? i.e. each time system reboots, it automatically adds these routes in... (1 Reply)
Discussion started by: tayyabq8
1 Replies
4. Solaris
Hi there
When adding a route (or indeed deleting a route) which file is amended ? I am moving a box from one network to another and when it starts up it tries to connect run 'add net 192.x.x.x' etc etc ...but i dont want it to do that
where do I edit these route additions
cheers (5 Replies)
Discussion started by: hcclnoodles
5 Replies
5. Solaris
Hey Gurus.
My routes add using route add , are lost , after reboot.....where caould i save this routes a dont lost them ? Sun Solaris 10 is my OS.
Thanks in advance,
AGADEA. Unix ADMIN (3 Replies)
Discussion started by: aggadtech08
3 Replies
6. Solaris
Hi,
I need help to add new route:
10.252.0.138, GW 10.252.0.129 to e1000g1
and
10.252.0.10, GW 10.252.0.1 to e1000g2
tnx (4 Replies)
Discussion started by: mehrdad68
4 Replies
7. IP Networking
I would really appreciate some help with HP UX's Network Routes.
Basically, what I want to do is, I would want a system with global ip (eg: 202.144.138.122) to ping/access my HP-UX server which is with private IP address (192.168.1.23). I have all the routers/switches in between properly route... (2 Replies)
Discussion started by: damchey
2 Replies
8. SCO
Hi,
Just a question of thought. Why one needs to add static routes on Unix servers ? If I had ethernet card, it already has the settings for gateway for incoming and outgoing requests. We donot have to explicitly set the route it should take. Then what is the use... (3 Replies)
Discussion started by: dextergenious
3 Replies
9. Solaris
Hello All,
I have a Solaris 10 machine with 4 physical network interfaces configured viz. igb0, e1000g0, igb2 and e1000g2.
Out of these interfaces, I am routing all my normal monitoring and O&M activities via. igb0 and e1000g0 interfaces.
However, I am facing an issue on one of the... (4 Replies)
Discussion started by: mystition
4 Replies
LEARN ABOUT SUNOS
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)