Problems connecting Solaris 10 to network via ISP

10 More Discussions You Might Find Interesting

1. Red Hat

Connecting using SSH in WAN network

i have been learning linux from some time for linux plus exam and learned SSH protocol and have practised to connect to remote computer within Lan network and able to sucesssfully connect it . using ssh username@hostname But i wish to ask how do i use same ssh protocol to connect to other ...

2. AIX

problems connecting with exceed (solved)

Hi, We have a user who cannot connect to the aix system anymore with hummingbird exceed. Our unix servers are aix 5.3. She is running windows xp and using hummingbird 12. She used to not have any problem, but now when she tries to use xstart she gets an error 'unable to connect to host using...

3. Shell Programming and Scripting

connecting to network, auto-entering info

Hey guys, I just started college a few days ago. To my dismay, my school has a very frustrating wireless network access system. Every time you want to use the network, you need to open up a browser and get re-directed to a login page. Every access, you need to reenter the same username and...

4. IP Networking

Connecting to DHCP network with Realtek interface

I have a Realtek 8139 interface in one of my machines and it will not connect to the network. /etc/rc.conf contains ifconfig_rl0="DHCP" and "rl0" was obtained from a dmesg. A network interface restart yields the following: # /etc/rc.d/netif restart Stopping network: lo0 rl0 fwe0 plip0. rl0: no...

5. IP Networking

Connecting to an SSN from an internal network

Hi I have an Apache Web server running on a Solaris 8 box that sits on a SSN. I have one desktop that connects to the SSN from the internal network and is recognised directly without using the gateway, all other desktops, laptops from inside the internal network connect to the SSN using the...

6. UNIX for Dummies Questions & Answers

Problems connecting to the Internet

I am trying to connect a Solaris 10 PC to the internet via a Linksys router and a cable modem. I have tried following suggestions in one of the posts here for manual setup but so far no luck. Does the Solaris 10 install for x86 automatically pick up the internet connection? Dave :>)

7. HP-UX

Remotely connecting to HP-UX poses a lot of problems

1)MY HP-UX11iv2 machine is on a specific subnet as in rrr.rr.199.( its a rp3410 blade server).It has 2 hard disks one of them has HP-UX11iv2 and the other hard disk is not being used 2)ip of the hp-ux machine is rrr.rr.199.rrr 3)i need to access this hp-ux machine remotely from a windows machine...

8. HP-UX

Connecting To An External Network Using A logical (PACKAGE) IP Address

Hie everyone, I am currently facing a problem whereby I can not connect to an external network from a package ip address on a HP-UX cluster. Below is the illustration: Primary Server IP Address : n.n.n.202 Secondary Server IP Address : n.n.n.212 Package IP Address : n.n.n.211 ...

9. Programming

tcp server listening, client connecting problems

hello everyone. I tried searching for something related to this, but I figured it was time to ask my own question. I am experiencing these problems using Ubuntu 7.04 I am starting up a TCP listener/server and once connected, will act as a communication/control link with a program on another...

10. Solaris

Connecting Solaris to Airport network

Hi, I've been trying to find out for the past two days how to set my Solaris 10 to join wireless network (Airport base station with ACL and wep or wpa on). Using ethernet is a bit out of question as I don't have an ethernet cable that would reach the other side of the house. Solaris 10...

LEARN ABOUT FREEBSD

gre

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

Solaris