Sponsored Content
Full Discussion: basic networking
Special Forums IP Networking basic networking Post 17427 by satops on Thursday 14th of March 2002 10:42:22 PM
Old 03-14-2002
Thanks for your help. I'm still having some problems. I set up my linux computer as follows:
ip: 192.168.0.1
network: 192.168.0.0
mask: 255.255.255.0
broadcast:192.168.0.255
gateway: 192.168.0.254

I also bought a crossover cat 5 cable and a linux compatible modem. When I try to ftp or telnet to 192.168.0.1 from my windows computer, everything times out. Am I missing something?

Also, I installed the new modem and it works (dials and connects), but netscape won't open any websites.
Please help.

Smilie
 

8 More Discussions You Might Find Interesting

1. Slackware

Basic networking questions.

Hey, I'm new to Linux. I have a few questions about it. I run Slackware. After the installation the Linux installation had problems with my old hardware (network card, sound card) so I removed them and Linux would start. But now, I can't seem to use the network card in Linux because it's not... (3 Replies)
Discussion started by: RellioN
3 Replies

2. UNIX for Dummies Questions & Answers

Basic networking setup in unix

I have a SunOS 5.8 box and have always downloaded & applied patches via my PC, but I want to be able to go out to sunsolve directly from the console ... however, I guess it doesn't know the IP of our domain's DNS server or something. Where are these setting held on a Sun box??? (1 Reply)
Discussion started by: FredSmith
1 Replies

3. UNIX for Advanced & Expert Users

how ..........networking

hi everyone this is dipendra, i am interested in networking,i know simple socket programming . and now i am wonder to get in to audio socket. i have no clue how to build audio socket.so i am looking if u can provide me a link regarding the audio socket building tutorials. (1 Reply)
Discussion started by: dipendra_regmi
1 Replies

4. IP Networking

C networking

Can anybody help me regarding networking using c language i know how to capture the packets and to verify it`s protocol destination and source ip etc. Can anybody help me to direct a packet coming to an ip to some other ip of my choice ........ Hope reply ... (0 Replies)
Discussion started by: Sannair
0 Replies

5. IP Networking

Networking

Hi, I have a question on networking. I will try to ask with an example... Suppose i am googling something, as in searching something in the google page. In this case what I basically want to know is, does the client do a connect evrytime to the server whenever a search is done in google,... (1 Reply)
Discussion started by: naan
1 Replies

6. IP Networking

Basic networking please help

I am running Ubuntu Desktop and Ubuntu Server editions on two separate VMs. For the desktop I have set network adapters: Adapter 1: internal network called intnet Adapter 2: NAT Server: Adapter 1: internal network called intnet Now I'm suppose to set ip addresses which I'm pretty sure... (5 Replies)
Discussion started by: shadowcat
5 Replies

7. IP Networking

Basic networking question

Hii, Today morning I attended an interview, they had showed me the attached image and had few questions about that. The image shows a network with 4 nodes viz.. A B C & D and two switches(layer2) and a router(layer3). Just wanted to know can node A and node D would be on same network e.g... (4 Replies)
Discussion started by: zing_foru
4 Replies

8. IP Networking

Networking

hi From mt windows machine I can ping a LINUX machine but there is no arp entry for the same LINUX on my windows. How is it possible and what can I do to add the arp entry as I need it. thanks (1 Reply)
Discussion started by: leghorn
1 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
All times are GMT -4. The time now is 06:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy