Sponsored Content
Full Discussion: Can't connect to Internet
Operating Systems Solaris Can't connect to Internet Post 302379850 by bartus11 on Saturday 12th of December 2009 04:07:09 PM
Old 12-12-2009
/etc/resolv.conf should contain line like that:
Code:
nameserver 192.168.1.100

where 192.168.1.100 is the IP address of your DNS server.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Cannot connect to the Internet

I running HPUX 11.0, Netscape gives me an error "Unable to locate Server" when using a www.something.com address. If I use an IP address I get past the router and onto the Internet. My workstation can get to the Router @ 192.168.0.1 and also it's local APACHE server. I have DHCP enabled... (8 Replies)
Discussion started by: johnalt
8 Replies

2. Solaris

How to connect Solaris 10 to the internet ?!

ive installed a fresh copy of solaris 10 on a E3500 Server machine, i gave it a static IP address , 192.168.1.15 its a test server in our office (small office) we are using LINKSYS as our internet router and DHCP as well .. its IP is 192.168.1.1 and ive added this IP as Default route on the server... (9 Replies)
Discussion started by: mduweik
9 Replies

3. Solaris

trying to connect to internet

i have just installed solaris 10 on a 60 gb hard drive. now im trying to install my nic driver but when i put in the floppy disk for the nic card it cant read it, so then i found that i have to mount the floppy drive and i tried putting in the mount command but i dont know where to mount it and if... (38 Replies)
Discussion started by: vutty81
38 Replies

4. Solaris

how to connect to internet on Solaris 10

Hi, I am new to Solaris just migrating from Windows XP. I want to connect to internet but I have problem with configuration. My ISP has provided me a router.I get internet connection through DHCP. I don't know any proxy or subnetmask or any IP address that requires during configuration of... (1 Reply)
Discussion started by: pappu2008
1 Replies

5. Solaris

How to connect to Internet

Hi I installed solaris developer edition 1/08 today.I want to connect to Broadband internet through my ADSL 2+ Modem/Router with a username and password. plz help in this case,I am new to sun solaris:confused: the modem itself is a router it worked well on ubuntu and red hat (3 Replies)
Discussion started by: santugvd
3 Replies

6. Linux

how to connect internet????

HI, Am using GPRS ( MOB # 3230 ) internet connection in windows Hw to use internet r connect in linux.. ( Red Hat Linux Ver.10 ) Please help me.. Thanks in adv.. (1 Reply)
Discussion started by: bharath raja
1 Replies

7. UNIX for Dummies Questions & Answers

Solaris 10 - How to connect to internet

I recently installed solaris 10 on a seperate hard disk in my desktop pc. My first hard disk is running windows xp. I am totally new to solaris. Please help me to connect to the internet through solaris 10. I read a few threads, and re-installed solaris 10 by giving 'Yes' to the question that... (1 Reply)
Discussion started by: hari86av
1 Replies

8. Linux

How to connect to internet

Hi, Can someone guide me regarding how to connect to internet. what are steps? Thanks in advance (2 Replies)
Discussion started by: naren nandale
2 Replies

9. Red Hat

How to connect internet in Linux OS?

What all is required so that I can use internet on my Linux OS My OS: Red Hat Fedora version: 2.6 I have to connect via my Nokia cell phone via cable. This way only I had been using internet on my Windows OS. If any software is required to install on my UNIX for internet, then I don't... (1 Reply)
Discussion started by: ravisingh
1 Replies

10. IP Networking

How to connect internet in Linux OS

How to enable internet on my Linux OS My OS: Red Hat Fedora Release 9 (Sulphur) version: 2.6 I have to connect via my Nokia cell phone via cable. This way only I had been using internet on my Windows OS. If any software is required to install on my UNIX for internet, then I don't have any. If... (14 Replies)
Discussion started by: ravisingh
14 Replies
mxallowd(1)							   User Manuals 						       mxallowd(1)

NAME
mxallowd - dynamically whitelist your Mail eXchanger SYNOPSIS
mxallowd [-d] [-c configfile] [-t whitelist-time] [-p pflog-interface] [-l pcap-filter] [-F] [-s] [-q] [-p] -f fake-mailserver -r real- mailserver -n queue-num DESCRIPTION
mxallowd is a daemon which uses libnetfilter_queue (on Linux) or pf and pflog (on BSD) to allow (or deny) connections to a mailserver (or similar application) if the remote host hasn't connected to a fake daemon before. This is an improved version of the so-called nolisting (see http://www.nolisting.org/). The assumption is that spammers are not using RFC 2821-compatible SMTP-clients and are sending fire-and-forget spam (directly to the first or second MX-entry without retrying on error). This direct access is blocked with mxallowd, you'll only get a connection if you retry. NOTE: It is highly recommended to install nscd (nameserver caching daemon) or a similar software in order to speed-up DNS lookups. Since version 1.3, DNS lookups are done in a thread (so they don't block the main process), however, on very-high-traffic-sites, mxallowd may show significantly better overall performance in combination with nscd. OPTIONS
-b, --no-rdns-whitelist Disable whitelisting all IP-addresses that have the same RDNS as the connecting one (necessary for google mail) -c, --config Specifies an alternative configuration file (instead of /etc/mxallowd.conf) -t, --whitelist-time Specify the amount of time (in seconds) until an IP-address will be removed from the whitelist -s, --stdout Log to stdout, not to syslog -q, --quiet Don't log anything but errors. -f, --fake-mailserver Specify which IP-address the fake mailserver has (connecting to it will whitelist you for the real mailserver) -r, --real-mailserver Specify which IP-address the real mailserver has -F, --foreground Do not fork into background, stay on console -n, --queue-num (only available when compiled for netfilter_queue) Specify the queue number which will be used for the netfilter_queue-link. This has to be the same which is specified in the ipta- bles-rule and it has to be specified, there is no default. -p, --pflog-interface (only available when compiled for pf) Specify the pflog(4) interface which you configured in pf(4). The default is pflog0. Also see the pcap-filter-option if you use an interface which does not only get smtp-traffic. -l, --pcap-filter (only available when compiled for pf) Specify the filter for pcap. The default is "port 25". See tcpdump(8) for more information on the filters. FILES
/etc/mxallowd.conf System-wide configuration file. Use the long options without the beginning two dashes. For example: stdout fake-mailserver 192.168.1.3 fake-mailserver 192.168.1.4 real-mailserver 192.168.1.5 queue-num 23 EXAMPLES FOR NETFILTER
The machine has two IP-addresses. The mailserver only listens on 192.168.1.4, the nameserver returns the mx-records mx1.domain.com (192.168.1.3) with priority 5 and mx2.domain.com (192.168.1.4) with priority 10. # modprobe nfnetlink_queue # iptables -A INPUT -p tcp --dport 25 -m state --state NEW -j NFQUEUE --queue-num 23 # mxallowd -s -F -f 192.168.1.3 -r 192.168.1.4 -n 23 Then open a separate terminal and connect via telnet on your real mailserver. You'll see the connection attempt being dropped. Now connect to the fake mailserver and watch mxallowd's output. Afterwards, connect to the real mailserver to verify your mailserver is still working. EXAMPLES FOR PF
The machine has two IP-addresses. The mailserver only listens on 192.168.1.4, the nameserver returns the mx-records mx1.domain.com (192.168.1.3) with priority 5 and mx2.domain.com (192.168.1.4) with priority 10. Create a pf.conf like this: table <mx-white> persist real_mailserver="192.168.1.4" fake_mailserver="192.168.1.3" real_mailserver6="2001:dead:beef::1" fake_mailserver6="2001:dead:beef::2" pass in quick log on fxp0 proto tcp from <mx-white> to $real_mailserver port smtp pass in quick log on fxp0 inet6 proto tcp from <mx-white> to $real_mailserver6 port smtp block in log on fxp0 proto tcp to { $fake_mailserver $real_mailserver } port smtp block in log on fxp0 inet6 proto tcp to { $fake_mailserver6 $real_mailserver6 } port smtp Afterwards, load it and start mxallowd using the following commands: # pfctl -f /etc/pf.conf # mxallowd -s -F -f 192.168.1.3 -r 192.168.1.4 Then open a separate terminal and connect via telnet on your real mailserver. You'll see the connection attempt being dropped. Now connect to the fake mailserver and watch mxallowd's output. Afterwards, connect to the real mailserver to verify your mailserver is still working. The ruleset for pf is actually longer because pf does more than netfilter on linux -- netfilter passes the packets and lets mxallowd decide whether to drop/accept whilst pf blocks/passes before even "passing" to mxallowd. SEE ALSO
iptables(8), pf(4), pflog(4), tcpdump(8) AUTHOR
Michael Stapelberg <michael+mxallowd at stapelberg dot de> Linux MARCH 2012 mxallowd(1)
All times are GMT -4. The time now is 09:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy