Hi Rupert I understand but any clue why it has traffic with Mainframe IP when it is not even listening on any application
On Mon, 23 Dec, 2019, 12:28 PM Rupert Reynolds, <[email protected]> wrote: > 0.0.0.0 is a special "no address" or "any address", depending on context. > > If a listening server socket binds to 0.0.0.0 then it listens on any > interfaces present, which might be two adaptors with addresses > 192.168.something and 10.something, for example. > > 0.0.0.0 is non-routable and a typical use in traffic would be in DHCP, in > which an adaptor doesn't have an address assigned yet and the device sends > out a DHCP request from 0.0.0.0 asking to be assigned a proper address. > > I'd ask for clarification, myself :-) > > On Mon, 23 Dec 2019, 07:53 Jake Anderson, <[email protected]> > wrote: > > > Hello > > > > Cross posted > > > > Out network vulnerability team has reported that there is a traffic > between > > 0.0.0.0 and LPAR IP. > > > > Does it mean 0.0.0.0 listen to all address and make server open to > internet > > ? > > > > I believe 0.0.0.0 belongs to BPXOINIT(OMVS) > > > > Regards > > Jake > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
