WAN external interface 192.0.0.0 network
|
WAN internal interface 192.0.3.0 network
|
192.0.3.0 LAN
|
wireless router 192.0.3.1
|
DSL modem 192.0.3.2
The problem I am having is that some traffic from the 192.0.3.0 LAN seems to be "leaking" onto the 192.0.0.0 WAN. I noticed this when I installed a NAS on the network. I mapped a drive on a pc to a NAS share. When the backup program starts running, the frame WAN (192.0.0.0) starts dropping packets and the ping times go ridiculous high. When I stop the backup, the WAN traffic and ping times normalize again...
I have a static route in the DSL modem that points 192.0.3.0 to 192.0.0.0 because I need SOME traffic to go over the WAN (a windows shared printer). The rest of the time the frame WAN is only used for some serial printers that our Unix server talks to over the WAN (192.0.0.0).
I have a VPN in place now, so I do not need the 192.0.3.0 traffic to go over the WAN at all now. However, when I remove the static route from the DSL modem my serial printers stop receiving jobs from our Unix server on the other side of the WAN??? Why do my serial printers need the 192.0.3.0 network to talk? Aren't they separate from the LAN? They don't even have network cards for christ sake.
Hi All
Would someone help me to find the detailed report on memory leak.
any commands to get detailed report for OS level and applications
As we are using REDHAT LINUX 5.9
Thanks
Murali Muppa (2 Replies)
I have a local network on dev eth0
Server has static IP of 10.0.0.1
Gateway is 10.0.0.1
and Dns is 10.0.0.1
I am using this network for imaging 500 plus computer...
Now, Issue that I am having is that I need to update packages and I dont want to change the configuration on eth0 because I... (0 Replies)
Hi,
I would like to ask some networking solution regarding my work LAN and 3G usb network problem. I want to route my internet traffic to the 3G network and sometimes connect to some of my work network for ssh to configure some workstation or print something. Currently my problem is i can't... (0 Replies)
Hi,
We have a website running on a local centos 5.4 surfer, static IP.
The domain.com uses no-ip.com to take care of the DNS, it forwards all to my server.
My router receives the port 80 call, routes it to my server and the world can see domain.com perfectly fine.
However, we cannot see... (3 Replies)
I have installed WAMPSERVER 2.0 on my windows vista x64 system but still am having issues with getting the webserver to be seen outside my local network. It is working fine within my local network.
Been through several setup tutorials so far, no dice still.
For testing purposes I have... (1 Reply)
Hello. I am not sure where to post this and would appreciate any moderator help in moving this to the area where it is most applicable. Thank you.
I've posted these questions in a couple different forums, but have not received any answers about what I am doing wrong. I would appreciate any... (3 Replies)
I just need to know the important concepts. I tried searching on the internet for information about this but got bombarded with too many un-neccessary details I find confusing and helpless.
I just need to know WAN and LAN concerning how to monitor them and fix or (troubleshoot) basic problems (3 Replies)
CARP(4) BSD Kernel Interfaces Manual CARP(4)NAME
carp -- Common Address Redundancy Protocol
SYNOPSIS
pseudo-device carp [count]
DESCRIPTION
The carp interface is a pseudo-device which implements and controls the CARP protocol. carp allows multiple hosts on the same local network
to share a set of IP addresses. Its primary purpose is to ensure that these addresses are always available, but in some configurations carp
can also provide load balancing functionality.
A carp interface can be created at runtime using the ifconfig carpN create command.
To use carp, the administrator needs to configure at minimum a common virtual host ID and virtual host IP address on each machine which is to
take part in the virtual group. Additional parameters can also be set on a per-interface basis: advbase and advskew, which are used to con-
trol how frequently the host sends advertisements when it is the master for a virtual host, and pass which is used to authenticate carp
advertisements. Finally carpdev is used to specify which interface the carp device attaches to. If unspecified, the kernel attempts to set
carpdev by looking for another interface with the same subnet. These configurations can be done using ifconfig(8), or through the SIOCSVH
ioctl.
Additionally, there are a number of global parameters which can be set using sysctl(8):
net.inet.carp.allow Accept incoming carp packets. Enabled by default.
net.inet.carp.preempt Allow virtual hosts to preempt each other. It is also used to failover carp interfaces as a group. When the
option is enabled and one of the carp enabled physical interfaces goes down, advskew is changed to 240 on all
carp interfaces. See also the first example. Disabled by default.
net.inet.carp.log Log bad carp packets. Disabled by default.
net.inet.carp.arpbalance Balance local traffic using ARP. Disabled by default.
EXAMPLES
For firewalls and routers with multiple interfaces, it is desirable to failover all of the carp interfaces together, when one of the physical
interfaces goes down. This is achieved by the preempt option. Enable it on both host A and B:
# sysctl -w net.inet.carp.preempt=1
Assume that host A is the preferred master and 192.168.1.x/24 is configured on one physical interface and 192.168.2.y/24 on another. This is
the setup for host A:
# ifconfig carp0 create
# ifconfig carp0 vhid 1 pass mekmitasdigoat 192.168.1.1
netmask 255.255.255.0
# ifconfig carp1 create
# ifconfig carp1 vhid 2 pass mekmitasdigoat 192.168.2.1/24
netmask 255.255.255.0
The setup for host B is identical, but it has a higher advskew:
# ifconfig carp0 create
# ifconfig carp0 vhid 1 advskew 100 pass mekmitasdigoat
192.168.1.1 netmask 255.255.255.0
# ifconfig carp1 create
# ifconfig carp1 vhid 2 advskew 100 pass mekmitasdigoat
192.168.2.1 netmask 255.255.255.0
Because of the preempt option, when one of the physical interfaces of host A fails, advskew is adjusted to 240 on all its carp interfaces.
This will cause host B to preempt on both interfaces instead of just the failed one.
In order to set up an ARP balanced virtual host, it is necessary to configure one virtual host for each physical host which would respond to
ARP requests and thus handle the traffic. In the following example, two virtual hosts are configured on two hosts to provide balancing and
failover for the IP address 192.168.1.10.
First the carp interfaces on Host A are configured. The advskew of 100 on the second virtual host means that its advertisements will be sent
out slightly less frequently.
# ifconfig carp0 create
# ifconfig carp0 vhid 1 pass mekmitasdigoat 192.168.1.10
netmask 255.255.255.0
# ifconfig carp1 create
# ifconfig carp1 vhid 2 advskew 100 pass mekmitasdigoat
192.168.1.10 netmask 255.255.255.0
The configuration for host B is identical, except the skew is on virtual host 1 rather than virtual host 2.
# ifconfig carp0 create
# ifconfig carp0 vhid 1 advskew 100 pass mekmitasdigoat
192.168.1.10 netmask 255.255.255.0
# ifconfig carp1 create
# ifconfig carp1 vhid 2 pass mekmitasdigoat 192.168.1.10
netmask 255.255.255.0
Finally, the ARP balancing feature must be enabled on both hosts:
# sysctl -w net.inet.carp.arpbalance=1
When the hosts receive an ARP request for 192.168.1.10, the source IP address of the request is used to compute which virtual host should
answer the request. The host which is master of the selected virtual host will reply to the request, the other(s) will ignore it.
This way, locally connected systems will receive different ARP replies and subsequent IP traffic will be balanced among the hosts. If one of
the hosts fails, the other will take over the virtual MAC address, and begin answering ARP requests on its behalf.
Note: ARP balancing only works on the local network segment. It cannot balance traffic that crosses a router, because the router itself will
always be balanced to the same virtual host.
SEE ALSO netstat(1), sysctl(3), arp(4), arp(8), ifconfig(8), sysctl(8)HISTORY
The carp device first appeared in OpenBSD 3.5.
BSD October 16, 2003 BSD