09-02-2003
Normally I've seen it put on a different subnet (so as to insure it goes across the correct interface/subnet) but setting a host route may help:
/usr/sbin/route add -host 192.168.0.21 192.168.0.16 1
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
LEARN ABOUT FREEBSD
nos-tun
NOS-TUN(8) BSD System Manager's Manual NOS-TUN(8)
NAME
nos-tun -- implement ``nos'' or ``ka9q'' style IP over IP tunnel
SYNOPSIS
nos-tun -t tunnel -s source -d destination -p protocol_number [source] target
DESCRIPTION
The nos-tun utility is used to establish an nos style tunnel, (also known as ka9q or IP-IP tunnel) using a tun(4) kernel interface.
Tunnel is the name of the tunnel device /dev/tun0 for example.
Source and destination are the addresses used on the tunnel device. If you configure the tunnel against a cisco router, use a netmask of
``255.255.255.252'' on the cisco. This is because the tunnel is a point-to-point interface in the FreeBSD end, a concept cisco does not
really implement.
Protocol number sets tunnel mode. Original KA9Q NOS uses 94 but many people use 4 on the worldwide backbone of ampr.org.
Target is the address of the remote tunnel device, this must match the source address set on the remote end.
EXAMPLES
This end, a FreeBSD box on address 192.168.59.34:
nos-tun -t /dev/tun0 -s 192.168.61.1 -d 192.168.61.2 192.168.56.45
Remote cisco on address 192.168.56.45:
interface tunnel 0
ip address 192.168.61.2 255.255.255.252
tunnel mode nos
tunnel destination 192.168.59.34
tunnel source 192.168.56.45
AUTHORS
Nickolay N. Dudorov <nnd@itfs.nsk.su> wrote the program, Poul-Henning Kamp <phk@FreeBSD.org> wrote the man-page. Isao SEKI
<iseki@gongon.com> added a new flag, IP protocol number.
BUGS
We do not allow for setting our source address for multihomed machines.
BSD
April 11, 1998 BSD