10-05-2010
port forward & DYNDNS Inquiry
Hi,
Is there anyone know how to make port forward? And also, how to set up DYNDNS with router?
10 More Discussions You Might Find Interesting
1. UNIX and Linux Applications
hi all
i have some question if any one can help me please
How get root without local ? :(
&
How get root with open port in server use the telnet ? :(
&
How get root with Buffer Overflows ? :(
please help me
thanx to all (2 Replies)
Discussion started by: iis
2 Replies
2. UNIX for Advanced & Expert Users
Hello there,
I have a big problem, and I hope somebody can help me. I try to realize a port forward over three server. Here is a picture...
Client Server1 | Server2
------- ------- | -------
|...... | |...... | | |...... ... (2 Replies)
Discussion started by: Art007
2 Replies
3. Solaris
Hi Gurus
I need to know few things related to HBA port & fcinfo command
I have a server where there are 4 HBA ports cards are their. Out of 4 ports 2 are in use & 2 are not in use when I check it physicall. Now I want to know the command through which I can get information about all above... (6 Replies)
Discussion started by: girish.batra
6 Replies
4. Ubuntu
Hi,
I am new to linux stuff. I want to use linux iptables to configure rule so that all my incoming traffic with protocol "tcp" is forwarded to the "FORWARD CHAIN". The traffic i am dealing with has destination addresss of my machine but i want to block it from coming to input chain and somehow... (0 Replies)
Discussion started by: arsipk
0 Replies
5. UNIX for Advanced & Expert Users
I've been going crazy trying to get this working. Here's the situation: we have a Solaris 10 box that connects an internal network to an external network. We're using ipf/ipnat on it. We've added a couple of new boxes to the internal network (192.168.1.100, .101) and want to be able to get to port... (1 Reply)
Discussion started by: spakov
1 Replies
6. Debian
Hello, the Nat and the forward worked on my debian server up to the reboot of machines.
The following rules*:
/sbin/iptables -t nat -A PREROUTING -p tcp -i eth2 -d xxx.xxx.xxx.xxx --dport 29070 -j DNAT --to-destination 10.0.1.7:29070
/sbin/iptables -A FORWARD -p tcp -i eth2 -o eth0 -d... (0 Replies)
Discussion started by: titoms
0 Replies
7. Red Hat
Hi,
I have a newly built RHEL5 OS that is unable to talk to the DNS server. I am unable to telnet resolv.conf entry over port 53 but apparently this port has been opened.
# telnet 209.212.96.1 53
and.....
# dig www.google.com
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>>... (9 Replies)
Discussion started by: Duffs22
9 Replies
8. AIX
Hello folks,
I have an AIX server that is connected to a storage array via a Brocade switch using 4 ports from either side. The zoning is done such that there are 4 paths visible from the server to the storage.
My work involves frequent disabling or enabling the switch ports that are... (1 Reply)
Discussion started by: nkiran
1 Replies
9. Shell Programming and Scripting
Hi,
I have a file having following content.
<sip:9376507346@97.208.31.7:51088
<sip:9907472291@97.208.31.7:51208
<sip:8103742422@97.208.31.7:51024
<sip:9579892841@97.208.31.7:51080
<sip:9370904222@97.208.31.7:51104
<sip:9327665215@97.208.31.7:51104
<sip:9098364262@97.208.31.7:51024... (2 Replies)
Discussion started by: SunilB2011
2 Replies
10. Red Hat
Hi all,
I can't port forward from WAN to VPN Client. VPN Client Ubuntu 18 192.168.0.16 Port 6000
VPN Gateway for LAN clients Centos 192.168.0.12
Router 192.168.0.1
I can forward to the VPN Client if VPN is not connected if I forward Port 6000 from 192.168.0.1 directly to 192.168.0.16.... (2 Replies)
Discussion started by: stinkefisch
2 Replies
IRDPD(8) System Manager's Manual IRDPD(8)
NAME
irdpd - internet router discovery protocol daemon
SYNOPSIS
irdpd [-bsd] [-U udp-device] [-I ip-device] [-o priority-offset]
DESCRIPTION
Irdpd looks for routers. This should be a simple task, but many routers are hard to find because they do not implement the router discov-
ery protocol. This daemon collects information that routers do send out and makes it available.
At startup irdpd sends out several router solicitation broadcasts. A good router should respond to this with a router advertisement.
If a router advertisement arrives then no more solicitations are sent. The TCP/IP server has filled its routing table with the info from
the advertisement, so it now has at least one router. If the advertisement is sent by a genuine router (the sender is in the table) then
the irdpd daemon goes dormant for the time the advert is valid. Routers send new adverts periodically, keeping the daemon silent.
Otherwise irdpd will listen for RIP (Router Information Protocol) packets. These packets are sent between routers to exchange routing
information. Irdpd uses this information to build a routing table.
Every now and then a router advertisement is sent to the local host to give it router information build from the RIP packets.
Lastly, if a router solicitation arrives and there is no router around that sends advertisements, then irdpd sends an advertisement to the
requestor. Note that this is a direct violation of RFC1256, as no host is supposed to sent those adverts. But alas the world is not
always perfect, and those adverts make booting hosts find routers quickly with this help from their brothers. (Of course, they will lose
the router soon if they don't have an irdpd daemon themselves.)
OPTIONS
-b Broadcast advertisements instead of sending them to the local host only. This may be used to keep (non-Minix) hosts alive on a net
without adverts.
-s Be silent, do not send advertisements to hosts that ask for them.
-d Debug mode, tell where info is coming from and where it is sent. Debugging can also be turned on at runtime by sending signal
SIGUSR1 or turned off with SIGUSR2.
-o priority-offset
Offset used to make the gateway's preferences collected from RIP packets look worse than those found in genuine router adverts. By
default -1024.
SEE ALSO
set_net_default(8), boot(8), inetd(8), nonamed(8), rarpd(8).
BUGS
Under standard Minix this daemon can't listen to two both IRDP and RIP at the same time, so it starts out with IRDP. It switches over to
RIP if it can't find a router, or if it threatens to lose its router. It does not switch back.
Irdpd may help a host that should not be helped, i.e. if it doesn't have an irdpd daemon with RIP collecting trickery. It will make System
Administrators pull out their remaining hair trying to find out why a host can access outside networks for a some time after boot, but goes
blind afterwards.
AUTHOR
Kees J. Bot (kjb@cs.vu.nl)
IRDPD(8)