07-31-2002
I think you are able to configure MSN to go through the firewall on Port 80. From the tools menu select Options and go to the Connections tab. Fill in the proxy information and you should be set.
If you need the proxy information open Internet Explorer and from the Tools menu select Internet Options go to the Connections tab and click the LAN Settings button and copy the info under the proxy server section. If you are not running IE there should be a similar process under Netscape/Mozilla/Opera/Whatever...
8 More Discussions You Might Find Interesting
1. SuSE
Right now i'm about two days away from losing all my windows based computers....lol. So i need to know of a few good progs that will beable to communicate with MSN messenger...lol right now i'm still running rh 7 so is there anything that would work with that? (8 Replies)
Discussion started by: byblyk
8 Replies
2. Linux
Would any of you know if there are any Linux (and/or BSD) MSN-clients that make it possible to send messages from shellscripts? When I search sourceforge I get lots of hits, but none of these really advertise this ability.
I would like to have my servers send me a message when certain events... (0 Replies)
Discussion started by: indo1144
0 Replies
3. UNIX for Dummies Questions & Answers
Hi guys, I'm new to these forums. I'm more of a Windows guy, but I work at an electronics manufacture company that uses Solaris 10 extensively. We have Sunfire v480 servers set up to do system level testing. Everything is networked so you telnet into any server from any computer in the facility.... (1 Reply)
Discussion started by: Daniel.a
1 Replies
4. BSD
HI!
Because ppp deamon by no means reconnect if connection droped i try mpd. Mpd successful recoennct and all works fine except one problem, MSN messenger can't sign in (error 81000360). With ppp deamon msn works good.
With mpd and ppp have exactly firewall settings "OPEN"...
Where is the... (4 Replies)
Discussion started by: sniper007
4 Replies
5. UNIX and Linux Applications
Hi, I copied source of the pidgin open source, and installed in LINUX,
I successfully login to gtalk using pidgin , but my problem is when i send a message , it
successfully sent to the receiver. but iam not able to receive messeges from other. if anybody knew it please let me know that... (1 Reply)
Discussion started by: ch.siva
1 Replies
6. Red Hat
Dear All
I m running Linux Proxy Server on RHEL-5 64bit for providing http access to users in my office, i m facing a problem while using msn messenger on LAN, we access msn messenger through above mentioned proxy server, whenever I sign in to msn messenger, it gets signed on but after a short... (1 Reply)
Discussion started by: surfer24
1 Replies
7. Red Hat
I have configured squid-2.6 and Dansguardian 2.10.0.3 on RHEL5 for caching and web filtering for my office internet users. i m facing problems in loging into msn messenger, i have put acls in squid and msn ips in dansguardian exceptionsite list but still not getting msn messenger login, my squid... (1 Reply)
Discussion started by: surfer24
1 Replies
8. Solaris
I know this is not maybe a good place to start this topic , so if I opened in wrong place please move it were belongs.
My question is maybe stupid , but I can not connect to msn network with pidgin.
I used google , it seems pidgin has a problem connecting on msn .
I tried to install amsn... (1 Reply)
Discussion started by: solaris_user
1 Replies
LEARN ABOUT NETBSD
tftp-proxy
TFTP-PROXY(8) BSD System Manager's Manual TFTP-PROXY(8)
NAME
tftp-proxy -- Internet Trivial File Transfer Protocol proxy
SYNOPSIS
tftp-proxy [-v] [-w transwait]
DESCRIPTION
tftp-proxy is a proxy for the Internet Trivial File Transfer Protocol invoked by the inetd(8) internet server. TFTP connections should be
redirected to the proxy using the pf(4) rdr command, after which the proxy connects to the server on behalf of the client.
The proxy establishes a pf(4) rdr rule using the anchor facility to rewrite packets between the client and the server. Once the rule is
established, tftp-proxy forwards the initial request from the client to the server to begin the transfer. After transwait seconds, the pf(4)
NAT state is assumed to have been established and the rdr rule is deleted and the program exits. Once the transfer between the client and
the server is completed, the NAT state will naturally expire.
Assuming the TFTP command request is from $client to $server, the proxy connected to the server using the $proxy source address, and $port is
negotiated, tftp-proxy adds the following rule to the anchor:
rdr proto udp from $server to $proxy port $port -> $client
The options are as follows:
-v Log the connection and request information to syslogd(8).
-w transwait
Number of seconds to wait for the data transmission to begin before removing the pf(4) rdr rule. The default is 2 seconds.
CONFIGURATION
To make use of the proxy, pf.conf(5) needs the following rules. The anchors are mandatory. Adjust the rules as needed for your configura-
tion.
In the NAT section:
nat on $ext_if from $int_if -> ($ext_if:0)
no nat on $ext_if to port tftp
rdr-anchor "tftp-proxy/*"
rdr on $int_if proto udp from $lan to any port tftp ->
127.0.0.1 port 6969
In the filter section, an anchor must be added to hold the pass rules:
anchor "tftp-proxy/*"
inetd(8) must be configured to spawn the proxy on the port that packets are being forwarded to by pf(4). An example inetd.conf(5) entry fol-
lows:
127.0.0.1:6969 dgram udp wait root
/usr/libexec/tftp-proxy tftp-proxy
SEE ALSO
tftp(1), pf(4), pf.conf(5), ftp-proxy(8), inetd(8), syslogd(8), tftpd(8)
CAVEATS
tftp-proxy chroots to /var/chroot/tftp-proxy and changes to user ``_proxy'' to drop privileges.
BSD
May 31, 2007 BSD