Early in this thread you mentioned these are on different network subnets.
. .
Just thought about a similar issue. . .
sysctl -a | grep rp_filter
If a packet comes in to Linux and the path BACK to the remote IP is NOT out
that same interface (asymmetric routing) the Linux kernel will drop the
p
On Wed, Apr 18, 2018 at 08:52:32PM -0400, Asif Iqbal wrote:
> I tested with firewalld turned off and selinux all permissive. I also did
> not see any denied in audit log
> related to this when selinux was enforced
Have you checked the *client* firewall? TFTP responses to client
requests are block
On Wed, 2018-04-18 at 20:52 -0400, Asif Iqbal wrote:
> On Thu, Apr 12, 2018 at 9:26 AM, Steven Tardy wrote:
>
> > Reading back through prior emails. . . TFTP client requests packets *are*
> > making it to the TFTP server. So it seems like something on the TFTP server
> > itself.
> >
>
> Right.
On Thu, Apr 12, 2018 at 9:26 AM, Steven Tardy wrote:
> Reading back through prior emails. . . TFTP client requests packets *are*
> making it to the TFTP server. So it seems like something on the TFTP server
> itself.
>
Right. I am not sure how to debug that
>
> Like previously mentioned server
On Thu, Apr 12, 2018 at 2:25 AM, peter.winterflood <
peter.winterfl...@ossi.co.uk> wrote:
>
> have you checked that tftp is added to hosts.allow.
> syslog may be reporting libwrap errors, libwrap is trcpwrappers
> regards peter
>
>
>
yes hosts.allow is wide open and I did test with tcpdmatch and i
Reading back through prior emails. . . TFTP client requests packets *are*
making it to the TFTP server. So it seems like something on the TFTP server
itself.
Like previously mentioned server side
firewall/iptables/tcp-wrappers/selinux are all possible culprits.
Hmmm just thought of something else
On Thu, Mar 29, 2018 at 12:48:15PM -0400, Asif Iqbal wrote:
> I do not see tftp traffic is leaving from S
>
> A:~$ tftp
> (to) 192.168.1.20
> tftp> get file
> Transfer timed out.
>
> As you can see no pkt is leaving. If it were leaving S, but A were not
> receiving then I would think firewall
> i
have you checked that tftp is added to hosts.allow.
syslog may be reporting libwrap errors, libwrap is trcpwrappers
regards peter
On 11 April 2018 16:57:04 "Asif Iqbal" wrote:
On Thu, Mar 29, 2018 at 12:48 PM, Asif Iqbal wrote:
>
>
> On Thu, Mar 29, 2018 at 7:21 AM, Steven Tardy wrote:
>
On Thu, Mar 29, 2018 at 12:48 PM, Asif Iqbal wrote:
>
>
> On Thu, Mar 29, 2018 at 7:21 AM, Steven Tardy wrote:
>
>> A STATEFUL firewall with “ip any any” can and will still block asymmetric
>> communications due to the firewall keeping track of state (hence tha name
>> stateful firewall).
>>
>>
On Thu, Mar 29, 2018 at 7:21 AM, Steven Tardy wrote:
> A STATEFUL firewall with “ip any any” can and will still block asymmetric
> communications due to the firewall keeping track of state (hence tha name
> stateful firewall).
>
> Tcpdump on your servers /other/ NICs and you’ll see the tftp traff
A STATEFUL firewall with “ip any any” can and will still block asymmetric
communications due to the firewall keeping track of state (hence tha name
stateful firewall).
Tcpdump on your servers /other/ NICs and you’ll see the tftp traffic
leaving your server on some other NIC (probably on with the d
On Wed, Mar 28, 2018 at 9:15 PM, Asif Iqbal wrote:
>
>
> On Wed, Mar 28, 2018 at 6:25 PM, Steven Tardy wrote:
>
>> On Wed, Mar 28, 2018 at 3:16 PM Asif Iqbal wrote:
>>
>> > It is not respoding to A server which is sending the tftp read request
>> RRQ.
>> >
>> > I do see the RRQ packets coming f
On Wed, Mar 28, 2018 at 6:25 PM, Steven Tardy wrote:
> On Wed, Mar 28, 2018 at 3:16 PM Asif Iqbal wrote:
>
> > It is not respoding to A server which is sending the tftp read request
> RRQ.
> >
> > I do see the RRQ packets coming from A to S, but S never responds back
> from
> > a different port
On Wed, Mar 28, 2018 at 3:16 PM Asif Iqbal wrote:
> It is not respoding to A server which is sending the tftp read request RRQ.
>
> I do see the RRQ packets coming from A to S, but S never responds back from
> a different port Y to A
>
> So this part is working fine
>
>
>
> https://en.wikipedia.o
I have a tftpd server S running on centos 7 and managed by systemd
It is not respoding to A server which is sending the tftp read request RRQ.
I do see the RRQ packets coming from A to S, but S never responds back from
a different port Y to A
So this part is working fine
https://en.wikipedia.o
15 matches
Mail list logo
