[mrtg] Re: SMTP on TCP port

[Peter P. Benac]

Chris,

      Are you attempting to write and SNMP Agent?  As I said before Redhat's
own SNMP agents will bind to port 161 before you startup your software
unless you disable them.  Furthermore you can't use the same functions for
UDP ports that you use for TCP ports.   The latter assumes a "connection"
between devices; whereas, UDP ports are connectionless.  

     You have to use the more primitive recv and send functions for UDP
ports instead of the recvfrom and connect/send functions.

     I assure you even RedHat hasn't messed with the way TCP/IP works at
this level.

Regards,
Pete
----
Peter P. Benac, CCNA
Emacolet Networking Services, Inc
Providing Systems and Network Consulting, Training, Web Hosting Services
Phone: 919-847-1740 or 866-701-2345
Web: http://www.emacolet.com
Need quick reliable Systems or Network Management advice visit
http://www.nmsusers.org

To have principles...
             First have courage.. With principles comes integrity!!!



> -----Original Message-----
> From: Chris Wilson [mailto:chris at sigmer.com]
> Sent: Wednesday, November 26, 2003 11:08
> To: Peter P. Benac
> Cc: mrtg at list.ee.ethz.ch
> Subject: Re: [mrtg] Re: SMTP on TCP port
> 
> 
> Hi,
> 
> Sorry, I think my terminology is incorrect.
> 
> The problem is that, when I start net-snmp, informing it to
> use UDP port 
> 161, I can SNMP walk it locally (on the remote and local ip 
> addresses), 
> but when I try remotely it fails to work.
> 
> Then I repeat the process, telling it to use TCP port 161 it
> works fine, 
> remotely and locally.

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi