07-10-2002
if you are using a linksys router with dhcp, all you need to do is for the computer that you want to have a static ip, just set that computers ip to any value like this, 192.168.1.2 - 99
10 More Discussions You Might Find Interesting
1. HP-UX
***Newbie alert***
What's the easiest way to accomplish this? An admin left our company and I have taken over his HP Workstation and moved it to a different location that is on a different IP segment.
I have performed a number of google searches but the steps I have followed haven't worked.
... (1 Reply)
Discussion started by: Steelysteel
1 Replies
2. IP Networking
I have a USB Wireless Adapter using the rum0 driver. All I want to do is set a perminent static IP for the onboard wired interface elxl0. I can plumb the wired interface up fine on the fly, but when I try to save the static IP over a reboot, I lose the IP address assigned to rum0 from my wireless... (1 Reply)
Discussion started by: ts97783
1 Replies
3. IP Networking
I am trying to write a set of scripts for my Ubuntu 810 Server to allow a user to change from DHCP to a user-supplied Static IP, Subnet, Gateway and DNS Servers.
So far I have the following, where $USERCHOICE is a user-entered value in each case:
ifconfig eth0 down && ifconfig eth0 $USERCHOICE... (1 Reply)
Discussion started by: cleanden
1 Replies
4. Solaris
Hello friend, I am new in UNIX, but I want to learn a lot
Well I have a problem to try to configure my PC with a static IP Address
(IP 192.168.1.39, Mask 255.255.255.0, gateway 192.168.1.1)
(DNS 200.48.225.130 and 200.48.225.146).
where are the file that I must be change?
The SO is Sun Solaris... (15 Replies)
Discussion started by: andresguillen
15 Replies
5. Red Hat
Hi,
I am using RHEL 5.1 and i would like to know,
how to find the whether my system is using DHCP or STATIC IP
with out looking at /etc/sysconfig/network-scripts/ifconfig-eth0 configuration file.
Regards,
Venkat (3 Replies)
Discussion started by: venkat55
3 Replies
6. UNIX for Dummies Questions & Answers
Hey guys ,
YEs this is probably silly for most but i am new to this forum and solaris . i am curious to know if the ip address we have for our solaris server is static or dhcp . how can i tell ? will ifconfig -a tell me this ? or other commands?
Thanks in advance (1 Reply)
Discussion started by: xdrivex
1 Replies
7. Red Hat
Hi All,
Could you please explain the purpose of assigning the static IP by using the DHCP Concept. Like by using the clients MAC address we assign the static IP Address. Waiting for your reply. Thanks in Advance. (6 Replies)
Discussion started by: Sharath Kumar
6 Replies
8. HP-UX
Hi,
I can find the IP details whether it is Static or dynamic in Linux machine from the location /etc/sysconfig/network-scripts/ifconfig-eth0 configuration file.
Can someone suggest a location to find the same in HP UX machines?
-Vivek (2 Replies)
Discussion started by: vkk
2 Replies
9. IP Networking
I'm trying to figure out what circumstances would cause an Open Solaris 11.2 host to switch itself from a static to a DHCP ip address upon reboot. This has only happened once but is a cause for some concern as this machine will be part of a web server pool.
Nothing has changed on the LAN that... (2 Replies)
Discussion started by: SmokeyJoe
2 Replies
10. Solaris
We have 2 solaris 10 t5240 servers with static IP addresses on nxge0 I/F which were rebooted a few days back with a known good config that has been in place for years (for /etc/hosts, /etc/hostname.nxge0, /etc/netmasks, etc)
They are not using dhcp.
About the same time today, both of their... (7 Replies)
Discussion started by: hdatontodo
7 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