Re: Help please
> On 17 Nov 2018, at 8:00 pm, macports-users-requ...@lists.macports.org wrote: > >> The problem is definately the modem. I turned OFF the firewall (actually >> I need to think thru, why would the modem have a firewall at all, unless >> bad guys can login to the modem …) and rsync ran perfectly. I tried but >> was not able to make a modem firewall rule for rsync. So turn off >> firewall, selfupdate, turn on is pretty painless. > > Again, as an Aussie NBN user I have had zero problems with it, and I > didn't have to do anything special (other than port-redirects to my > FreeBSD server). You are with T$, aren't you, with the Fast 5355 router? > > And yes, you *do* need the firewall enabled, to at least "Medium" i.e. > inbound traffic only in response to outbound traffic, and block everything > below NetBIOS. > > You do have remote access disabled, don't you? And even then, T$ can > "upgrade" your firmware in the middle of the night, and the first you know > about it is when the Mac has dropped the WiFi connection and failed to > restart (you need to disable/enable it, and hope that it gloms onto the > right service). My motivation in continuing this thread is that unless macports users are rare in Aussie (how sad that would be) then other macport users are certain to have the magic big T$ modem. (T$ is joke reference to Telstra) I do not use the modem wifi, apple do not play nice with furren AC modems (my tests are 5Mb / sec close to a tp link and 35Mb to an airport using my macbook) Dave I do not understand your > And yes, you *do* need the firewall enabled Any out going packet will be NAT’d and allowed back Any intruding packet will not be NAT’d and dumped by the router. There is no pathway from the internet to any of mymachine unless the packet is ESTABLISHED, RELATED The best answer that I can find is that if you have and infected machine the firewall prevents it calling other machines. Well my network is linux and mac machines only, so I guess that is of little concern James
Re: Help please
On Sat, 17 Nov 2018, James Linder wrote: Why on earth would would the modem have a firewall? (but their firmware is ratty so maybe thet are protecting their modem) Because it's not so much a modem as a router. If anything can be said to be the modem then it's the NBN box itself, converting the VDSL (if FTTN) or fibre (if FTTP) to a gigabit WAN connection to the router. Please understand network terminology before using it. And yes, the T$ helldesks are utterly clueless, since being outsourced to Asia; they merely read from a script. But this is getting grossly OT, and the problem would appear to lie fairly and squarely with your kit. -- Dave
Re: yelp fails to build on Mojave
Done. On Sat, Nov 17, 2018 at 2:10 PM Chris Jones wrote: > > > On 17 Nov 2018, at 4:41 pm, Carlo Tambuatco wrote: > > yelp (a dependency of gnucash) fails to build on macOS Mojave. > > Log file is attached. > > Don't know if a ticket on this is filed yet... > > > Then take a look and submit one if need be. > > https://trac.macports.org/wiki/Tickets > > Mails to the user lists are not the way submit bug reports. > > > >
Re: yelp fails to build on Mojave
> On 17 Nov 2018, at 4:41 pm, Carlo Tambuatco wrote: > > yelp (a dependency of gnucash) fails to build on macOS Mojave. > > Log file is attached. > > Don't know if a ticket on this is filed yet... Then take a look and submit one if need be. https://trac.macports.org/wiki/Tickets Mails to the user lists are not the way submit bug reports. >
yelp fails to build on Mojave
yelp (a dependency of gnucash) fails to build on macOS Mojave. Log file is attached. Don't know if a ticket on this is filed yet... <>
Re: gimp2 install
Well, some progress: I was able to get over the hump by not updating all dependencies (-n switch), given that I actually have older versions of e.g. zstd and libtiff already installed. Much to my amazement gimp2 actually built. And it even runs, albeit complaining bitterly about tiff being out of date, D-Bus not running and some other assorted odds and ends. That said, it actually opens tiff (16 bit) files and jpegs just fine and seems to save as well. However, as I expected it is the Xwindows version. To get the macOS GUI I assume I need to use the variant quartz. But, do I need to completely hose the present install or can I just deactivate it? I'd kind-of like to keep the Xwindows version around in case I cannot get the macOS GUI version to work. Already it is better than what I had before. Thanks, Uli On 11/16/18 3:02 AM, Ryan Schmidt wrote: On Nov 15, 2018, at 19:14, Riccardo Mottola wrote: Hi, as you thought, it is specific ASM stuff, so the typos are relative to a precise architecture only, On 2018-11-14 20:55:58 +0100 Ryan Schmidt wrote: On Nov 14, 2018, at 11:17, Riccardo Mottola wrote: I wonder if this will cause issues on my 10.5 at the next upgrade, since it is 32bit form me.. I'll see. zstd and tiff built successfully on our 10.5 PowerPC builder. The problem may be specific to 32-bit Intel, or it may be specific to Snow Leopard. the previous patch was incomplete! Get this one... not just a backport, I had to fix the ASM stuff! I rock! Late in the night.. but this fixes 32bit intel. Riccardo Thanks, well done. The first patch was already applied upstream and is in 1.3.7; as I said we should update to that version. https://github.com/facebook/zstd/commit/16bb8f1f9e8ec952458be9681a125d29627cdde9 I have submitted a PR to the developers to make the relevant part of the second change: https://github.com/facebook/zstd/pull/1418 I will submit a PR to update our port to 1.3.7 and include that patch.
Re: Help please
On 16/11/2018 04:28, James Linder wrote: > >> On 16 Nov 2018, at 11:14 am, Ryan Schmidt wrote: >> >> >> >> On Nov 15, 2018, at 00:51, j...@tigger.ws wrote: >> >>> The new bit is a Telstra NBN modem (for Aus’s new high speed broadband.) If >>> any Aus user has tamed the Telstra NBN modem please tell me what and how. >> Have you tried using a closer mirror instead of the master (which is in >> Germany)? >> >> https://trac.macports.org/wiki/Mirrors >> >> You can separately configure where base is downloaded from during selfupdate >> (macports.conf) and where ports are downloaded from during selfupdate or >> sync (sources.conf). >> >> We have a mirror in Australia, unfortunately for some reason they don't >> mirror base. I'll have to have a word with them about that. Maybe there is >> another mirror that's closer to you than the master. Maybe try the one in >> New Caledonia. >> >> The Australian mirror does mirror ports, so you could use it for that. >> >> Trying different servers could also be a troubleshooting step to narrow down >> whether it's a problem with all rsync traffic or just with reaching specific >> servers. > Ryan thanks. > The problem is definately the modem. I turned OFF the firewall (actually I > need to think thru, why would the modem have a firewall at all, unless bad > guys can login to the modem …) and rsync ran perfectly. I tried but was not > able to make a modem firewall rule for rsync. > So turn off firewall, selfupdate, turn on is pretty painless. > > James Have you tried explicitly opening 873/tcp outgoing? Have you tried using iftop or wireshark to see what is/isn't being connected to? Russell
