08-29-2003
setting a route in Solaris
I am having problems getting this to work, though it seems like it would be simple. I have a host with 2 interfaces, hme0 (192.168.0.132) for the primary interface, and hme1 (192.168.0.16) for backups. I want it to talk to the backup host, which is 192.168.0.21, across the hme1 interface.
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello Dear Friends, I'm here again
I need to know where is the permanent file for gateway configuration.
I did the following command
route add -net 0.0.0.0 5.0.0.3 ( My Gateway), but when i restart my computer i have to do it again.
What the file can i set the permanent configuration for my... (1 Reply)
Discussion started by: themask
1 Replies
2. IP Networking
WE are running Unix - Solaris 2.6, we create a subnet. In the windows enviroment we are able to add a static route by using
route add -p 172.16.10.0 mask 255.255.255.0 172.16.17.224, but when we add the route in Solaris as
route add -net 172.16.10.0 255.255.255.0 172.16.17.224, we receive an... (5 Replies)
Discussion started by: cassy
5 Replies
3. Solaris
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
4. Solaris
I was told this worked on an HP system (same network as the sun server I am trying to set this up on)> but I get "netmask: bad value"2when I try it on the Sun:
route add net 199.42.23.192 netmask 255.255.255.192 204.104.63.30 1
I've tried many different iterations (leaving out netmask, only... (2 Replies)
Discussion started by: nhmeanie
2 Replies
5. Solaris
Hi,
Any one can help me in this below mentioned issue I am facing in my solaris server?
here the scenario goes....
i have multiple segments in my LAN like remote csr, database, production etc. and all the segments are configured in Windows/CISCo network.
from my all system in remote... (1 Reply)
Discussion started by: Praan
1 Replies
6. Solaris
Hi,
I am new to solaris 10. What is the procedure the os takes if a default route is not configured? I am using a multihomed server with 4 interfaces. It looked strange to me this morning, because i had not defined a default route it defaulted to making one up, with the ip address of another... (9 Replies)
Discussion started by: borderblaster
9 Replies
7. Solaris
Hi there,
I'm trying to configure an additional network interface on Solaris 8 (eri0). The interface has been activated, but all the frames are still routed to the current default interface (ce0) I've tried following command (with various syntaxes...) unsuccessfully so far:
# route add... (2 Replies)
Discussion started by: sreiniche
2 Replies
8. Solaris
Hi,
Every time when i boot my system i have to manually issue the following commands.
ifconfig elxl0 plumb 192.168.200.129 netmask 255.255.255.0 up
route add default 192.168.200.1
I need some help so that it should be configured permanently and i wouldn't have to manually issue... (2 Replies)
Discussion started by: malikshahid85
2 Replies
9. Solaris
I need to add a new route on solaris10 machine.
I want that all traffic on the 23 port (telnet) use 192.168.200.1 gateway.
How I do ?
Thank you in advance. (1 Reply)
Discussion started by: arfry
1 Replies
10. Solaris
Hi Solaris Experts,
I am trying to add a routing table entry on our 5.1 Generic_144488-12 sun4v sparc Solaris 10 SUNW,SPARC-Enterprise-T5220 so that it is possible to ping 10.56.9.34 node
# netstat -rnv
IRE Table: IPv4
Destination Mask Gateway Device Mxfrg Rtt Ref
Flg Out In/Fwd ... (2 Replies)
Discussion started by: gjackson123
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