[swinog] Re: Swisscom DNS issue: spectrum-conference.org wrongfully resolves to a bluewin address in swisscom mobile networks
Hello, On Tue, Apr 23, 2024 at 10:04:14AM +0200, Stefan via swinog wrote: > But you know that it is already daily business that Swiss ISP's are blocking > websites? One of the example you give was voted by the Swiss people (Casino blocking). ISP have no say in that matter. Some countries go way further in blocking "content" (as was mentionned on the list earlier). But here, we are discussing additional security measures that some ISPs, including Swisscom, are taking: Swiss people did not vote yet about blocking malware. And Swisscom also blocks / intercepts / redirects SMTP for quite a few years now, for end users. On port 25 (not on 587 nor 465 AFAIK). I think they are pretty unique in that aspect (other ISPs usually simply block incoming port 25, they don't AFAIK filter out outgoing). > Use other DNS-Servers if you want to be "free", but accept the risk. That could be a solution: an opt-out. It *seems* to me that Sunrise, e.g., actually even offers an opt-in, as their firewalling service is usually valued at 5 CHF/month but in essence free to the end user (not sure what it really does) and can be refused when ordering. In my opinion, the most important thing is that the blocking be documented to the end-user, even on every month's invoice, and that opt-out (or opt-in) be offered for everything that is not compulsory by law. Have a nice day. ___ swinog mailing list -- swinog@lists.swinog.ch To unsubscribe send an email to swinog-le...@lists.swinog.ch
[swinog] Re: Microsoft massive spam outbreak
Hello, On Mon, Jan 22, 2024 at 04:07:26PM +0100, Benoit Panizzon via swinog wrote: > I am aware, Microsoft Office365 customer service blames this on us > 'falsely and for no reason' blocking email from those ip addresses, and > when presented with Evidence of what happened, they close the case with > 'issue solved' which was never the case. I see, here you can see a more detailed feedback (mostly from users though): https://answers.microsoft.com/en-us/outlook_com/forum/all/microsoft-outlook-365-server-blacklisted-by-spam/851d8fc4-11b9-445a-860b-1704897a02b2 A customer of mine was hit with his problem, and I suggested work-arounds and to show the customer customer's the extent of the problem. The obvious solution would be that everyone gets a Microsoft hosted mail service and drops independant service providers :) NB: apart from the joke, it gets every day more complicated to manage an independant SMTP provider, notably due to a very feelable concentration of individuals, but also enterprises within one or two GAFAMs: unfortunately we no longer live in an Internet world where we can say "Microsoft is irrelevant": most universities and enterprises seem to have been lurred there. ___ swinog mailing list -- swinog@lists.swinog.ch To unsubscribe send an email to swinog-le...@lists.swinog.ch
[swinog] Re: How to destroy data effectively?
Hello, On Fri, Dec 02, 2022 at 03:55:23PM +0100, Patrick Studer via swinog wrote: > We recommend remove them from computers and bring them to a company named XXX > (to professional shred them). As a joke, we now know where to look for your data :) ___ swinog mailing list -- swinog@lists.swinog.ch To unsubscribe send an email to swinog-le...@lists.swinog.ch
[swinog] Re: switch started blocking whois queries?
Hello, whois alphanet.ch works from UPC/Sunrise, SWITCH and init7 for me. The disclaimer and some of the data are still there. ___ swinog mailing list -- swinog@lists.swinog.ch To unsubscribe send an email to swinog-le...@lists.swinog.ch
Re: [swinog] SPF checking on upcmail.net failing
Hello, On Tue, Jan 25, 2022 at 02:38:58PM +0100, Marc SCHAEFER wrote: > On Tue, Jan 25, 2022 at 01:03:23PM +, Beat Eichenberger wrote: > > Is there a UPC mailadmin following this list? > > Also, the return address for billing bounces: > > : host mx2.tripolis.com[87.253.151.86] said: 450 > 4.1.1 > : Recipient address rejected: unverified > address: > User unknown in virtual alias table (in reply to RCPT TO command) First, this may actually not be a domain that UPC controls, but it is where the invoices are sent from (beware, there are some spams out there that mimic invoicing or refunds, but this was not the problem here). As I contacted UPC through various means during the last month (including registered postal mail :->), they finally replied by e-mail today and they have solved the problem I raised on the 27th of December. No idea if the mail to swinog sped up the process or not. However, they did not comment if their invoice provider fixed, or not, this e-mail address issue or not. Thank you for the various replies I got through the list. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] SPF checking on upcmail.net failing
On Tue, Jan 25, 2022 at 01:03:23PM +, Beat Eichenberger wrote: > Is there a UPC mailadmin following this list? Also, the return address for billing bounces: : host mx2.tripolis.com[87.253.151.86] said: 450 4.1.1 : Recipient address rejected: unverified address: User unknown in virtual alias table (in reply to RCPT TO command) ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] UPC Cablecom IPv6 verschwunden?
On Thu, Jan 06, 2022 at 01:06:33PM +0100, Lukas Knauer wrote: > Was that ever available? iirc Cablecom/UPC offers either IPv4-only or > IPv6+CGNAT (aka "Dualstack lite"). But no real dual stack. BTW, I made a video about how to create IPv6 servers on an *end-user* connection, and I mention the DSLite versus "modem" issue. https://peertube.gaialabs.ch/w/wcxPAsaqNU9EskfSRRiPFb https://www.youtube.com/watch?v=X60zts9YvXk That was done with the small UPC black box in DSLite mode (I think that's a Connect Box), last year. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
[swinog] SPF/DMARC sunrise issue
Hello, I am only using SPF, DKIM and DMARC information to up points in my spamassassin (there are too many badly configured SPF sites around, and they most of the time are not DNSSEC-secured). In general, SPF/DMARC alone is not enough to mark as spam in my opinion. However, someone reported the following issue with Sunrise: apparently they are lacking at least ONE of their webmail SMTP senders in their SPF records: 195.141.178.228 for example. dplanet.ch descriptive text "v=spf1 mx include:spf.sunrise.ch -all" spf.sunrise.ch descriptive text "v=spf1 ip4:195.141.178.100 ip4:195.141.178.101 ip4:195.141.178.220 ip4:195.141.178.221 ip4:195.141.178.223 ip4:195.141.178.229 ip4:195.141.178.94 ip4:195.141.178.95 ip4:195.141.178.96 ip4:195.141.178.71 ip4:195.141.178.199 ip4:195.141.178.74 195.141.178." It especially may break dplanet.ch senders as their DMARC policy is quarantine (sunrise's is none). Gmail was for example reporting random problems depending on the sunrise sender (webmail) SMTP IP address: ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of innocent-bu...@dplanet.ch designates 195.141.178.229 as permitted sender) smtp.mailfrom=innocent-bu...@dplanet.ch; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=dplanet.ch ARC-Authentication-Results: i=1; mx.google.com; spf=fail (google.com: domain of innocent-bu...@dplanet.ch does not designate 195.141.178.228 as permitted sender) smtp.mailfrom=innocent-bu...@dplanet.ch; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=QUARANTINE) header.from=dplanet.ch Sunrise end-user support did not seem to notice yet, so if someone around here has better / direct contact, it would be handy. Have a nice week-end anyway. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] OVH
On Sat, Apr 17, 2021 at 08:59:28AM +0100, Klaus Ethgen wrote: > do any of you know just one legit service that is hosted by OVH? I use them as a DNSSEC registrar. A friend had a cache which took fire. > They own massive amount of /16 networks and many of them are already in > my blocklist as I have seen massive server attacks from that OVH > networks. Last year, I did some statistics about attacks while reporting them first to the block's abuse, then to abuseipdb.com. Most of the problems I had came from China, where the abuse addresses never worked. I informed the registry, they started an abuse e-mail verification campaign (like RIPE does regularly), but after a few months problems restarted. Then, most of the other attacks came from Online (which was a pity, because they don't have an usable e-mail address, you can only report through a web interface with a CAPTCHA, they simply forward the request to the end user and if he does not reply they close the account: and you can't even interact with the end user: I got so many "What should I do? I don't know what's the problem" ...). I even once had to send them postal mail when their report form was broken, and they replied with a non-repliable e-mail address. Then it's Microsoft, then Google, then many others. OVH: not a lot of attacks came from them at least last year. I have stopped sending abuse e-mails and I am only reporting to abuseipdb.com now, which I use to filter access to some services. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] G.Fast DSL modems - bridge only
On Thu, Apr 01, 2021 at 12:26:19PM +0200, Benoît Panizzon wrote: > Actual situation: I live about 250m away form the DSLAM in the street. > After several cases opened @ Swisscom, they found out it is just about > a little too far away for g.fast to work properly. About 190 m, see images: https://www.alphanet.ch/~schaefer/tmp/fritzbox-init7-FTTS/ ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] G.Fast DSL modems - bridge only
On Thu, Apr 01, 2021 at 11:45:55AM +0200, Jeroen Massar wrote: > Apparently FRITZ!Box 7582 does not do Bridge mode, but Zyxel XMG3927 does. I am running a FRITZ!Box 7582 in G.fast mode on a FTTS init7 (probably with Swisscom behind it) in bridge mode, terminating the PPP on an apu2. I particularly like the amount of detail you have through the web GUI on the link itself. > Anybody has any positive/negative experiences and/or other recommendations? As the FRITZ!Box is a bit overkill, some people mentionned instead the use of SFP/GBIC converters, but I did not try yet. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Mail rejection at bluewin
On Wed, Mar 31, 2021 at 02:06:24PM +0200, Tobi wrote: > We're seeing the same issue since 28th March. Looks like their new > reputation system needs some fine tuning by a big hammer :-) > Maybe they bought the same reputation system as 1&1 did not long ago. They communicated as follows: "Due to a heavy spam wave before and over the weekend around the 27th of March, Bluewin Mail was forced to temporarily tighten up its policy for large senders. As of today, these rules have been lifted and sending to Bluewin Mail should not lead to rejects or defers anymore. If you still experience issues sending to Bluewin Mail as of today [tuesday], please open up another ticket on our support portal (support.bluewin.ch). " I concur there were more spams last week-end than usual, the catched-up list was about twice as long, and 2 phishing attempts went through on my mail server. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Spam from 'Rocketmails.ch'
On Mon, Dec 28, 2020 at 06:03:28PM +0100, Peter Rohrer wrote: > I got an answer from the federal prosecutor, unfortunately I was to > late and didn't press charges within 3 months after knowing about the That's really short. It is surprising that Wrong accusations prescribe after 5 years, but accusations must be made within 3 monthes. > offender (Art. 31 StGB). So, if you ever get into a similar situation, > don't waste to much time sending letters to the spammer and waiting for > answers. It's already too late, actually, as the culprit happened in august. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Spam from 'Rocketmails.ch'
On Thu, Oct 15, 2020 at 08:54:32PM +0200, Peter Rohrer wrote: > I sent him registered letters to both his "Sandro Achilles Photography > Corporation" (in 2019) and to "ACHILLES ??? Management & Marketing > Consulting" (he received it about 2 Months ago) and did not get any > response so far. I also called his phone number, he claimed someone > else is handling those request for him. If you do not get any reply after one month, I think that then it should be escalated to the proper authorities, as this looks a violation of Swiss law. So far everyone has replied in the legal delay. I sent normal mail (and then registered mail when RocketMails played the `it's not us, it's RocketMountain'). If someone knows more about the legal procedure to follow when there is no reply, I would happily know about it. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Spam from 'Rocketmails.ch'
Hello, Thank you for this valuable information. On Mon, Oct 12, 2020 at 12:21:38PM +0200, Benoit Panizzon wrote: > Please contact SECO (Lena Geiser). They know 'this case' since 2017. > Please contact ECO.de (Mr. Brandolino). They know about him very > recently. I did that. Schober changed its name to Künzlerbachmann. > Of course it would be very very interesting, if your data could also be > tracked back to a customer of Schober who had it's data processed @ > Schober while S.A. was part of their management. Let's wait for Sandro Achille's reply, in a month or so. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Spam from 'Rocketmails.ch'
On Mon, Sep 21, 2020 at 11:35:41AM +0200, Benoit Panizzon wrote: > Update about today's call with Rocket Mountains AG. They just replied, in time. They basically are not answering specific questions about specific e-mail address, inclusive technical addresses that are not linked to a specific person, nor the domain names that I included in the request. They basically say that another company was responsible for the data acquisition and ask me to contact them. They however confirmed having suppressed my personal information. They gave a completely nonsensical reply to the reason why they had that data in the first place. I will send another query to that other company, Sandro Achilles Photography Corporation, Voltastrasse 66, 8044 Zurich and see what happens next. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Spam from 'Rocketmails.ch'
On Tue, Oct 06, 2020 at 09:12:32AM +0200, Benoit Panizzon wrote: > Did you get a reply to your request? Not yet, but they still have about two weeks. > But they don't want to do that and don't (want to) understand that this > leads to spam complaints because the recipient never had any contact > with Rocket Mountain AG before. Contact the SECO please, the more people complain, the higher is that SECO does something. Especially when it's a company complaining. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Spam from 'Rocketmails.ch'
On Mon, Sep 21, 2020 at 11:02:16AM +0200, Benoit Panizzon wrote: > emails originates from Swiss Post customers who agreed that Swiss Post > uses their data for marketing. Well, in my case, they wrote to technical addresses that never were communicated to the Swiss Post. SECO was informed, as this violates SR 241, Art. 3. Abs. 1, 1 lit. Kondition a. SECO told me I could sue them just for that. Depending on how complete they reply to my request, I might. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Spam from 'Rocketmails.ch'
On Sat, Aug 22, 2020 at 12:30:21PM +0200, Peter Rohrer wrote: > I sent an "Auskunftsbegehren" regarding Spam to the Whois address of > rocketsmails.ch in 2018, and I got a first answer by mail (from > rocketleads.ch) and later by written letter (after I send them a second > registered mail) from the Company Rocket Mails AG. After about one month, they answered. They seem to have a third company, Rocket Mountain AG, and thus rejected my request because it was not formally addressed to that company which seems to be now handling addressing for the other two (?). I just resent it, this time as recommandé (eingeschrieben). We will see what they will invent next not to comply with my rights. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Spam from 'Rocketmails.ch'
On Fri, Aug 21, 2020 at 04:24:26PM +0200, Benoît Panizzon wrote: > Today we received several delisting request for URI's and IP Addresses > somehow associated with Newsletters sent by 'Rocketmails.ch'. A few weeks ago, I asked SECO about Rocket Mountain AG & Rocket Leads AG / Christian Huldi General-Wille-Str. 201 CH-8706 Meilen because they sent spam to multiple of my technical addresses, and SECO answered basically this: 1) sending to technical addresses is illegal, because they did not opt-in, and opt-in or having bought something is one of the three cumultative conditions to allow sending advertising e-mail 2) they told the company directly to stop. 3) they told me I can sue the company if I want In German, here is the basic info they send when you complain to SECO: Wir beziehen uns auf Ihre heutige Beschwerde vom betreffend die Versendung von Spamnachrichten durch die [ FIRMA ] Die von Ihnen erwähnten E-Mails könnten möglicherweise unlautere Massenwerbung im Sinne von Art. 3 Abs. 1 lit. o UWG (Bundesgesetz gegen den unlauteren Wettbewerb https://www.admin.ch/opc/de/classified-compilation/19860391/ ; SR 241) darstellen. Gemäss dieser Bestimmung ist der Versand von Massenwerbung nur zulässig, wenn die folgenden drei Bedingungen kumulativ erfüllt sind: a. Der Empfänger hat in den Empfang einer Sendung ausdrücklich eingewilligt oder die Zustimmung des Empfängers ergibt sich aus einem beim Absender getätigten Kauf. b. Die Sendung enthält einen korrekten Absender. c. Die Sendung enthält einen klaren und deutlichen Hinweis, der die Ablehnung des weiteren Empfangs der Massenwerbung problemlos und kostenlos ermöglicht. Sie haben die Möglichkeit, wegen Verletzungen von Art. 3 Abs. 1 lit. o UWG bei der Polizei oder der Staatsanwaltschaft einen Strafantrag gegen den Absender einzureichen und hätten überdies die Möglichkeit, auf dem Zivilprozessweg die Unterlassung der weiteren Zustellung von Massenwerbung zu verlangen. NB: I have no idea if Rocket Mountain AG, Rocket Leads AG and Christian Huldi has any link with rocketmails.ch, however both were hosted at hosttech GmbH which basically told me they wouldn't do anything, and told me to contact the customer: I did that, and got absolutely no reply in the last three weeks. I might send the formular that was mentionned on the list to see where they got that technical address from, thank you for the hint. I have decided not to sue for the moment, this is very time consuming. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Broken SPF Check implementation in Microsoft Exchange Forefront?
On Mon, Dec 02, 2013 at 05:20:25PM +0100, Klaus Ethgen wrote: I had one of this issue in Univerity too. same in the cantonal mail server ne.ch. customer had to hack a pipe to a procmail to change the enveloppe so that a simple mail reflector works. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Cablecom offline?
On Fri, Mar 16, 2012 at 09:34:35AM +0100, Martin Suess wrote: I'm not at home but my boxes at home (connected via Cablecom) are still reachable. The main problem is that Hosting Cablecom is down, including (some) Cablecom hosting customers. Apparently there is some routing issue. This doesn't seem to impact IP traffic. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Subliminal advertising / Spam from our domain registry switch/nic.ch]
Hi, in my opinion, we should refer to the domain registry as NIC/CH (or nic.ch) It shouldn't be named SWITCH. SWITCH can operate them as long as they have the mission from the OFCOM/BAKOM (expires 2014?). But the name should be NIC/CH and no mention of any SWITCH services should be made with relation to NIC/CH. (remember when non SWITCH customer couldn't get ch. domains ?) ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Debian vs. Ubuntu
On Fri, Jan 29, 2010 at 11:22:04AM +0100, Peter Keel wrote: Yes, but that's absolutely painless. I also regret the times when Debian was only releasing every 3 years or so, however, the current release cycle is not that fast, you still have two years between upgrades, and obsolescence is usually announced one year ahead. I still prefer Debian over Ubuntu, even installed minimally, because Debian has less weight (although it's increasing: I have for example seen with horror that I was touched by the python security bug, because Debian installed python for the ssh-blacklist package -- it's unfortunate those dependancies leak in ...). Remember: the more packages you have installed, the more the administrative overhead will cost. I suggest the following, after the upgrade: sed -i s/etch/lenny/g /etc/apt/sources.list apt-get update apt-get dist-upgrade - start aptitude, check if there are any Obsolete or locally installed packages, remove them, and possibly find new packages to replace them. If you don't do this, those packages might be a security hazard (or just an administrative cost). - maybe use apt-get autoremove (but see below) to get rid of unnecessary installed packages (less packages == less work). - maybe use deborphan to locate unused packages, and remove it. It is always a good idea to read the release notes before upgrading (see http://www.debian.org/releases/stable/). There are many advices there for what to do BEFORE, DURING, and AFTER the upgrade. Other ideas: - I use OpenVZ as a fast, efficient, simple: in a word UNIX-ish virtualization plateform; keeping the host system as simple as possible, basically a hardware layer. Thus non host updates can be tested first on a VZ copy; host updates can be attempted first on similar hardware, especially if you already have some sort of high availability in place. - don't forget to check whether you have added any non standard sources.list entries, those packages are not supported by Debian on upgrades. Of course you haven't installed any package by hand with dpkg -i or converted with alien/rpm that you found on the Internet I hope :) - if you use special administrative tricks (for example package diversions, package holds), be sure to check for them before and after upgrading. - it is generally assumed that any local changes to the system will be done in /usr/local and never to installed packages themselves (diversions come handy here!). Locally installed software (in /usr/local or /opt) is usually not touched by system upgraded, don't forget to update it as necessary yourself. - if you use aptitude, beware of the autoremove features. - use FAI for easy service / system installation (class-based, reproductible) For those who don't know, diversions are a way to tell the packaging system that when it updates a file, it should update it elsewhere. This paves the way for seemless patching and wrapper scripts in-place. Holds are ways to tell the system to never touch (upgrade) a package. There are unfortunately two incompatible holds in Debian: apt/dpkg and aptitude. Recommended books: The Debian system : concepts and techniques, 1-59327-069-0; Cahiers de l'Admin: Debian GNU/Linux (http://www.ouaza.com/livre/admin-debian/extrait-apt.pdf) ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
[swinog] routing quirks with IP-MAN
Hi, It seems the Swiss POP for sixxs (IPv6 connectivity) is unreachable from Cablecom (net2000), Sunrise ADSL, Bluewin ADSL, but is reachable from Green ADSL. For the records, http://www.sixxs.net/) is where you can get free IPv6 on IPv4 tunnels when your ISP hasn't yet arranged for IPv6 end-user delivery (most don't). It used to be reachable in november 2009 when I did my last tests, on Cablecom (net2000). The IP address of the POP is: 194.1.163.40 Looks like this is a /24 (PI) within IP-MAN's AS. Does anyone has an idea why it is not routed correctly ? (SIXXS is working on it, however, what's behind the scene interests me). Is this because it's a lone /24, and most providers don't peer correctly for less than /22 ? An administrative problem (like when EUnet was routed through Amsterdam for SWITCH customers -- well at least it was routed!) Or is it because IP-MAN wants direct peering and doesn't announce the prefix globally ? Maybe to avoid being charged by strange peering plans ? Thanks ;) have a nice new year 2010! PS: I am especially interested because I am considering to route a old /24 from a /15 (allocation unspecified) somehow, and want to see if it is really usually unfeasible from a global routing perspective, or from the practical quirks of commercial operators today. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] routing quirks with IP-MAN
On Mon, Jan 04, 2010 at 09:25:42PM +0100, Pim van Pelt wrote: If you have a /24 you should be generally accepted by most every ISP out there, as far as breaking aggregation of your /15, I cannot comment (but I say: go for it) It's not mine, unfortunately. But I am working with the owner to find a good solution. For reference, look at 193.72.186.0 in the WHOIS :) Thank you for the precize answer on this peering-only routing. I have now asked both of my current service providers (namely net2000 and sunrise) to look into peering. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] mxbw.bluewin.ch timeout
On Wed, Nov 18, 2009 at 10:32:13AM +0100, ralf.zenklu...@barinformatik.ch wrote: For us it was fine for a week now - since they had the ddos. But right now we have 300 emails in queues and can't send these to mxzhb or mxzhh :-( Strangely, I cannot send through cablecom (no SYN/ACK received), however I can send it through Sunrise, albeit slowly. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Embedded Linux practicing
On Tue, Oct 07, 2008 at 04:50:34AM -0700, Stanislav Sinyagin wrote: My first mini-project is to build a small Wifi (or even Bluetooth?) hotspot (only for home use, of course) which would take its Internet feed from one of those mobile USB GPS modems that you get for few francs a month from Swisscom or Sunrise. It is quite easy to do with the WL-500g WiFi access point, which has the advantage of a) being compatible with standard systems (e.g. DD-WRT GNU/Linux) b) having an USB port you can plug the Swisscom Unlimited dongle inside (the one which pretends to be a CD-ROM, uh, a tty) I think it costs about 120.-. I have done it, and it works (routing the Swisscom Unlimited net to the internal switch, not the WiFi, in my case) PS: the discussion on OSS gets annoying. Use whatever tool you find appropriate, as long as you can fix it when required. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Embedded Linux practicing
On Tue, Oct 07, 2008 at 11:44:42AM -0700, Stanislav Sinyagin wrote: Marc, the goal is not to build it from commodity parts, but to learn how to build such systems in general :) From scratch, starting with custom kernel build, then tailored busybox, then web management and stuff... You are talking software here. So, do it yourself. Start by recompiling DD-WRT and download the firmware, see if it works. Then you can do it even more low-level. You can even choose how much low-level you want to be, while still remaining software-oriented. Another approach could be a hardware approach: taking an Ethernut (http://www.ethernut.de/), add-on a USB child card, and develop the drivers for the interface. That will be very teachy! that's what I call open source: working with the source :-) You are right. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Anyone from Green here?
On Thu, Sep 11, 2008 at 10:37:35AM +0200, Per Jessen wrote: One of my customers has just been told he needs to pay to get a DNS reverse map entry for thei Green ADSL line with fixed IP. Is that really true?? I had a similar query lately, and [EMAIL PROTECTED] replied that with MPS1 (1 IP address) they won't do it, they will do it only for MPS8 and with a delegation. That's a pity, but it's how marketing works. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Swisscom wants CHF 31/Month per regulated copper line
On Tue, Mar 20, 2007 at 11:23:38AM +0100, Andre Oppermann wrote: The price seems to be a bit far out when considering that a normal phone line (which includes the telephony infrastructure as well) costs only CHF 25.25/Month. Reading the financial reports of Swisscom You also have to take in account that service was degraded: in 1992, installing a phone line (new, with wiring to the central) took 2 days. They came with two wiring trucks and there were about 5 people. And I didn't have to sign any `provision' or guarantee I wouldn't disconnect the line until N years have passed. Today, delays of 2.5 months are quoted in some cases, and not the most remote cases. And I am still waiting (after three days) that my phone connection in La Neuveville (at 43 CHF (ISDN) + 7 CHF (advanced service 24h)) gets moved in Cernier ... I would think delays like this are unacceptable. They seem to be due to Swisscom optimizing some costs, maybe in the attempt to raise more money. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] better than visio?
On Tue, Jan 16, 2007 at 12:44:25PM +0100, Philippe Strauss wrote: What do swinogers use to document their network with logical representation (routers, switch, access-servers, firewall... but no physical representation of a particual device like a 7200vxr etc), I'm having a hard time with visio right now :-/ I am afraid I am still using xfig (in the past I have been using tkined/scotty: it allowed detection of networks and documentation). Then you can use a generation script, using transcript, to be able to plot colours on a GUI, to show availability for example, using colours. Without Javascript or complicated technology: just a simple generated image, refreshed either interactively or regularly. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Solutions for emergency connectivity
On Thu, Sep 28, 2006 at 01:39:26PM +0200, Bernard Dugas wrote: Do you have a direct path visibility between the 2 sites ? What length ? Unfortunately, there is no way to do that. Thank you for the people having answered already, I think we are on the path to a solution. I will try to post a summary next week. ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Reading list as RSS feed
On Wed, May 31, 2006 at 09:43:39AM +0200, Olivier Mueller wrote: what about simply replacing the mailing list by a blog? ;-) We could call it swinog 2.0... Then we would have rss as wished by Ruedi, anti-spam and anti-autoresponder captcha protection, etc. What about installing UNIX/procmail ? :) ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] [Fwd: [Full-disclosure] DNS Smurf revisited]
On Fri, May 27, 2005 at 09:31:32PM +0200, Simon Leinen wrote: I can spoof packets from my home broadband connection (and probably the 299'999 other broadband customers of that Swiss ISP can do so as well :-). Hopefully other Swiss ISPs do this better. sunrise freesurf used to allow this also, didn't try for some time. (it even let source address be in the private address space) ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
