Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - staticznld

#46
On 21.7 the IPV6 ip address generation did the same.

https://forum.opnsense.org/index.php?topic=26335.0
#47
IGB0: 40:XX:XX:02:cb:17 WAN
IGB1: 40:XX:XX:02:cb:18 LAN currently unused
IGB2: 40:XX:XX:02:cb:19 GUEST
IGB3: 40:XX:XX:02:cb:1a unused
IGB4: 40:XX:XX:02:cb:1b unused
IGB5: 40:XX:XX:02:cb:1c LAN


Last night i moved my LAN from IGB1 to IGB5, the link local address on opnsense ends with CB:1C as expected.
I was also able to ping the link local address from the lan to opnsense.

From my guest network i am unable to ping opnsense through link local ending with CB:19.

Before is switched my LAN to IGB5 i had it on IGB1.
In this scenario is was unable to ping the link local address of opnsense.
The link local address was the same CB:18 address as link local of the PPPoE tunnel!

I am not having any problems with guest interface but found this behaviour strange.
#48
IGB0 sorry :-[

In Interfaces Overview WAN the fe80::4262:31ff:fe02:cb19/64 is used as link local.
#49
pppoe0 runs on top of IGB0!
Thats the strange thing!

So i suspected the link local address would be generated from the MAC address of IGB0 and not IGB2.

The pppoe tunnel is build over Vlan6 on IGB0
#50
Hi,

It looks like the link local address of the WAN PPPoE is the same as the link local address of the LAN interface.

igb2: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=802028<VLAN_MTU,JUMBO_MTU,WOL_MAGIC>
ether 40:62:31:02:cb:19
inet6 fe80::4262:31ff:fe02:cb19%igb2 prefixlen 64 scopeid 0x3
inet6 2a02:a450:839:XXXX:XXXX:XXXX:fe02:cb19 prefixlen 64
inet 172.19.0.1 netmask 0xffffff00 broadcast 172.19.0.255
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

pppoe0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 1500
inet6 fe80::4262:31ff:fe02:cb17%pppoe0 prefixlen 64 scopeid 0xf
inet6 fe80::4262:31ff:fe02:cb19%pppoe0 prefixlen 64 scopeid 0xf
inet 77.XXX.XXX.91 --> 195.190.228.50 netmask 0xffffffff


There are no troubles using IPv6 connectivity on the IGB2 LAN network.
From the LAN side i am unable to ping the link local address of the router!
Running a traceroute from a client to google reports the GUA address as the first hop.

Anyone capable of explaining this behaviour?
#51
Dutch - Nederlands / Re: Hulp gevraagd bij VLAN config
January 07, 2021, 11:36:06 AM
Dag,

Op IGB1 de Vlans 10 en 20 aanmaken.
IGB1 naar switch als Trunk met vlans 10 en 20, van switch 1 een trunk met wederom vlan 10 en 20 naar switch 2.

Dit lijkt mij de makkelijkste oplossing, of er moet nog iets mogelijk zijn met LAGG, om zo IGB 1 en 2 tot 1 interface te maken.

#52
20.7 Legacy Series / Re: IPTV issues on dutch xs4all
September 22, 2020, 02:43:11 PM
Are you running a Unifi controller or Sonos system on the LAN interface?
Had the same problems with KPN, solved it by putting all the STB's in a different vlan.
#53
Under interfaces choose your parent nic without vlan or pppoe and add it.
Enable the device and only set the Mtu to 1508.
#54
No issues here, I had the problem problem before, when setting mtu on the pppoe interface on 1508.
I fixed it by creating another interface on the physical nic and set there the mtu to 1508 to.

https://www.speedguide.net/
Tcp analyzer shows here mtu 1500.
#55
Still isseus here.

I see in the firewall log an message from a link local address to the FF02::2 and it passed.
So I assume the Router solicitation will come to Radvd.

When the link local address of the OPNsense box sends the router advertisements to FF02::2 then the client can configure its ip address.
#56
Dutch - Nederlands / Re: DNS not working on VLAN
August 15, 2020, 11:26:50 AM
Onder services Unbound - general - network interfaces, Vsmarthome ingeschakeld?
En hoe zijn de firewall regels op de LAN interface?
#57
While digging further i also see the same issue.

Router solicitations are sent from a client (VU+ linux stb) but not answered.
When OPNsense sents an Router advertisement the stb is picking up an address and is connected through IPV6.

The packet capture future with Wireshark is great to analyse the problem!

Edit:

When creating a firewall rule to allow icmp6 to any it looks like its working.
Nope not working
#58
Thanks for the info!
Tried setting it up as before and indeed immediately an ipv6 address!

Switched back to default though.
#59
Dutch - Nederlands / Re: KPN glasvezel
August 12, 2020, 12:54:25 PM
Je vlan's 4 en 6 moeten gemaakt worden op de netwerkinterface.
Op vlan 4 (iptv) heb je geen PPPoe nodig.
WAN verbinding PPPoe opzetten over *NIC*_vlan6.

Zie screenshots
#60
Hi,

After installer 20.7 i see some issues regarding IPV6.
After a complete restart of a Windows 10 clients it takes up to 5 a 10 minutes to acquire an IPV6 address.
I am not using DHCPv6 only stateless address configuration.
When restarting the Radvd service in the opnsense interface the windows 10 client immediately picks up an address.



Anyone an idea?