Strange "breach" between WAN & LAN during reboot ??

[GiantJack]

Hi!
I face a very strange behavior I wanted to share.

I have a DSL connexion using a so called "freebox" (a "modem" provided by my ISP).
The service offer some multimedia player and the system is in 2 piece, the so called "server" (include modem) and the "player" connected on TV.

The player use VLAN100 to receive the TV broadcast from the server.
Following a howto, I have created some time ago a VLAN100 bridge from WAN to LAN so that I can see TV with player connected on my LAN.
I have also firewall rules to have this bridge fully opened.
The setup looks like this:



Please forgive me that the picture shows a pfsense device 

The VLAN100 bridge worked some monthes but is now broken, I have no more TV
While trying to figure out how to make the TV work again I notice this:

When I reboot opnsense, I briefly have a working connexion from the modem to the player
On last test, the connexion worked fine during 1min 28sec.

Here is my record today:
I connected to opnsense by SSH, press 6 for reboot:
16:06:00 : I pressed "y" to confirm reboot.
16:06:11 : my freebox player succeed to connect to the freebox server.
16:07:39 : my freebox player lost connection to freebox server.


in the system.log, I found this, but does not help so much:   (for privacy, I replace my ipv4 public address by xx.xx.xx.xx)

Code: [Select]

Apr 14 16:06:08 OPNsense opnsense: /usr/local/etc/rc.linkup: Clearing states for stale wan route on igb1
Apr 14 16:06:09 OPNsense opnsense: /usr/local/etc/rc.filter_configure: Ignore down inet gateways : WAN_FBX_IPV6
Apr 14 16:06:09 OPNsense opnsense: /usr/local/etc/rc.filter_configure: ROUTING: removing /tmp/igb1_defaultgw
Apr 14 16:06:09 OPNsense opnsense: /usr/local/etc/rc.filter_configure: ROUTING: creating /tmp/bge0_defaultgw using '192.168.9.1'
Apr 14 16:06:09 OPNsense opnsense: /usr/local/etc/rc.filter_configure: Ignore down inet6 gateways : WAN_FBX_IPV6
Apr 14 16:06:11 OPNsense kernel: pflog0: promiscuous mode disabled
Apr 14 16:06:11 OPNsense kernel: igb1: link state changed to UP
Apr 14 16:06:11 OPNsense kernel: igb1_vlan100: link state changed to UP
Apr 14 16:06:11 OPNsense kernel: pflog0: promiscuous mode enabled
Apr 14 16:06:12 OPNsense opnsense: /usr/local/etc/rc.linkup: Hotplug event detected for VLAN_100_WAN(opt2) but ignoring since interface is configured with static IP (0.0.0.0 ::)
Apr 14 16:06:13 OPNsense opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet attached event for wan
Apr 14 16:06:13 OPNsense opnsense: /usr/local/etc/rc.linkup: HOTPLUG: Configuring interface wan
Apr 14 16:06:13 OPNsense dhclient: Starting delete_old_states()
Apr 14 16:06:13 OPNsense dhclient: Comparing IPs: Old: xx.xx.xx.xx New: 
Apr 14 16:06:13 OPNsense dhclient: Removing states from old IP 'xx.xx.xx.xx' (new IP '')


(....)


Apr 14 16:06:31 OPNsense opnsense: /usr/local/etc/rc.filter_configure: Ignore down inet gateways : WAN_FBX_IPV6
Apr 14 16:06:31 OPNsense opnsense: /usr/local/etc/rc.filter_configure: ROUTING: keeping current default gateway 'xx.xx.xx.xx'
Apr 14 16:06:31 OPNsense opnsense: /usr/local/etc/rc.filter_configure: Ignore down inet6 gateways : WAN_FBX_IPV6
Apr 14 16:06:33 OPNsense kernel: pflog0: promiscuous mode disabled
Apr 14 16:06:34 OPNsense kernel: pflog0: promiscuous mode enabled
Apr 14 16:06:34 OPNsense opnsense: /usr/local/etc/rc.linkup: Hotplug event detected for VLAN_100_WAN(opt2) but ignoring since interface is configured with static IP (0.0.0.0 ::)
Apr 14 16:06:35 OPNsense opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'igb1_vlan100'
Apr 14 16:06:35 OPNsense opnsense: /usr/local/etc/rc.newwanip: On (IP address: ) (interface: VLAN_100_WAN[opt2]) (real interface: igb1_vlan100).
Apr 14 16:06:35 OPNsense opnsense: /usr/local/etc/rc.newwanip: Failed to detect IP for VLAN_100_WAN[opt2]
Apr 14 16:07:30 OPNsense shutdown: reboot by root: 
Apr 14 16:07:30 OPNsense shutdown: reboot by root: 
Apr 14 16:07:30 OPNsense syslogd: exiting on signal 15
Apr 14 16:11:12 OPNsense syslogd: kernel boot file is /boot/kernel/kernel



The good point is that I am maybe close to find how to make my VLAN work.
The worrying point is that this occur during reboot...like an unexpected hole between WAN & LAN during this sequence.

I hope someone can help a little ?

If some more information or logs are needed, let me know !