Hi list
Can somebody from UPC contact me off-list regarding some suspicious DNS queries (from an UPC-IP) to our authoritative NS?
Thanks in advance.
Kind regards,
Thomas Amgarten
arcade solutions ag
+41 41 417 31 73
Dear SwiNOG supporter,
this is the official Call for Paper email. Please submit your proposal via https://www.swinog.ch/cfp/
The 35th meeting of the Swiss Network Operators Group (SwiNOG) will be held in Berne on top of the Gurten on Thursday May 8th 2019.
Important Dates for https://www.swinog.ch/meetings/swinog35/:
12.02.2019 Call for Papers
tbd Registration opens
28.04.2019 Final publication of agenda
03.05.2019 Registration closes
06.05.2019 Deadline for all slides
08.05.2019 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,
* IPv6
* Open Source tools and interesting Github projects
* 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 to fill in the form at https://www.swinog.ch/cfp/
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
Dear SwiNOGers
I'm new to JunOS. I like this OS so far, but I'm having a hard time,
securing this stuff...
Something's wrong in my JunOS filters... Basically I want to block
everyone from accessing the interface on the router itself, but I want
to allow traffic to pass the interface. Somehow that doesn't work. See
below the (relevant) configuration parts:
interfaces {
xe-0/1/2 {
description blabla;
vlan-tagging;
}
unit 100 {
description Blabla;
vlan-id 100;
family inet {
filter {
input INTERFACE-INCOMING;
}
address 192.168.1.1/24
}
}
}
policy-options {
prefix-list MYINTERFACE {
192.168.1.1/32;
}
}
firewall {
family inet {
filter INTERFACE-INCOMING {
term WAN-ADDRESS {
from {
destination-prefix-list {
MYINTERFACE;
}
}
then {
discard;
}
}
term ALLOW-ALL {
then accept;
}
}
}
}
Anybody with a hint, why this filter doesn't actually block traffic to
192.168.1.1? I can still ping it.
Kind regards,
Viktor
