An IP address is how you talk to another computer over an IP network. Each network card has its own IP. You try connecting to 10.0.2.15, and IP protocol will find that computer and talk to it if it's there.
It must be unique on the network -- you shouldn't have two 10.0.2.15's plugged into the same local network, they'll conflict.
An IP address, combined with its netmask, netmask are sort of a combined house and street address. The netmask defines which part is local.
Meaning, 192.168.56.102 can directly talk to any other network card with an IP address of 192.168.56.anything-else. If it were 192.168.57, it would have to forward the message along to a gateway and hope it knows where it belongs.
So the IP address is a unique ID for each computer, and the subnet mask defines which block of other IPs it can talk to.
Hi !
Does anyone know how can i get information about my network interface ... if it works in half or full duplex mode !!
Thx in adivance !
Witt (4 Replies)
Hi every body,
I have a Fiber Channel interface (fcs2) in AIX 5.2. This interface was fine & up but for some reason I could not return this interface UP again after I set it DOWN.
When I tried to set this interface UP I encountered the following error:
Method error... (7 Replies)
Hi all,
Here im facing problem with NIC Interface with my X86 Version of Solaris Express, even after loading module for that Interface. So please check this below mentioned log for your use and get back to me ASAP.
- - - -- --... (0 Replies)
Hello,
I have just installed Solaris 9 x86 in a VMWare and the 1st problem I have is to enable the networking. I can only see the loopback interface and nothing else.
- I dont have any /etc/hostnames.xxx
- ifconfig -a shows only the loopback
- kstat -c net shows only the loopback ...
Any... (11 Replies)
Hi
i have replace a NIC card on solaris 10 when i give the following command
ifconfig -a
it just show the lo0 (only loop back with inet 127.0.0.1)
when i give the following command to config the interface,
ifconfig elxl0 plumb
ifconfig: plumb: elxl0: no such interface
please help... (11 Replies)
i need to configure a zone to use different interface (bge2) than global and have connected to completely different network switch & to use its own defaultrouter and hosts file .. is it possible ..if so ..how ?
Thanks (9 Replies)
Hi,
I'm a italian student. For my thesis I develop a gateway with protocol 6lowpan.
For that I must access to network interface to develope my personal stack based on standard 802.15.4.
Can you help me? I need an explanation for that. (0 Replies)
Hello,
Please, how can i create a network interface with a routable IP address on linux (ubuntu) ?
AND
How can i desactivate an interface?
Thank you so much for help. (1 Reply)
I've one Netra 240
After changing main board and system configuration card reader, Network is not accessible any more, Network interfaces are always UP and Running even when there is no cable connected to Network interfaces.
I tried to restart and plumb/unplumb with no luck.
ifconfig -a... (7 Replies)
I have a RHEL 5 system with a bonded interface configure using only one network port (eth0). So I have config file for ifcfg-bond0 and ifcfg-eth. I'd like to configure eth5 to be the second SLAVE in the bond. My question is, after I modify ifcfg-eth5, can I add eth5 to the bond0 interface without... (1 Reply)
Discussion started by: westmoreland
1 Replies
LEARN ABOUT FREEBSD
if_gre
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