Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.98 minutes in June 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

Shorewall forward reject – How to resolve the error

by | Feb 14, 2021

Stuck with the error Shorewall forward reject? We can help you.

Shorewall is a firewall tool that makes the task of network security easier. However, the error is the result of rejecting the connection request.

As part of our Server Management Services, we assist our customers with several Shorewall errors.

Today, let’s get into the details on how our Support Engineers fix the error, Shorewall forward reject.

 

Why Shorewall forward reject?

We use Shorewall as a firewall for security purposes. The rules added in the Shorewall will reject access from unwanted IP addresses.

All the rules are present in the following configuration file.

/etc/shorewall/rules

Rules in this file govern connection establishment. It allows requests and responses automatically using connection tracking.

For instance, the error appears as:

Shorewall forward reject

The rejected/dropped packets logged out of the INPUT or FORWARD chains indicate the following.

  1. Users zone definitions screw up and the host sending the packets or the destination host isn’t in any zone.
  2. The source and destination hosts are both connected to the same interface and user don’t have a policy or rule for the source zone to or from the destination zone or user haven’t set the route back option for the interface in /etc/shorewall/interfaces.
  3. Two firewall interfaces connect (from different zones) to the same hub or switch.

Moving ahead, let’s see how our Support Engineers fix this error.

 

How can we resolve this problem?

At Bobcares, where we have more than a decade of expertise in managing servers, we see many customers face the error, Shorewall forward reject.

Now, let’s see how our Support Engineers fix it.

Recently, one of the customers approached us with SHOREWALL:FORWARD:REJECT error log from the users /var/log/messages file. The customer was unable to access google.com from his LAN.

While checking Shorewall configuration files, we could trace that the entry ‘all all REJECT info in the cat /etc/shorewall/policy Shorewall configuration is the cause of the problem.

cat /etc/shorewall/policy
$FW all ACCEPT
loc $FW ACCEPT
all all REJECT info

Thereafter, in order to resolve the issue, we add the following line in the cat /etc/shorewall/policy.

loc net ACCEPT

It indicates that it opens all ports to outside for LAN and so the connection had established.

Similarly, another user came to us with the following error message.

Jun 27 15:37:56 gateway kernel: Shorewall:all2all:REJECT:IN=eth2
OUT=eth1 SRC=192.168.x.x
DST=192.168.x.x LEN=67 TOS=0x00
PREC=0x00 TTL=63 ID=5805 DF
PROTO=UDP SPT=1803 DPT=53 LEN=47

On further checking this problem, we traced that 192.168.x.x was in the “dmz” zone and 192.168.x.x is in the “loc” zone. The rule was missing in the configuration file, so we added the following.

Finally, the error had resolved.

[Failed to resolve the error? We’ll fix it for you.]

 

Conclusion

In short, the ‘Shorewall forward reject’ error mainly occurs when there is any misconfiguration or missing in the rules added to the Shorewall configuration files. Today, we saw how our Support Engineers helped the customers in fixing this problem.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF