06-25-2010
I tried the same commands.
#ifconfig lo0 plumb
#ifconfig lo0 192.168.90.2 netmask 255.255.255.0 up
created a new file /etc/sun1.lo0 and added the above entry in that
the following entry added in /etc/hosts
#192.168.90.2 sun1 loghost
the following entry added in /etc/netmasks
#192.168.90.0 255.255.255.0
after rebooting ip address is persist but netmask is showing 255.0.0.0
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
WEe have installed Intel version of Solaris 8 in a machine .we skipped the network configuration at the begning.we selected unnetworked.Now we need to connect the same machine to a network.
We configured the Card using ifconfig but its taking the ip address itself as the Default G/W.
I need help... (4 Replies)
Discussion started by: premkumar
4 Replies
2. UNIX for Dummies Questions & Answers
Hi. I have installed Solaris 8 and I am trying to configure the network settings. For some reason every time I reboot, my card loses its configuration. I can run ifconfig and the only IP address bound to my card (on either interface) is 127.0.0.1. I can change that to a valid IP address on my... (8 Replies)
Discussion started by: Ask Me
8 Replies
3. HP-UX
Hi,
I have installed a HP-UX B.11.00 U 9000/800 Server in one of the domain. And I'm also able to telnet/ping into this server from systems in the same domain.
But I'm not able to telnet/ping into this server from a different domain.
So, what shoud need to do to achieve this... (6 Replies)
Discussion started by: S.Vishwanath
6 Replies
4. IP Networking
I have solaris 2.8 on an ultra 1 and just configured the following files:
defautrouter
resolv.conf
nsswitch.conf
netmasks
hosts
but when I reboot, my NIC still is not configured. Which file do I need to configure to keep the NIC configured after reboot? (3 Replies)
Discussion started by: DarkLord
3 Replies
5. Solaris
hi again...
i configured my network settings sometiime ago using the sys-unconfig command.the active link was rtls0.
there was some problem with the network so i changed the ISP. now when im trying to reconfigure the system wit sys-unconfig, it tries to configure the network on rtls1 (and shows... (1 Reply)
Discussion started by: strider
1 Replies
6. Solaris
I am seeking help from the gurus in this forum and hope that I can find answers soon. Anyone who provide the answers will be greatly appreciated.
I have a sparc box with Solaris 10 on it. We install Solaris with zone structure. One global zone and two other zone. I installed Oracle DB on global... (6 Replies)
Discussion started by: duke0001
6 Replies
7. SCO
I have a SCO 5.07 Server and I am trying to get it on my network. I have edited the /etc/hosts file and /etc/rc2.d/s99route . I has connectivity on the NIC card but not sure if I am forgetting another file. Thanks! (2 Replies)
Discussion started by: andrewd
2 Replies
8. UNIX for Dummies Questions & Answers
I am using solaris 10, my internet works alright but each time i reboot i keep loosing my connection. I will have to use the
ifconfig iprb0 192.168.1.xx netmask 255.255.255.0 up and
Route add default 192.168.1.xxx command to gain back my internet.
I know there is a better way of addressing... (1 Reply)
Discussion started by: seyiisq
1 Replies
9. Solaris
Hi
I have installed Solaris 5.10 on Intel x86 machine (standalone).
I want to access internet through solaris. How should I configure the network? Is static IP or DHCP advisable? (5 Replies)
Discussion started by: johnl
5 Replies
10. Solaris
Hi, I am new in Solaris 11. I can't even make the NIC work. Here is the issue:
Any help will be greatly appreciated. (6 Replies)
Discussion started by: aixlover
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