Sponsored Content
Full Discussion: route after reboot
Operating Systems Solaris route after reboot Post 302263731 by upengan78 on Tuesday 2nd of December 2008 11:12:45 AM
Old 12-02-2008
route after reboot

Hello,

I just added a route in solaris 10 system for host to use gateway.

Quote:
route add -host 192.168.100.70 192.168.100.5
I see that new route in the netstat command
Quote:
192.168.100.70 192.168.100.5 UGH 1 2
Will this stay after reboot or I have to make any provision for this? Please let me know

Thanks
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

no route to host

I not able to ping outside the internet. i am able to ping my 192. ip address. when i try to ping a 68. ip address i get no route to host. what should i do to correct this issue. I have sco openserver 5.05 (6 Replies)
Discussion started by: scoman2
6 Replies

2. IP Networking

trace route ip

hi everybody , i have a solaris 5.6 box and i want to trace the route on an ip i treid traceroute but soalris 5.6 does not support it ... is there a command that can be used equivelent to traceroute ? thanks for your help (2 Replies)
Discussion started by: ppass
2 Replies

3. UNIX for Dummies Questions & Answers

Disappearing route

I have a route that disappears when the server is rebooted. to get the route back I do: route add 65.x.x.x 10.0.x.x I go to cd /etc/inet vi config and the route is in place Anybody might know what is happening? (4 Replies)
Discussion started by: jrmontg
4 Replies

4. Solaris

SOLARIS does not route

hi, i installed solaris 9 on an SPARC server with two network interfaces. behind each interface is a small lan. i can reach every computer in every lan using one of the other interface when i am logged in the solaris. but if a computer from one lan has to connect to a computer on the other lan,... (4 Replies)
Discussion started by: bong02
4 Replies

5. Solaris

different between soft reboot and hard reboot

Hi Guru's Can any want here could explain to me the different between soft reboot and hard reboot . Best Regards Seelan (3 Replies)
Discussion started by: seelan3
3 Replies

6. Solaris

Adding new Route

Hi, I am trying to add route command in SunOS machine but it is not successful : route add -host 10.31.251.47 -gateway 10.31.251.0 -interface ce0 this command fails with an error "lo0:1: bad value" I want to add a route to 10.31.251.47 that picks 10.31.251.0 as the gateway via the... (1 Reply)
Discussion started by: jaygamini
1 Replies

7. UNIX for Dummies Questions & Answers

Static Route

Hi, Request you to please tell me the command or the process to add the static route in redhat linux. Thanks in Advance. Regards Arun (2 Replies)
Discussion started by: Arun.Kakarla
2 Replies

8. IP Networking

Route to nowhere?

Hi, HP-UX 11iV2, but it's probably universal (tcp/ip) I have a production and a test server. The test server gets the application updated nightly from the production server software. The application accesses a set of process servers on a separate subnet (192.163.22.30,31,32), but reachable... (1 Reply)
Discussion started by: monroedoug
1 Replies

9. Solaris

Delete route so it does not persist after reboot

Solaris 10 I am trying to delete a route using the command: route -p delete 192.0.0.0 192.1.3.254 The route gets delete but for some reason the route pops back up in the routing table after reboot. I also deleted the /etc/inet/static_routes file and the route still persists after reboot.... (6 Replies)
Discussion started by: jastanle84
6 Replies

10. IP Networking

Route get output

I'm having some trouble understanding the output of the route command. Specifically, the "route to" and "destination" fields. I'm guessing "route to: <address>" means when the queried host receives packets, it sends them to <address> by default, and "destination: <address>" means <address> is the... (2 Replies)
Discussion started by: Ultrix
2 Replies
GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME
gre -- encapsulating network device SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file: device gre Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_gre_load="YES" DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop. gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands. This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco routers. gre also supports Cisco WCCP protocol, both version 1 and version 2. The gre interfaces support a number of additional parameters to the ifconfig(8): grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option. enable_csum Enables checksum calculation for outgoing packets. enable_seq Enables use of sequence number field in the GRE header for outgoing packets. EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.* / / +------ the Internet ------+ Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal address 192.168.2.1, the following commands will configure the tunnel: On router A: ifconfig greN create ifconfig greN inet 192.168.1.1 192.168.2.1 ifconfig greN inet tunnel A B route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1 On router B: ifconfig greN create ifconfig greN inet 192.168.2.1 192.168.1.1 ifconfig greN inet tunnel B A route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1 NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8). For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop. The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero. SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8) A description of GRE encapsulation can be found in RFC 2784 and RFC 2890. AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org> Heiko W.Rupp <hwr@pilhuhn.de> BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as if they would belong to this interface. The sequence number field also used only for outgoing packets. BSD
November 7, 2014 BSD
All times are GMT -4. The time now is 02:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy