-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/31/2017 07:02 AM, Tom Eastep wrote:
> On 03/31/2017 02:44 AM, Kade W. Hampson wrote:
>> Ok, this is now an ongoing issue, I am constantly having to type
>> "shorewall allow 192.168.0.3"
>
>
> Are you using BLACKLIST policies?
>
Or,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/31/2017 02:44 AM, Kade W. Hampson wrote:
> Ok, this is now an ongoing issue, I am constantly having to type
> "shorewall allow 192.168.0.3"
>
Are you using BLACKLIST policies?
- -Tom
- --
Tom Eastep\ Q: What do you get when you
>
Subject: Re: [Shorewall-users] Weird NAT issue
Well, it turns out that Shorewall had just decided to reject the HyperV
Server's IP.
Which is pretty funny because looking through the original dump that I
posted there is no mention of the Drop/Reject?
Is this just Admin error? Or a bug.
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/28/2017 08:16 AM, Kade W. Hampson wrote:
> Well, it turns out that Shorewall had just decided to reject the
> HyperV Server's IP. Which is pretty funny because looking through
> the original dump that I posted there is no mention of the
>
lists.sourceforge.net>
> Subject: Re: [Shorewall-users] Weird NAT issue
>
> On 3/21/2017 9:43 AM, kadham1 wrote:
>> If my server was bypassing it's VLAN configuration it wouldn't be
> able
>> to ping any other devices on the 192.168.0/24 subnet.
>> So this leads me
all-users@lists.sourceforge.net> Subject: Re: [Shorewall-users] Weird
NAT issue
On 3/21/2017 9:43 AM, kadham1 wrote:
> If my server was bypassing it's VLAN configuration it wouldn't be able
> to ping any other devices on the 192.168.0/24 subnet.
> So this leads me to the only device
sourceforge.net>
> Subject: Re: [Shorewall-users] Weird NAT issue
>
What does your eth0 connect to? Is it on the same switch but supposed
to be on a different VLAN?
--
Check out the vibrant tech commu
the OS every
night, so possibly a rouge update?
Original message From: Ryan Joiner <ry...@idatasys.com> Date:
22/3/17 1:59 am (GMT+10:00) To: Shorewall Users
<shorewall-users@lists.sourceforge.net> Subject: Re: [Shorewall-users] Weird
NAT issue
On 3/20/2017 3:47
On 3/20/2017 3:47 PM, kadham1 wrote:
> I totally missed that, eth0 is my external/wan interface on the router,
> but it is VLANed to stop any communication with it unless going through
> the router.
>
>
Crazy! Somehow packets are arriving on that interface and thus.. it
ain't gonna work... :)
; Date:
21/3/17 3:24 am (GMT+10:00) To: Shorewall Users
<shorewall-users@lists.sourceforge.net> Subject: Re: [Shorewall-users] Weird
NAT issue
On 3/20/2017 9:38 AM, kadham1 wrote:
> No it doesn't unfortunately, but that being said it is on the same VLAN
> as all machines on
elstra Mobile Network
>
> Original message
> From: "Robert K Coffman Jr. -Info From Data Corp."
> <bcoff...@infofromdata.com>
> Date: 21/3/17 2:23 am (GMT+10:00)
> To: Shorewall Users <shorewall-users@lists.sourceforge.net>
> Subject: Re: [Shorewall-
an Jr. -Info From Data
Corp." <bcoff...@infofromdata.com> Date: 21/3/17 2:23 am (GMT+10:00) To:
Shorewall Users <shorewall-users@lists.sourceforge.net> Subject: Re:
[Shorewall-users] Weird NAT issue
> On 3/20/2017 11:52 AM, kadham1 wrote:
> I am getting log events
> Unfortunately one of my servers (192.168.0.3) is not able to communicate
> with any other subnets, including WAN.
Kade,
If 192.168.0.2 is working fine and 192.168.0.3 can communicate to its
own subnet with no issue, I'd check the default gateway on 192.168.0.3.
- Bob
Hey guys,
I have been having an issue with one of my servers for a couple weeks, and
it has me absolutely stumped.
So I use shorewall on the router that does all my cross-subnet routing.
Unfortunately one of my servers (192.168.0.3) is not able to communicate
with any other subnets,
14 matches
Mail list logo
