swinog

swinog@lists.swinog.ch

2944 discussions

Re: [swinog] background migration of swisscom connection from IPv4 native to v6 + DS-Lite
by Scott Weeks 30 Oct '17

30 Oct '17

--- gert(a)space.net wrote: From: Gert Doering <gert(a)space.net> To: Scott Weeks <surfer(a)mauigateway.com> On Sun, Oct 29, 2017 at 02:53:41PM -0700, Scott Weeks wrote: > I was not around for those discussions (and not being a computer > science person, nor wanting to go on this for too long as has been > endlessly done on other lists), but it seems TLV would have allowed > 4 to be a subset of the new space. I never heard that discussed > much and that's what I meant by my comment. The point is: if you introduce a change to the packet format (and TLV would be), you are no longer compatible with IPv4. Which makes the whole "I want this to be compatible so I do not have to change infra or end points" totally moot. Worse, then you have "old IPv4" and "new IPv4" machines who might or might not be able to talk to each other, depending on which IPv4 address the "new IPv4" got (a long one or a short one) - while with IPv6, you have unmodified old IPv4 to ensure compatibility during the transition, and then you turn it off (in 10 years or so). --------------------------------------------------- I guess all ways IETF participants thought of a new address space would not have allowed backwards compatibility with IPv4? Thanks for the explanation. I appreciate it. Hopefully, others here find it interesting, too. scott

1 0

Re: [swinog] background migration of swisscom connection from IPv4 native to v6 + DS-Lite
by Scott Weeks 30 Oct '17

30 Oct '17

--- gert(a)space.net wrote: From: Gert Doering <gert(a)space.net> On Sun, Oct 29, 2017 at 12:57:54PM -0700, Scott Weeks wrote: > Yeah, it's quite unfortunate that IPv4 ran out so suddenly, > barely 15 years after people were told to move towards IPv6. > --------------------------------------- > > > Especially after IETF made it backwards compatible and made > it so easy to switch from 4 to 6... ;-) There's no way to make "something with longer addresses" compatible without IPv4 without changing everything (routers, endpoints) - so, that argument is usually one brought forward as one of a long list of standard excuses to avoid deploying IPv6, while at the same time blaming everyone else for the problems with IPv4. ------------------------------------------- Note the smiley face above. This one, too... :) I was not around for those discussions (and not being a computer science person, nor wanting to go on this for too long as has been endlessly done on other lists), but it seems TLV would have allowed 4 to be a subset of the new space. I never heard that discussed much and that's what I meant by my comment. scott

2 1

Re: [swinog] background migration of swisscom connection from IPv4 native to v6 + DS-Lite
by Scott Weeks 29 Oct '17

29 Oct '17

--- gert(a)space.net wrote: From: Gert Doering <gert(a)space.net> Yeah, it's quite unfortunate that IPv4 ran out so suddenly, barely 15 years after people were told to move towards IPv6. --------------------------------------- Especially after IETF made it backwards compatible and made it so easy to switch from 4 to 6... ;-) scott _______________________________________________ swinog mailing list swinog(a)lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog

2 1

background migration of swisscom connection from IPv4 native to v6 + DS-Lite
by WolfSec-Support 29 Oct '17

29 Oct '17

Hello, could be someone from swisscom so kind and contact me offlist via email please. our customer has a swisscom dsl connection and last week they changed these to v6. he already tried 3 times via swisscom helpdesk without success. the first level seems to have no idea about ds lite and v6... ;-/ we want to go back to v4 native. in customer center we have deactivated v6 - but it is still online via v6 and ds-lite we did all what was explained: - switchoff modem for an hour - reboot 3 times router etc effectively now the vpn is for sure not working via ds lite and carrier grade NAT.... thanks in advance Stephan Besten Dank. Freundliche Grüsse, WolfSec-Support WolfSec Postanschrift: Swiss Post Box: 104213 Zürcherstrasse 161 CH-8010 Zürich http://www.wolfsec.ch

3 7

Only four weeks until DENOG9 in Darmstadt, Germany
by Arnold Nipper 27 Oct '17

27 Oct '17

Dear SwiNOG The ninth meeting of the German Network Operators Group (DENOG) will be held in Darmstadt, Germany on the 23rd and 24th of November 2017. Again these are two days packed with presentations, lots of room to socialise and networking accompanied by an exhibition where you can talk to vendors. There are still a few places left. If you are interested please register at http://www.denog.de/meetings/denog9/registration.php Best regards Arnold Nipper -- Arnold Nipper email: arnold(a)nipper.de mobile: +49 172 2650958

1 0

Security Chat 4.0 - November 16 - Sign Up Now!
by Raffael Marty 21 Oct '17

21 Oct '17

This is already the fourth iteration of our Security Chat series. We are gathering for an evening of short security-related presentations and networking with peers in the security industry. Security Chat 4.0 Thursday, November 16th, 18.00 - 20.00 AdNovum Informatik AG (Headquarters), 22 Röntgenstrasse, 8005 Zürich (free) singup at: http://bit.ly/security40 If you are interested in giving a short presentation, please indicate on the signup or email me directly. Any topic welcome: Projects you are working on, research you have conducted, questions you would like to get answers from the attendees, an embarrassing security story; the stage is yours. We have a sponsor who offered to provide us with some small libations for after the event. And keep the rest of your evening open; I am sure there'll be a group that is going to get some dinner afterwards. Hope to see you at the event! -raffy PS: Tell your friends!

1 0

GSM AT command to set 'Validity Period'?
by Benoit Panizzon 16 Oct '17

16 Oct '17

Dear Swinogers We use smsd to send our nagios alarms via a GSM usb stick. I'm looking for some advice after I was not able to find a working solution. The mobile operator we use has a somewhat short queue to accept SMS and when a recipient is not getting the SMS (mobile off during vacation or whatever) this sms blocks the queue until it expires. If the queue is full, no more sms are being accepted. The SMS are being sent with a default validity period of 7 days. So they expire from the queue after this period. Well, the easy solution would be to sent the period to a couple of hours. No need for techs to get old SMS. What I did is: AT+CSMP=17,143,0,0 // Set Validity Period to 12 hours. AT+CSAS // Save settings to SIM If I query the settings: AT+CSMP? I see these values are set. But after contacting the mobile operator to check if the VP is correct, he tells me we still send them with default 7 days. Does anyone have a hint on how to set the VP correctly via AT commands? Kind regards -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 1

##### SwiNOG #32 - Please Submit your Lightning talks #####
by Simon Ryf 14 Oct '17

14 Oct '17

Hey fellows, We’re still a bit short of presentations for the 9th next month. (Yes – I’m the one to blame ;) Therefore: Pretty please – submit your lightning talks (or full-blown presentations). Anything starting from 5 minutes is a perfect match for SwiNOG. Don’t hesitate to ask me to narrow down together a topic or get a question answered. Have a good weekend Br Simon From: Simon Ryf <simon(a)swinog.org> Date: Friday, 29 September 2017 at 12:19 To: "swinog(a)swinog.ch" <swinog(a)swinog.ch> Subject: ##### SwiNOG #32 - Call for Papers ##### Dear SwiNOG supporter, this is the official Call for Paper email. Please send your proposal to swinog-core (at) swinog.ch or directly to me. The 32nd meeting of the Swiss Network Operators Group (SwiNOG) will be held in Berne on top of the Gurten on Thursday November 09 2017. Important Dates for SwiNOG#31 29.09.2017 Call for Papers 03.10.2017 Registration opens 22.10.2017 Call for Papers closing 22.10.2017 Final publication of agenda 03.11.2017 Registration closes 05.11.2017 Deadline for all slides 09.11.2017 Meeting day Topics for Presentations/Talks The number and length of presentations per session is not fixed, although due to time constraints we would prefer the length of the presentations to be between 5 to 45 minutes. Here is a non-exhaustive list of typical SwiNOG meeting topics: - Security - DDOS Mitigation - AntiSpam - IPv6 - Open Source tools - International view of the internet (incidents, outages, measurements) - Routing - Server applications (DNS, Web, etc.) - Legal issues (B‹PF, etc.) - Telecommunication politics (Net Neutrality, Incumbent monopoly, etc.) -> PLEASE feel free to talk to us about any kind of topic and collaboration!!! You can always start a discussion on the list - I'm sure people join in. Language of Slides and Talks The whole day will be held in English, therefore we kindly ask you to produce your presentation in English. Submission Guidelines All submissions must have a strong technical bias and must not be solely promotional for your employer. Please remember that your presentations should be suitable for a target audience of technicians from varied backgrounds, working for companies whose sizes may vary considerably. To submit a proposal for a presentation, we request that you provide the following information to <swinog-core at swinog.ch>: * the name of the presenter (and if applicable your affiliation) * a working email address * the name and number of the topic which will contain the presentation * the title of the presentation * its expected length (in minutes) * a short abstract of the presentation (so we know what it is about) We also welcome suggestions for specific presentations which you feel would be valuable to the SwiNOG community. Please be aware that your presentation will be published on the SwiNOG website after the event. We can publish modified slides if requested - it might be that some confidential data will be presented by you which are not intended for publication on the internet. Greetings, Simon Ryf SwiNOG Core Team General Information (SwiNOG Community) The Swiss Network Operators Group (SwiNOG) is an informal group of people who are concerned with engineering and operation of the Swiss Internet. SwiNOG exists to enhance the quality of Internet services available in Switzerland. It does this by fostering the free exchange of technical ideas and information between different companies and organisations. SwiNOG is a community for professionals who are operating, designing or researching the Internet. It provides a technical forum where those working on, with and for the Internet can come together to solve problems with every aspect of their (net)work. The meeting is designed to provide an opportunity for the exchange of information among network operators, engineers, researchers and other professionals close to the network community. More information about SwiNOG can be found at http://www.swinog.ch/, Facebook, Xing, Information about the meeting will be published at http://www.swinog.ch/meetings/swinog31/ General Information (SwiNOG Organisation) The SwiNOG Organisation Association is a non-profit association under article 60 and further of the swiss civil law. It manages the SwiNOG community ressources (domain, web, mailing-lists, etc..) and organises SwiNOG meetings. Contact: SwiNOG Organisation 8000 Zurich Switzerland

1 0

Selling Cisco 7206 VXR NPEG1
by Hofer Ruedi 11 Oct '17

11 Oct '17

Dear all I am selling 3 x Cisco 7206 VXR / NPEG1 / dual power supply ... aka the internet workhorse;) They were bought in 2003 and used until recently. They are in good condition and clean. See tech spec below for details. Price: CHF300/piece (is about reasonable, right?) - No guarantee - No Lasers - No Cables - No Shipping, pickup at our premises only, see address below - Cash-only payment First come first served. Please contact me offlist if interestet. mailto:ruedi.hofer@ewb.ch Freundliche Grüsse Ruedi Hofer Leiter Telecom Center Energie Wasser Bern Monbijoustrasse 11, Postfach, 3001 Bern ruedi.hofer(a)ewb.ch, ewb.ch<http://www.ewb.ch/> Summary : - Cisco 7206VXR, 6-slot chassis - NPE-G1 / 512MB RAM / 64MB Flash Card - 3x1GB Interface Web Refrence : https://www.cisco.com/c/en/us/td/docs/routers/7200/install_and_upgrade/netw… ####################################### RAW DATA ################################################## ewb-ch-emc-brn01-rm-01#sh inventory raw NAME: "Chassis", DESCR: "Cisco 7206VXR, 6-slot chassis" PID: CISCO7206VXR , VID: , SN: 30827013 NAME: "I/O and CPU Slot 0", DESCR: "I/O and Processor Slot Container" PID: , VID: , SN: NAME: "NPE-G1 0", DESCR: "Cisco 7200 Series Network Processing Engine NPE-G1" PID: NPE-G1 , VID: , SN: 31248843 NAME: "GBIC Port Container 0/1", DESCR: "GBIC Port Container" PID: , VID: , SN: NAME: "GigabitEthernet0/1", DESCR: "BCM1250 Internal MAC" PID: , VID: , SN: NAME: "GBIC Port Container 0/2", DESCR: "GBIC Port Container" PID: , VID: , SN: NAME: "GigabitEthernet0/2", DESCR: "BCM1250 Internal MAC" PID: , VID: , SN: NAME: "GBIC Port Container 0/3", DESCR: "GBIC Port Container" PID: , VID: , SN: NAME: "GigabitEthernet0/3", DESCR: "BCM1250 Internal MAC" PID: , VID: , SN: NAME: "Flash Card Slot Container CPU", DESCR: "Flash Card Slot Container CPU" PID: , VID: , SN: NAME: "disk2", DESCR: "64MB Compact Flash Disk for NPE-G1" PID: MEM-NPE-G1-FLD64 , VID: , SN: NAME: "NPE Inlet Temperature 0", DESCR: "NPE Inlet Temperature Sensor" PID: , VID: , SN: NAME: "NPE Outlet Temperature 0", DESCR: "NPE Outlet Temperature Sensor" PID: , VID: , SN: NAME: "+3.45 V Voltage 0", DESCR: "+3.45 V Voltage Sensor" PID: , VID: , SN: NAME: "+5.15 V Voltage 0", DESCR: "+5.15 V Voltage Sensor" PID: , VID: , SN: NAME: "+12.15 V Voltage 0", DESCR: "+12.15 V Voltage Sensor" PID: , VID: , SN: NAME: "-11.95 V Voltage 0", DESCR: "-11.95 V Voltage Sensor" PID: , VID: , SN: NAME: "Gi0/1", DESCR: "BCM1250 Internal MAC RJ45" PID: , VID: , SN: NAME: "Gi0/2", DESCR: "BCM1250 Internal MAC RJ45" PID: , VID: , SN: NAME: "Gi0/3", DESCR: "BCM1250 Internal MAC RJ45" PID: , VID: , SN: NAME: "PA Slot 1", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 2", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 3", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 4", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 5", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PA Slot 6", DESCR: "PA Slot Container" PID: , VID: , SN: NAME: "PEM 0", DESCR: "Power Supply Container" PID: , VID: , SN: NAME: "Power Supply 0", DESCR: "Cisco 7200 AC Power Supply" PID: PWR-7200-AC , VID: , SN: NAME: "PEM 1", DESCR: "Power Supply Container" PID: , VID: , SN: NAME: "Power Supply 1", DESCR: "Cisco 7200 AC Power Supply" PID: PWR-7200-AC , VID: , SN: ewb-ch-emc-brn01-rm-01#sh ver ewb-ch-emc-brn01-rm-01#sh version Cisco IOS Software, 7200 Software (C7200-JK9O3S-M), Version 12.4(8c), RELEASE SOFTWARE (fc3) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2006 by Cisco Systems, Inc. Compiled Tue 12-Dec-06 03:30 by prod_rel_team ROM: System Bootstrap, Version 12.2(8r)B, RELEASE SOFTWARE (fc1) BOOTLDR: 7200 Software (C7200-KBOOT-M), Version 12.2(15)B, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1) System image file is "disk2:c7200-jk9o3s-mz.124-8c.bin" Last reload reason: Reload Command This product contains cryptographic features and is subject to United States and local country laws governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors and users are responsible for compliance with U.S. and local country laws. By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local laws, return this product immediately. A summary of U.S. laws governing Cisco cryptographic products may be found at: http://www.cisco.com/wwl/export/crypto/tool/stqrg.html If you require further assistance please contact us by sending email to export(a)cisco.com<mailto:export@cisco.com>. Cisco 7206VXR (NPE-G1) processor (revision A) with 491520K/32768K bytes of memory. Processor board ID 30827013 SB-1 CPU at 700MHz, Implementation 1025, Rev 0.2, 512KB L2 Cache 6 slot VXR midplane, Version 2.7 Last reset from power-on PCI bus mb1 (Slots 1, 3 and 5) has a capacity of 600 bandwidth points. Current configuration on bus mb1 has a total of 0 bandwidth points. This configuration is within the PCI bus capacity and is supported. PCI bus mb2 (Slots 2, 4 and 6) has a capacity of 600 bandwidth points. Current configuration on bus mb2 has a total of 0 bandwidth points. This configuration is within the PCI bus capacity and is supported. Please refer to the following document "Cisco 7200 Series Port Adaptor Hardware Configuration Guidelines" on Cisco.com <http://www.cisco.com> for c7200 bandwidth points oversubscription and usage guidelines. 3 Gigabit Ethernet interfaces 509K bytes of NVRAM. 62976K bytes of ATA PCMCIA card at slot 2 (Sector size 512 bytes). 16384K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x2102

1 0

Selling Cisco 7206 VXR NPEG1
by Hofer Ruedi 10 Oct '17

10 Oct '17

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

swinog