[j-nsp] ndp traffic reflected

2021-06-03 Thread Baldur Norddahl
Hello Take a look at this tcpdump: 16:56:54.663623 e6:5d:37:8f:d8:7b > 33:33:ff:a9:dd:f5, ethertype IPv6 (0x86dd), length 86: 2a00:7660:242a:::1 > ff02::1:ffa9:ddf5: ICMP6, neighbor solicitation, who has fe80::222:7ff:fea9:ddf5, length 32 16:56:54.663804 00:22:07:a9:dd:f5 >

[j-nsp] wrong IP in traceroutes

2021-05-15 Thread Baldur Norddahl
Hello Sometimes we get the wrong IP back in traceroutes. Here is an example: gigabit@kviknet01:~$ mtr -n -r -c3 185.24.168.181 Start: 2021-05-15T14:58:20+ HOST: kviknet01.ring.nlnog.netLoss% Snt Last Avg Best Wrst StDev 1.|-- 212.237.176.65 0.0% 30.2 0.2

Re: [j-nsp] evpn irb default gateway

2021-05-12 Thread Baldur Norddahl
128.0.0.0 resolve no-readvertise I can apparently have a working system by splitting my 0.0.0.0/0 into two halves 0.0.0.0/1 and 128.0.0.0/1. Not very satisfying. There has to be an explanation and fix? Regards, Baldur Den tor. 13. maj 2021 kl. 00.33 skrev Baldur Norddahl : > Hello > >

[j-nsp] evpn irb default gateway

2021-05-12 Thread Baldur Norddahl
Hello My evpn with irb on an acx5448 is going ok except for one very strange problem. The router refuses to use the default route 0.0.0.0/0 when routing traffic via the irb interface. The router itself will ping just fine: baldur@formervangen-core3> ping routing-instance internet 8.8.8.8 PING

Re: [j-nsp] evpn trouble

2021-05-11 Thread Baldur Norddahl
We have two datacenter locations each with a mx204 and a pair of acx5448. The mx204 is used for ip transit, peering and subscriber management. The acx5448 is for connecting servers. Remember the mx204 does not have a lot of ports. We also have an outside plant currently with 26 locations, each

Re: [j-nsp] evpn trouble

2021-05-11 Thread Baldur Norddahl
on/en_US/release-independent/nce/information-products/pathway-pages/nce/EVPN_VxLAN_MAC-VRF.pdf> > > Not sure when MX/ACX will gain this feature though. > > Regards > Roger > > > > On Sat, May 8, 2021 at 12:12 AM Baldur Norddahl wrote: > >> Hello >> >

Re: [j-nsp] evpn trouble

2021-05-07 Thread Baldur Norddahl
Hello I found the answer to this one. On ACX5448 and ACX710 the routing-interface statement does absolutely nothing. Instead you need to use the undocumented l3-interface statement at the same place. On the MX204 platform the l3-interface statement does not exist. I will list the two configs

[j-nsp] evpn trouble

2021-05-07 Thread Baldur Norddahl
Hello I am deploying EVPN and while it works, we are having some issues. Here is the first one: An EVPN instance configured for testing on a MX204 and an ACX5448 both running 21.1R1. The have the same exact configuration except for the IP address of the IRB interface: baldur@formervangen-core3#

Re: [j-nsp] arp bug workaround (mx204)

2021-04-14 Thread Baldur Norddahl
p who-has 185.24.168.2 tell 185.24.168.1 > > krasi@test# run monitor traffic interface demux0.61 no-resolve > . > 13:30:01.788921 Out arp who-has 212.237.105.194 tell 212.237.105.1 > 13:30:15.788642 Out arp who-has 212.237.105.194 tell 212.237.105.1 > > Btw, you

[j-nsp] user defined variables from radius

2020-11-27 Thread Baldur Norddahl
Hello Under "dynamic-profile xxx variables" I can configure user defined variables. I get the impression that somehow these variables can be filled in by radius but how? Radius attributes are to my knowledge predefined. Say I create a variable called "foobar" - what would I do with my freeradius

Re: [j-nsp] arp bug workaround (mx204)

2020-11-09 Thread Baldur Norddahl
Den man. 9. nov. 2020 kl. 22.11 skrev Gert Doering : > Hi, > > On Wed, Nov 04, 2020 at 08:55:11PM +0100, Baldur Norddahl wrote: > > So I am searching for work arounds. For example if I could make an ACL > that > > rewrites the vlans matching an IP address, such that the

[j-nsp] arp bug workaround (mx204)

2020-11-04 Thread Baldur Norddahl
Hello I am trying to work around an arp bug in Junos. The issue is as follows: set interfaces ps201 unit 60 vlan-tags outer 2301 set interfaces ps201 unit 60 vlan-tags inner 1711 set interfaces ps201 unit 60 family inet unnumbered-address lo0.1 set routing-instances internet routing-options

Re: [j-nsp] ACX5448 & ACX710 - Update!

2020-07-30 Thread Baldur Norddahl
On 30.07.2020 10.29, Mark Tinka wrote: The ACX710 was clearly built for one or two mobile network operators. There is no doubt about that. Juniper have been making boxes that support both AC and DC for yonks. Hardened and regular. What's so special about the ACX710? In 2020? To be fair

Re: [j-nsp] ACX5448 & ACX710 - Update!

2020-07-30 Thread Baldur Norddahl
On 29.07.2020 23.18, Mark Tinka wrote: On 29/Jul/20 20:18, Baldur Norddahl wrote: I am also going to get a few ACX5448 for our datacentre locations. I am still considering getting some AC to DC powersupplies for the ACX710 because the cost saving is considerable. It is not like finding AC

Re: [j-nsp] ACX5448 & ACX710 - Update!

2020-07-29 Thread Baldur Norddahl
I am planning to deploy ACX710 with maybe 20 units (which for us is a huge number). We would have ordered DC in any case, so that is a non issue. We will have them at CO buildings were DC is what you get and maybe in the future in road side cabinets, where DC is the easy way to have some battery

[j-nsp] vrrp on a vpls / ps interface

2020-07-24 Thread Baldur Norddahl
Hello I noticed that VRRP on a ps interface does not seem to work. Is there anything I can do about that or is that not supported? This is on MX204. Exact same configuration is working fine on et-0/0/0.16. admin@gc-edge1> show configuration interfaces ps2 anchor-point {     lt-0/0/0; }

[j-nsp] DHCP relay monitoring

2020-07-09 Thread Baldur Norddahl
Hello On one of my MX204 routers the DHCP relay crashes after some running time and the process stops. It is not restarted automatically but will start again with the following command: admin@gc-edge1> restart dhcp-service error: Junos Dynamic Host Configuration Protocol process is not

[j-nsp] what do do with bug reports

2020-06-15 Thread Baldur Norddahl
Hello What am I supposed to do with glaring bugs? Are Juniper interested in knowing those or don't they care? In this case I found out that 19.1 behaves badly if you set [system services subscriber-management overrides interfaces family inet receive-gratuitous-arp]. The setting is supposed

Re: [j-nsp] VPLS q-in-q

2020-05-22 Thread Baldur Norddahl
On 22.05.2020 12.42, Baldur Norddahl wrote: However I also need this on a 'ps' interface to support auto configuration with subscriber management. I tried replicating the configuration from xe-0/1/7.424 on ps1.424 and that configuration is accepted by the router but does nothing. Auto

Re: [j-nsp] VPLS q-in-q

2020-05-22 Thread Baldur Norddahl
Hello I got this working by changing VPLS encapsulation from tagged to raw and this config: baldur@formervangen-edge1# show routing-instances poi-formervangen | display inheritance brief protocols {     vpls {     encapsulation-type ethernet;     ## 'no-control-word' was inherited

Re: [j-nsp] VPLS q-in-q

2020-05-20 Thread Baldur Norddahl
On 20.05.2020 15.04, Mark Tees wrote: Assuming 00:22:07:4d:7b:0d is the MAC behind the Juniper and the PCAP is on NIC of the host connected to the ZTE. At a guess the ZTE doing something different on ingress than what I am thinking here. If you can verify by PCAP on MPLS interface it would

Re: [j-nsp] VPLS q-in-q

2020-05-20 Thread Baldur Norddahl
r tags unless you are wanting to do an operation on them? It sound like your remote side/ZTE does the same as what I have mentioned above. On Wed, 20 May 2020 at 22:13, Baldur Norddahl wrote: Hello I am trying the suggestion received so far and now have this configuration: baldur@formervangen-edge1

Re: [j-nsp] VPLS q-in-q

2020-05-20 Thread Baldur Norddahl
Hello I am trying the suggestion received so far and now have this configuration: baldur@formervangen-edge1# show interfaces xe-0/1/7 flexible-vlan-tagging; native-vlan-id 424; encapsulation flexible-ethernet-services; unit 424 {     encapsulation vlan-vpls;     vlan-tags outer 424;    

[j-nsp] VPLS q-in-q

2020-05-20 Thread Baldur Norddahl
Hello I am trying to enable transport of q-in-q double tagged frames over VPLS through our MX204. The remote end is a switch of another brand (ZTE) and it has some limitations. The outer vlan tag is not transported so I need the MX204 to add it back before processing. However I can not figure

Re: [j-nsp] static arp with unnumbered-address

2020-02-14 Thread Baldur Norddahl
arp no-resolve vpn internet > MAC Address Address Interface Flags > 00:11:11:11:11:11 1.1.1.1 ge-0/0/0.10 permanent > > HTH, > Krasi > > > On Thu, 13 Feb 2020 at 15:09, Baldur Norddahl wrote: > >> Den tor. 13. feb. 2020 kl

Re: [j-nsp] static arp with unnumbered-address

2020-02-13 Thread Baldur Norddahl
unnumbered-address. > And if You export these /32 into Your iBGP, the /32 will be routed to > according to usual iBGP rules (local pref|metric etc). > Thanks > Alex > > -- Original Message -- > From: "Baldur Norddahl" > To: "Juniper List"

Re: [j-nsp] static arp with unnumbered-address

2020-02-13 Thread Baldur Norddahl
ances internet routing-options static route 192.0.2.11/32 > qualified-next-hop et-0/0/0.2766 > set routing-instances internet routing-options static route > 198.51.100.0/24 next-hop 192.0.2.11 resolve > Thanks > Alex > > -- Original Message -- > From: "Baldur Norddahl

[j-nsp] static arp with unnumbered-address

2020-02-12 Thread Baldur Norddahl
Hello How do you program in a static arp entry on an interface that is using family inet unnumbered-address ? Eg.: interface ps1 { unit 2766 { proxy-arp restricted; vlan-tags outer 402 inner 1016; family inet { unnumbered-address lo0.1; } } }

Re: [j-nsp] arp from correct IP address

2020-01-26 Thread Baldur Norddahl
open on this for 8 months. Sent full configs, built a > full lab for them (so they could trigger it remotely), self full PCAPs. > > MX204 + JunOS 18.3R + BNG (DHCP/IPoE naturally) > > Also on MX80 w/same code - so it's the BNG code, not the platform doing it. > > - Ck. >

[j-nsp] arp from correct IP address

2020-01-25 Thread Baldur Norddahl
Hello I have a problem where some customer routers refuse to reply to arp from our juniper mx204. The arp will look like this: 11:57:46.934484 Out arp who-has 185.24.169.60 tell 185.24.168.248 The problem is that this should have been "tell 185.24.169.1" because the client is in the

[j-nsp] Non-dhcp users with subscriber management

2019-07-04 Thread Baldur Norddahl
Hello I am new to Juniper MX. I successfully managed to configure customer vlan with dynamic profiles for dhcp users. I attached the important parts of the configuration at the end of this message. In the real network we are using q-in-q double tagged vlans, but to make thing simple I am

[j-nsp] subscriber management not inserting any routes

2019-05-18 Thread Baldur Norddahl
Hello I am having trouble with subscriber management not inserting any routes. Information is picked up from radius, such as this: baldur@interxion-edge1> show subscribers Interface IP Address/VLAN ID  User Name  LS:RI demux0.3221225472