Sponsored Content
Full Discussion: ip routing in solaris
Operating Systems Solaris ip routing in solaris Post 302296188 by adol65 on Tuesday 10th of March 2009 02:53:17 PM
Old 03-10-2009
do I need to add a line

route add -net 192.168.1.0 255.255.255.0 192.168.1.111

in order to use qe1 to send stuff to 192.168.1.1

or the system automatically understand this?
 

9 More Discussions You Might Find Interesting

1. IP Networking

routing problem in solaris

hi, below is the situation: my server is in 128.10.200.xxx network. i have a solaris computer running in a subnet. this computer got 2 nic card. 1 is 172.18.198.xxx , another 1 is 10.100.xxx.11 there is a machine stick with this computer, ip is 10.100.xxx.12 so, 10.100.xxx.11 and... (3 Replies)
Discussion started by: kyhah
3 Replies

2. Solaris

Basic Solaris static routing

Hi All, :(:confused: I have scoured the web and can't find this anywhere. What I am trying to do is set up a static route through an available gateway on a server, and then test connectivity through TELNET. I have done this on AIX (I already had this procedure). On AIX I would use SMIT. ... (7 Replies)
Discussion started by: jeffpas
7 Replies

3. Solaris

Solaris zone routing table

Does anyone know how to delete a an ip off the routing table ? i tried route delete 10.0.0.0 and gateway but it still comes back. i have 2 zones sharing one interface. help... (4 Replies)
Discussion started by: 23patrick
4 Replies

4. IP Networking

solaris 8 networking routing

hi all, how do i make sure that the new routing should take effect on the os memory right away? what should i run after i add all the new "route add ....". I have an example below: bash-2.03# netstat -rn Routing Table: IPv4 Destination Gateway Flags Ref Use Interface... (1 Reply)
Discussion started by: itik
1 Replies

5. Solaris

Routing problem of Solaris

Hi, I got problem of Sun Solaris 8 routing. IP of SunA is 10.16.64.164, and have routing table: 10.16.64.0 10.16.64.164 U 1 19236 bge1 10.6.0.0 10.6.0.3 U 1 16534 bge0 224.0.0.0 10.6.0.3 U 1 ... (4 Replies)
Discussion started by: milo
4 Replies

6. IP Networking

solaris routing between two networks

ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2 inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255 ether 0:14:4f:55:82:9 ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3 inet 10.231.11.232 netmask... (1 Reply)
Discussion started by: busyboy
1 Replies

7. Solaris

solaris routing between two networks

ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2 inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255 ether 0:14:4f:55:82:9 ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3 inet 10.231.11.232 netmask... (3 Replies)
Discussion started by: busyboy
3 Replies

8. UNIX for Advanced & Expert Users

Solaris 10 routing table issues

Hello Hope someone can help with this problem. We are running Solaris 10 with a current kernel patch of 142900-09. We appear to be getting a serious issue with the routing table as shown below: Output from netstat -rnv Destination ....Mask ............Gateway ........Device... (2 Replies)
Discussion started by: gregsih
2 Replies

9. Solaris

Solaris Routing

Hello All, Problem is that redundancy doesn't work, probably a routing issue I need to get sorted out When 172.29.11.x net is down, neither node3 nor node4 is trying 172.29.12.x network,The problem lies in network 172.29.13.x if 172.29.11.x network is down, node3/node4 should route to... (6 Replies)
Discussion started by: nadeemahmed
6 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 04:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy