router Linksys


 
Thread Tools Search this Thread
Special Forums IP Networking router Linksys
# 1  
Old 02-02-2007
router Linksys

I have a linksys router BEFSR41. I am trying to connect two network..

one device has to route from one network of IP address 192.168.10.12 to go to a device on separate network with IP address 192.168.25.95.

In the configuration LAN ip address by default it 192.168.1.1
If I define LAN IP to 192.168.10.82 and define WAN 192.168.25.98
then I can route my one network IP to go an talk to other.


I am trying to comfigure router but it doesn't seems to work properly.
New to networking ..

I hope I explained it well.
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

[Solved] Can't get on internet with Linux Static IP address and Linksys Router.

I configured my linux server with Static IP address out of the range of the DHCP linksys router, but cannot get on the internet. When I switch back to "Automatically obtain IP address" ..then I can get on the internet. Can comeone help with this. (2 Replies)
Discussion started by: FrankOscar
2 Replies

2. Cybersecurity

Linksys router question

Hi I have very basic network settings in my home. Cable connected to my Linksys Wireless G router. My wife and I connect to that using our laptop. Yes. I did enable encryption to connect. Also my wireless printer is connected to that. For some reason, last night around 12:30 AM, the... (4 Replies)
Discussion started by: samnyc
4 Replies

3. IP Networking

Linksys RV802 VPN Router

Does anyone know if this router can restrict incoming traffic to specific IP addresses. There does not seem to be any information on Cisco's web site any more. ie Only 209.123.123.123 is allowed access to port 9100, which is redirected to 192.168.1.100 (1 Reply)
Discussion started by: jgt
1 Replies

4. UNIX for Dummies Questions & Answers

Remote Unix printing to my WinXP works with no router. How can I make it work through my router?

I set up remote printing on a clients Unix server to my Windows XP USB printer. My USB printer is connected directly to my PC (no print server and no network input on printer). With my Win XP PC connected to my cable modem (without the router), i can do lp -dhp842c /etc/hosts and it prints. I... (7 Replies)
Discussion started by: jmhohne
7 Replies

5. Shell Programming and Scripting

using wget to submit a form on linksys router

I'm trying to use wget to submit a form. I have tried to dig out what is actually being "posted" and where, using tamperdata (see below). http://ubuntuforums.org/attachment.php?attachmentid=109123&d=1239224127 Here is my wget command: wget --http-user=xyz --http-password=xyz... (1 Reply)
Discussion started by: mike909
1 Replies

6. IP Networking

linksys router and solaris 8

I just sys-unconfigged my ultra sparc which is on my home network where I have 2 PCs attached. When I go to install Solaris 8, it asks various things re: networking. Specifically, when it asks for the IP addy for the DNS server, I input the info, but it barfs back "IP addy info not found". I... (10 Replies)
Discussion started by: nicomen
10 Replies

7. IP Networking

Connecting SGI to Linksys router

I have an SGI running Irix 6.5 and I am trying to connect it to my home network that consists of two Windows PC's (Win 98SE and Win 2000) plus the SGI all connected to a Linksys router which is connected to my DSL modem. My ISP is Verizon DSL (Dynamic IP addressing.) All network lights are... (3 Replies)
Discussion started by: mdbanas
3 Replies

8. Solaris

I can't ping my linksys router from Ultra 10

To begin with, I am a Solaris newbie; however, I am very familiar with Linux. Until I began working with Solaris, I didn't realize how much more difficult networking Solaris is than Linux. Before submitting this question, I have tried to fix this problem myself. After days of research, I still... (3 Replies)
Discussion started by: cstovall
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