Sponsored Content
Top Forums UNIX for Beginners Questions & Answers SCO OpenServer 5 Will Not Boot Post 303026616 by jgt on Friday 30th of November 2018 12:19:28 PM
Old 11-30-2018
i don't see an attachment?
you could run:
Code:
route add default 192.168.1.1

although you will have to add it to somewhere in /etc/rc2.d to have it survive a reboot. (where 192.168.1.1 is the gateway address)
SCO OpenServer 5 Will Not Boot-netconfigpng
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Help For SCO OpenServer

I've just installed Unix SCO OpenServer System v in an Intel PC and Everithing ok, except just one thing, in the begining of the installation the wizard asked me about the mouse , i have a generic 3 buttons mouse and i took a logitech and did not work i need to change the mouse configuration, ... (2 Replies)
Discussion started by: jimmyvaldes
2 Replies

2. UNIX for Dummies Questions & Answers

sco openserver 5.5

hello! when i try to make my system dual boot with both win98 & sco open server 5.5 it doesn't work at all.neither win98 take start nor sco open server boots.what should i do ? kindly help me thanks (1 Reply)
Discussion started by: buntty
1 Replies

3. UNIX for Advanced & Expert Users

SCO 5.0.2 openserver

I am doing some work for a customer that is running SCO 5.0.2 openserver and they have lost their cd. Is there anyplace I can download it? I have a replacement being shipped but it will not be here for two days and they are down. Any ideals? (3 Replies)
Discussion started by: SCOoT
3 Replies

4. UNIX for Dummies Questions & Answers

boot failure SCO 5.0.6 OpenServer

hello guys. I just installed SCO 5.0.6 OpenServer it went all the way to the end of the installation and the first boot try it gave me this message. not a directory boot not found cannot open stage 1 boot failure: error loading hd (40)/boot (2 Replies)
Discussion started by: josramon
2 Replies

5. SCO

Ethereal for SCO OpenServer 5.0.7???

Which version of Ethereal can I use for SCO OpenServer 5.0.7??? (0 Replies)
Discussion started by: bean2
0 Replies

6. UNIX for Dummies Questions & Answers

SCO Openserver 6.0

Hi there guys. I just got this new SCO version and i'm having some problem printing from shell, This is what i'm typing at the # sign : lp -dHP /etc/hosts and it prints no problem but when i use any other user at the $ sign it gives me this error. /dev/fd/7: /usr/lib/lp/sysv/7: not found. ... (1 Reply)
Discussion started by: josramon
1 Replies

7. UNIX for Dummies Questions & Answers

SCO Openserver 6.0

Hi guys, I just got this new 6.0 version and i'm trying to setup a remote office to telnet to this server running sco 6.0, in previous version all i have to do is add this file under /etc/rc2.d call S99route and put the gate in that file and that was it, for some reason in 6.0 it does not... (1 Reply)
Discussion started by: josramon
1 Replies

8. SCO

sco openserver 5.0.7

Dear members when i installed dual processor patch in openserver 5.0.7 in hp ML370 G4 server it hangs in sco at G_hd_config. i tried MP4, EFS 5.64,5.70A but not solved the problem.. (0 Replies)
Discussion started by: M_farooqui
0 Replies

9. SCO

sco openserver 5.0.0 boot / root disk

Hi, I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone. I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
Discussion started by: marcpascual
0 Replies

10. SCO

I need SCO Openserver 4.2!!!!

I need SCO Openserver 4.2. Please, give me distributive of that version SCO:eek: (0 Replies)
Discussion started by: caine
0 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 07:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy