Operating Systems Solaris Add Static Routes to new physical address Post 302284788 by incredible on Friday 6th of February 2009 10:32:11 AM
#cd /etc/rc2.d
#vi S99staticroute
Add the following line
route add 10.252.0.138 10.252.0.129
route add 10.252.0.10 10.252.0.1

reboot
 
Test Your Knowledge in Computers #52
Difficulty: Easy
A magnetic disc array is an example of offline storage.
True or False?

10 More Discussions You Might Find Interesting

1. AIX

Physical and Logical IP address

Hi all I need command to give logical and physical IP Address for my machine. thank you (1 Reply)
Discussion started by: magasem
1 Replies

2. AIX

Static Routes question

I added a static route through smit using: Communications applications and Services ==> TCIP/IP ==> Further Configuration ==> Static Routes ==> Add a Static Route ==> Route Type of host Filled in Destination Address, Default Gateway Address and Network Interface of en0. This... (2 Replies)
Discussion started by: jyoung
2 Replies

3. UNIX for Dummies Questions & Answers

How to apply static ip address

Hi there, I have a Debian 5.0 server newly installed. By default, the ip address is given by dhcp. pegase:~# grep '^' /etc/network/interfaces auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet dhcp pegase:~# head -2 /etc/hosts 127.0.0.1 localhost 127.0.1.1 ... (1 Reply)
Discussion started by: chebarbudo
1 Replies

4. Solaris

How to Configure a Static Ip Address

Hello friend, I am new in UNIX, but I want to learn a lot Well I have a problem to try to configure my PC with a static IP Address (IP 192.168.1.39, Mask 255.255.255.0, gateway 192.168.1.1) (DNS 200.48.225.130 and 200.48.225.146). where are the file that I must be change? The SO is Sun Solaris... (15 Replies)
Discussion started by: andresguillen
15 Replies

5. UNIX for Dummies Questions & Answers

What would the physical address be for virtual address?

Hi guys, I got one problem which I definetily no idea. What would the physical address be for virtual address? 1) 2ABC 2) 3F4B Here is the page table:see attached Thank you sos sososososso much!! (0 Replies)
Discussion started by: lemon_06
0 Replies

6. Red Hat

Purpose of Static IP address through DHCP

Hi All, Could you please explain the purpose of assigning the static IP by using the DHCP Concept. Like by using the clients MAC address we assign the static IP Address. Waiting for your reply. Thanks in Advance. (6 Replies)
Discussion started by: Sharath Kumar
6 Replies

7. SCO

Static routes in 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

8. Red Hat

Centos-quick way to check if static routes are persistent

Hi All, Is there a quick way to check whether the current routes on my centos are persistent or not before rebooting ? i can take a route -n output but i may completely lost access to my server if the routes are gone. thanks. (1 Reply)
Discussion started by: coolatt
1 Replies

9. IP Networking

Free subdomain to my IP Address and Static IP

Hi all, I would need to register a random free subdomain address and associate that to my IP Address. Any suggestion of a good service? Also I don't have a static IP but i remember that there are services that automatically reset the right IP address behind the subdomain but i don't remember... (1 Reply)
Discussion started by: Tameto
1 Replies

10. Red Hat

How to set static routes for packets, within the same Network?

I have three systems A,B,C. I want to configure A in such a way that all packets from A to C goes via B. I tried: 1. ip route add 'ip of C' via 'ip of B' 2. route add -net 'net address' netmask gw 'ip of B' These commands work initially when I try a ping or traceroute and expire after... (2 Replies)
Discussion started by: kanak
2 Replies
NATMIP(4)						   BSD Kernel Interfaces Manual 						 NATMIP(4)

NAME
natmip -- IP over ATM PVCs SYNOPSIS
device atm options NATM DESCRIPTION
The NATM protocol stack includes support for IP over ATM. Without any additional signalling stacks or other modules it is possible to build a CLIP (classical IP over ATM) network based on PVCs. An ATM network card (en0 in this example) is configured for IP by something like: ifconfig en0 128.252.200.1 netmask 0xffffff00 up IP routing is done with special interface routes (routes with directly reachable destinations) with a link layer gateway address. The link layer address specifies the ATM interface through which the destination can be reached, the virtual channel that connects to the destination and the ATM characteristics of this channel. The address part of the link layer address (see link_addr(3)) consists of a fixed part (the first 5 bytes) and a part that depends on the kind of the PVC (UBR, CBR, VBR, ABR). Multi-byte values are big-endian encoded: the bytes with the lower numbers contain the higher order bits. byte 0 Is a flag byte. Currently only flag 0x20 is used. When set, all IP frames are LLC/SNAP encapsulated before putting them into an AAL5 frame. Setting this flag is recommended and allows interoperability with other CLIP implementations. Note that BPF works only with LLC/SNAP encapsulation. byte 1 This is the VPI of the channel. bytes 2...3 VCI of the channel. Must not be zero. byte 4 Traffic type. One of 0 (UBR), 1 (CBR), 2 (ABR), 3 (VBR). The variable part for UBR connections may be either empty or three bytes: bytes 5...7 Specifies the peak cell rate for UBR. The variable part for CBR connections must be three bytes: bytes 5...7 Specifies the peak cell rate for CBR. The variable part for VBR connections must be 9 bytes long and specifies three values: bytes 5...7 Specifies the peak cell rate for VBR. bytes 8...10 This is the sustainable cell rate. bytes 11...13 The maximum burst size. The variable part for ABR connections must be 19 bytes long and specifies the following values: bytes 5...7 Specifies the peak cell rate for ABR. bytes 8...10 The minimum cell rate. bytes 11...13 The initial cell rate. bytes 14...16 The transient buffer exposure. byte 17 The NRM value. byte 18 The TRM value. bytes 19...20 The ADTF value. byte 21 The rate increase factor (RIF). byte 22 The rate decrease factor (RDF). byte 23 The cutoff decrease factor (CDF). To add a PVC the route(8) utility can be used: route add -iface <remote IP address> -link <iface>:<lladdr> The iface is the ATM interface through which remote IP address can be reached and lladdr is the link layer address as a string of dot-sepa- rated, hexadecimal bytes. NATM also supports the old, original format. This consists of 4 byte link layer addresses (and the channels are implicit UBR): byte 0 Flags: 0x01 use AAL5. 0x02 if using AAL5, use an LLC/SNAP header. Thus, parameter 3 means AAL5 and LLC/SNAP encapsulation (this is the required setting for interworking with other CLIP clients). Note that BPF works only with LLC/SNAP encapsulation. byte 1 VPI for the channel bytes 2...3 VCI for the channel EXAMPLES
Suppose you have 3 hosts 128.252.200.1, 128.252.200.2 and 128.252.200.3 connected by ATM through PVCs: between 128.252.200.1 and 128.252.200.2: 0xc9 UBR between 128.252.200.1 and 128.252.200.3: 0xca VBR between 128.252.200.2 and 128.252.200.3: 0xcb CBR The parameters for the VBR channel are: PCR 50000, SCR 10000, MBS 10. The peak cell rate for the CBR channel is 100000. To enable the links use the following commands: on host 128.252.200.1: ifconfig en0 128.252.200.1 netmask 0xffffff00 up route add -iface 128.252.200.2 -link en0:3.0.0.c9.0 route add -iface 128.252.200.3 -link en0:3.0.0.ca.3.0.c3.50.0.27.10.0.0.a on host 128.252.200.2: ifconfig en0 128.252.200.2 netmask 0xffffff00 up route add -iface 128.252.200.1 -link en0:3.0.0.c9.0 route add -iface 128.252.200.3 -link en0:3.0.0.cb.1.1.86.a0 on host 128.252.200.3: ifconfig en0 128.252.200.3 netmask 0xffffff00 up route add -iface 128.252.200.1 -link en0:3.0.0.ca.3.0.c3.50.0.27.10.0.0.a route add -iface 128.252.200.2 -link en0:3.0.0.cb.1.1.86.a0 This can also be done in rc.conf(5): on host 128.252.200.1: network_interfaces="lo0 en0" ifconfig_en0="inet 128.252.200.1 netmask 255.255.255.0" static_routes="host2 host3" route_host2="-iface 128.252.200.2 -link en0:3.0.0.c9.0" route_host3="-iface 128.252.200.3 -link en0:3.0.0.ca.3.0.c3.50.0.27.10.0.0.a" on host 128.252.200.2: network_interfaces="lo0 en0" ifconfig_en0="inet 128.252.200.2 netmask 255.255.255.0" static_routes="host1 host3" route_host1="-iface 128.252.200.1 -link en0:3.0.0.c9.0" route_host3="-iface 128.252.200.3 -link en0:3.0.0.cb.1.1.86.a0" on host 128.252.200.3: network_interfaces="lo0 en0" ifconfig_en0="inet 128.252.200.3 netmask 255.255.255.0" static_routes="host1 host2" route_host1="-iface 128.252.200.1 -link en0:3.0.0.ca.3.0.c3.50.0.27.10.0.0.a" route_host2="-iface 128.252.200.2 -link en0:3.0.0.cb.1.1.86.a0" SEE ALSO
en(4), fatm(4), hatm(4), natm(4), patm(4) AUTHORS
Chuck Cranor of Washington University implemented the NATM protocol layer along with the EN ATM driver in 1996 for NetBSD. BSD
August 11, 2003 BSD

Featured Tech Videos

All times are GMT -4. The time now is 06:38 AM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy