Sponsored Content
Special Forums IP Networking Lost Connectivity to the Internet Post 302118316 by sysgate on Monday 21st of May 2007 09:50:40 AM
Old 05-21-2007
In *BSD environment the ".ko" extension is a must. In such cases, for better tracing, the "-v" may be used - more verbose, but Aaron solved his issue with re-installing the BSD.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

RedHat Internet Connectivity

I recently installed RedHat9 on my laptop as a guest OS. My host OS is Windows2000 and I am using VMWare to toggle between two OSs. Any time I try to connect to internet from RedHat environment using Mozilla, internet acces does not work. At the office, after connecting my laptop to our... (7 Replies)
Discussion started by: eysheikah
7 Replies

2. UNIX for Dummies Questions & Answers

Internet connectivity via Win-ICS

Hi all, Have two DEC Alpha 3000 systems (I think they're considered legacy servers) that I acquired from my former employer prior to the Voluntary Administrator seizing the assets. They both have the basic SCO V4.0f OS installed and too be honest, I've had little time to even turn them on. ... (2 Replies)
Discussion started by: Cameron
2 Replies

3. Solaris

Network Connectivity lost after reboot

I have 4 V440 servers running Solaris 9. I have their interfaces configured (ce0) and have connectivity to our network. However, after reboot,...the connectivity is lost although the interface shows that its still up after an ifconfig -a. Only after I reconfigure the interface do I restore... (19 Replies)
Discussion started by: StorageGuy
19 Replies

4. Red Hat

problems with internet connectivity

I had a strange problem.Recently, I virtualized my RHEL 5 system by installing Fedora 8 as guest operating system. The installation went fine. But, after installation my internet connection stopped working. Any suggestions?. I was on TataIndicom wireless USB modem. I haven't had any problems with... (3 Replies)
Discussion started by: jaghelp323
3 Replies

5. Solaris

Intermittent internet connectivity

Hello, I am a relative UNIX newbie and we are unable to get out to the internet past the router. I can ping everything within the network but can't get out on a consistent basis. The UNIX DBA was let go recently and I have had to step in and assume his duties. Unfortunately, I am not quite... (1 Reply)
Discussion started by: judo42
1 Replies

6. UNIX and Linux Applications

SQUID proxy : How do I limit internet connectivity to X hrs/day

Hi Everyone! A friend of mine is looking for a way to limit time his kids spent on the internet. I told him he should try out Squid proxy server. He now tries to find a way to limit total time spend on the internet to "X" hours a day, at any time during the day. I remember there are built-in... (3 Replies)
Discussion started by: togr
3 Replies

7. UNIX for Dummies Questions & Answers

Internet connectivity problem

Hello fellow users and enthusists. I am in need of assistance. I have installed Solaris 10 on a Gateway AMD Athlon 64 system. It is set up to dual boot with Windows 7. I am attempting to get internet access through another Windows 7 box, which is sharing its wireless internet connection with... (0 Replies)
Discussion started by: jl2215
0 Replies

8. Solaris

Server M4000 server lost connectivity to storagetek 2540

Hi Guys, I have situation here ... server M4000 server lost connectivity to storagetek 2540 , storagetek 2540 unable to be ping.From DAS URL the storage is undetected. Any idea why this is happening. Please share. Thank you. Raj (1 Reply)
Discussion started by: muralirajah
1 Replies

9. Shell Programming and Scripting

Log of lost internet connections

I am having a big problem with lost internet connections with my DSL. I would like to create a log to be able to show the technician when he comes next week. I would like for it to only log pings that generate 100% packet loss. Thanks.. This script generates all ping attempts including... (4 Replies)
Discussion started by: drew77
4 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 02:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy