12-22-2007
I pretty sure tha rl0(External interface) because i can connect to internet through this interface.
rl1(Internal interface) to internal LAN. My rl1 is never configure and doesn't have any address. The others have address such as rl0, ral0 and tun0.
Route show :
Destination Gateway Flags Refs Use Mtu Interface
default 219.93.218.177 UGS 2 2083 - tun0
localhost localhost UH 0 2 33224 lo0
192.168.124 link#1 UC 1 0 - rl0
192.168.1.1 Hardwrae add UHLc 0 18 - rl0
192.168.2/24 link#3 UC 1 0 - ral0
192.168.2.3 Hardware add UH 1 0 1492 tun0
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Please help. I have downloaded the openbsd 2.9 snapshot from ftp.openbsd.org. the following files were downloaded from the snapshot dir. ( the whole dir. was downloaded ) base29,bsd,bsd.rd,cdrom29.fs,cksum,comp29,etc29,all three floppy images,game29,index,install.ata,install.chs... (11 Replies)
Discussion started by: Blunt_Killer
11 Replies
2. BSD
hi
I have two hhd's. One is primary disk which holds the OpenBSD system and the other is my download disk (disk2).
I formatted disk2 in "ffs" type. And created a "disklabel", wd1a.
The disklabel program says "No change made", but I can see the changes by "p" command.
I cannot mount my disk2!... (1 Reply)
Discussion started by: fnoyan
1 Replies
3. BSD
I have the DNS files set up on my OpenBSD 4.0 amd64 system however when I run named, I get the following error in my logs:
Sep 23 10:43:03 grunty named: starting BIND 9.3.2-P1
Sep 23 10:43:03 grunty named: /etc/named.conf:25: change directory to '/var/named' failed: file not found
Sep 23... (2 Replies)
Discussion started by: BOFH
2 Replies
4. BSD
I am an eight year Linux user and after getting into an argument with someone about OpenBSD overiding my theory that OS security is 50% OS and 50% admin skill, I decided to try OpenBSD for myself. I've tried BSDs before and haven't been able to get into them for day to dy use, but I am going to... (7 Replies)
Discussion started by: deckard
7 Replies
5. BSD
hello ,
I wondered if anyone could assist me in writing a simple packet filter firewall on my OpenBSD v4.5.
All I intend doing is to have two firewalling machine on a separate network :
192.168.1.1
ext_if = xl0 (dhcp) // Internet interface
int_if=xl1 // Internatl interface
... (0 Replies)
Discussion started by: mattjam
0 Replies
6. BSD
Hi,
I have OPENBSD 4.6 installed as a VM in Virtual Box on my Ubuntu 9.10 machine.
Problem is that the XWindows will not start when I boot my OPENBSD VM.
I am new to OPENBSD. How do I fix this problem? (5 Replies)
Discussion started by: mojoman
5 Replies
7. Linux
Dear Sir
I am a newbie in the world of IP telephony. I have been working with Asterisk PBX (SIP) and Cisco Call Manager (MGCP) but now I am learning on how to work GNUGK for H.323 Gatekeeper.
I am having a problem, configuring static call routing on GNUGK
in the section
... (0 Replies)
Discussion started by: mfondoum
0 Replies
8. IP Networking
I have Ubuntu linux Os with two eth cards. I can easily delete def gatewayg. But I can't add new one.. :confused::confused:
When I run route-n:
alperen@alperen-System-Product-Name:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use... (1 Reply)
Discussion started by: Mhnds
1 Replies
9. IP Networking
hi folks,
i have a horstbox-router with the following configuration.
it has 4 ethernet ports from wich one (wan0) is configured as an external modem via dhcp. at this port/interface(wan0) it is connected with my home network (other switch).
this configuration results in the following... (14 Replies)
Discussion started by: gencaslan
14 Replies
10. UNIX for Beginners Questions & Answers
Dear friends
I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different.... (6 Replies)
Discussion started by: tanpeng
6 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