Here's the problem. I got one network with a internett connection (2mbit). In this network there's 5 computers connected together with a hub. The other network is also with 5 computers. I'm just wondering if I could connect these networks together. But the one network should not get access to the... (1 Reply)
Hello,
I've moved to a new network with multiple AIX box's. Most of them are working fine and dandy.
On one box I need to set up a static route to a gateway.. no problem right?
Whenever I add the route it appears in the routing table as UGc and then begins adding new entries to the... (1 Reply)
I have an IP routing issue or I am just to stupid to work it out myself.
I have setup am old PC running SUSE Linux 11.3 as a router, the system has 3 Interfaces connecting 3 networks.
Interface 1 = 10.164.2.161/21
Interface 2 = 192.168.1.210/24
Interface 3 = 30.1.0.11/16
The default... (6 Replies)
Hi Mates,
I have one problem connecting a solaris machine to winxp machine.
Setup:-
Solaris 10 OS Virtual machine - on VMWARE (Ip Address:- 192.168.10.3).
WINXP SP2 is the base os. (Ip Address:- 192.168.10.2).
Bothe machines are connected using a bridge networking VMnet1.
When i ping... (1 Reply)
I have run into a wall troubleshooting a Centos 5 networking issue. Hoping someone can assist.
I've got a box with two vlans trunked over bond0
bond0 Link encap:Ethernet HWaddr 00:22:64:C1:D6:60
inet6 addr: fe80::222:64ff:fec1:d660/64 Scope:Link ... (0 Replies)
System: Dell Desktop w/ 2 SATA drives running Ubuntu 9.10 that uses 2 ethernet cards, 1 for internet connectivity and another to interface the machine with a high voltage power supply which supports ssh and EPICS controls. Second Ethernet card is connected to a NetGear WNR3500 router, the VME... (0 Replies)
Hi,
We have a website running on a local centos 5.4 surfer, static IP.
The domain.com uses no-ip.com to take care of the DNS, it forwards all to my server.
My router receives the port 80 call, routes it to my server and the world can see domain.com perfectly fine.
However, we cannot see... (3 Replies)
Hi,
I would like to ask some networking solution regarding my work LAN and 3G usb network problem. I want to route my internet traffic to the 3G network and sometimes connect to some of my work network for ssh to configure some workstation or print something. Currently my problem is i can't... (0 Replies)
we are not able to ping client server (falcon-ebr.sbms.bsc.com) from netbackup master server (135.179.96.122 tsprd-ebr.edc.single.net)
However from client server we are able to ping the master Server.
Please assist on this (1 Reply)
I recently installed Centos 6 and is my SOHO firewall/router. The small network is layout like such:
|--eth0(WAN)
Centos 6(firewall/router)
|---eth1(LAN)
|
Switch
|
|
LAN(192.168.3.0/27)
|
|
PCs ----Laptops---Printer... (8 Replies)
Discussion started by: metallica1973
8 Replies
LEARN ABOUT FREEBSD
nos-tun
NOS-TUN(8) BSD System Manager's Manual NOS-TUN(8)NAME
nos-tun -- implement ``nos'' or ``ka9q'' style IP over IP tunnel
SYNOPSIS
nos-tun -t tunnel -s source -d destination -p protocol_number [source] target
DESCRIPTION
The nos-tun utility is used to establish an nos style tunnel, (also known as ka9q or IP-IP tunnel) using a tun(4) kernel interface.
Tunnel is the name of the tunnel device /dev/tun0 for example.
Source and destination are the addresses used on the tunnel device. If you configure the tunnel against a cisco router, use a netmask of
``255.255.255.252'' on the cisco. This is because the tunnel is a point-to-point interface in the FreeBSD end, a concept cisco does not
really implement.
Protocol number sets tunnel mode. Original KA9Q NOS uses 94 but many people use 4 on the worldwide backbone of ampr.org.
Target is the address of the remote tunnel device, this must match the source address set on the remote end.
EXAMPLES
This end, a FreeBSD box on address 192.168.59.34:
nos-tun -t /dev/tun0 -s 192.168.61.1 -d 192.168.61.2 192.168.56.45
Remote cisco on address 192.168.56.45:
interface tunnel 0
ip address 192.168.61.2 255.255.255.252
tunnel mode nos
tunnel destination 192.168.59.34
tunnel source 192.168.56.45
AUTHORS
Nickolay N. Dudorov <nnd@itfs.nsk.su> wrote the program, Poul-Henning Kamp <phk@FreeBSD.org> wrote the man-page. Isao SEKI
<iseki@gongon.com> added a new flag, IP protocol number.
BUGS
We do not allow for setting our source address for multihomed machines.
BSD April 11, 1998 BSD