Sponsored Content
Full Discussion: Do I need to add a route??
Special Forums IP Networking Do I need to add a route?? Post 76924 by cleks on Friday 1st of July 2005 01:14:16 PM
Old 07-01-2005
In FreeBSD, you can add in /etc/default/rc.conf
 

10 More Discussions You Might Find Interesting

1. AIX

route add

Hello , We have 3 rs/6000 server's running aix on our local network, so each time I try to ping one of these servers we get a "network is down" error , I've been instructed to use to route add command which is ... #route add server.ip router.ip after this the ping command works fine ,... (6 Replies)
Discussion started by: cubicle^dweller
6 Replies

2. HP-UX

Add Route on HP-UX v10.x, help.

Hi, My H-UX box has the GW pointing to 10.10.10.1 and I need add it a new route pointing to 192.168.80.x with the GW 10.10.10.13 I tried with: #route add 192.168.80.2 255.255.255.255 10.10.10.13 but I get: add net 192.168.80.0: gateway 255.255.255.0: Network is unreachable I tried with... (4 Replies)
Discussion started by: efrenba
4 Replies

3. IP Networking

Route add probleme

I have a system that i want to reach via a vpn created vi a fierwall.The fierwall in an other system. The ip i am trying to get to is 172.16.4.48 I need to get to it via the hme1 interface. The vpn gateway has this ip 172.30.50.1 I need to clean up the routing table and make this work; or is it... (5 Replies)
Discussion started by: waterboy
5 Replies

4. Solaris

Route Add

Hi, I am trying to add route command in Solaris 10 machine in the following fashion: route add -host 10.8.112.10 180.144.1.250 -interface lo0:1 this command fails with an error "lo0:1: bad value" I want to add a route to 10.8.112.10 that picks 180.144.1.250 as the gateway via the... (3 Replies)
Discussion started by: sudhir_shet
3 Replies

5. IP Networking

route add

I have built a new linux server, via a iLo connection. and I am trying to connect via my desktop to the server I have just built to the management port eth0 via putty. Please could some one advise how to connect to this server from my desktop. Do i need to create add a route access on the... (0 Replies)
Discussion started by: venhart
0 Replies

6. Solaris

route add : network is unreachable

Hey Guys: I am trying to add a route for assign a network interface to the traffic to/from a specific net, but allways to get the same system message : network is unreacheable root@ColectorDMSCNT # route add net 200.44.46.0/24 161.196.84.196 1 add net 200.44.46.0/24: gateway... (2 Replies)
Discussion started by: aggadtech08
2 Replies

7. Solaris

Add route to solaris10

Hi need to add 2 routes, one on each server. I know the route add comand but I have always been given the parameters to put in. I need a route in each of the 2 following servers to be able to ping and ssh between them. But how do i know which netmask to put in the route add command ? In... (6 Replies)
Discussion started by: vettec3
6 Replies

8. Solaris

Add route to solaris 10

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

9. Solaris

Couldn't add route on Solaris 10

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

10. IP Networking

Add explicit route

Add explicit route to 10.128.255.41/32 , gateway: 10.128.201.254 if not working, please try gateway through management port: 10.128.55.254 Just want to double confirm if this would be the correct command #route add -net 10.128.255.41/32 10.128.201.254 And if didnt work #route add... (1 Reply)
Discussion started by: Thilagarajan
1 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 06:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy