Meteobridge is not directly communicating with the console, the Meteobridge listens to the traffic Weatherlink is listening to also.
Does not matter if it is USB or IP, the only think needed is the Davis console.
It will not work with any other setup, not with a Meteobridge PRO red or Meteostick f.i.
Not sure I totally recognise that description. Let's start from a configuration where first there's no separate PC and WLfW connected, and MB is linking direct to the IP logger. MB must be polling the logger in the usual way for LOOP data. That's all OK.
Then add in the separate PC and WLfW. If that's pointed at the IP logger's IP address then the WLfW will also be polling the logger for data. Happy to be proved wrong but I'd be surprised if MB detects the change in configuration and switches to some mode of listening. (Not sure how it listens to non-UDP packets intended for WLfW, but maybe there's a way.)
I can see a configuration where WLfW is pointed instead at the MB IP address to make use of the MB passthrough mode. But I'm not surprised to hear of issues downloading
archive data as distinct from receiving LOOP data.
But re the OP's problem: There's almost certainly no problem with the IP logger, but with the WLfW data files which have got corrupted or all the usual problems of datetime etc not being adequately synchronised. That needs fixing.
But more generally, if it's an IP logger then presumably (?) it is also uploading to weatherlink.com. Assuming so, then the best way of grabbing the archive data is via direct download from weatherlink.com using the Web Download option via the v1 API, which still works for free AFAIK. (That's the Web Download setting in the WLfW Communication Port dialogue.) Simply don't try to download the archive data direct from the logger (or via MB come to that).