LAN traffic leaking on to WAN


 
Thread Tools Search this Thread
Special Forums IP Networking LAN traffic leaking on to WAN
# 1  
Old 12-13-2011
LAN traffic leaking on to WAN

Network map:

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.
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Red Hat

Memory leaking

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)
Discussion started by: murali969
2 Replies

2. Red Hat

Wan on eth1 and Lan on eth0

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)
Discussion started by: golpemortal
0 Replies

3. IP Networking

Routing traffic problem between 3G and Office Lan Network

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)
Discussion started by: jao_madn
0 Replies

4. IP Networking

Local Lan, no-ip directed DNS forward, surf within lan

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)
Discussion started by: lawstudent
3 Replies

5. Web Development

Cannot access Apache web server from Wan side, only Lan side.

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)
Discussion started by: davidmanvell
1 Replies

6. UNIX for Dummies Questions & Answers

LAN traffic rerouting to web server

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)
Discussion started by: J-Fal
3 Replies

7. Solaris

How to configure private LAN and coporate LAN on the same machine-Solaris10

Hi , I am trying to configure a private LAN and corporate LAN on the same machien on Solaris 10. How can I achieve this? Thanks (1 Reply)
Discussion started by: deedee
1 Replies

8. UNIX for Dummies Questions & Answers

Can someone please give me information about WAN and LAN

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)
Discussion started by: TRUEST
3 Replies
Login or Register to Ask a Question
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