On Mon, Sep 03, 2018 at 10:58:49PM +0200, Vincent wrote:
> Hello stefan,
> 
> Hum... it could be similar situations. 
> 
> I've found an article combining the "join" and the trunk: 
> https://dataswamp.org/~solene/2018-08-30-openbsd-trunk.html

For me, it's as simple as this:

==> /etc/hostname.em0 <==
up

==> /etc/hostname.iwn0 <==
join wirelessnet wpakey foo
join anothernet wpakey bar
up

==> /etc/hostname.trunk0 <==
trunkproto failover
trunkport em0
trunkport iwn0
# You could hardcode a mac address here at will
#lladdr aa:bb:cc:dd:ee:ff
dhcp

/Alexander

> 
> I'll do same setup and will see
> 
> Thanks. 
> 
> V.
> 
> 
> 
> 
> 
> 
> 
> On 3 September 2018 20:26:27 CEST, Stefan Sperling <s...@stsp.name> wrote:
> >On Mon, Sep 03, 2018 at 07:46:09PM +0200, vincent delft wrote:
> >> Hello,
> >> 
> >> I'm running -current and enjoy the new "join" feature of hostname.if.
> >> 
> >> Nevertheless, I have sometime issues to have an  internet connection.
> >> 
> >> The context:
> >> I have wifi and cable possibilities to connect the same network.
> >Normaly I
> >> prefer the network connection, so at my desk I plug the cable and use
> >it.
> >> But in some cases, I disconnect my laptop and use the wifi
> >connection.
> >> 
> >> Problem:
> >> The wifi is well connected to my nwid, but the connectivity is not
> >working
> >> (cannot ping my main firewall to connect internet).
> >> I think the problem is linked to wrong arp table (cfr here under)
> >> 
> >> Why the arp entry for my firewall remains "expired" so long (could be
> >more
> >> than 10 minuntes) ?
> >> Why a "doas arp -ad" does not remove this bad fw entry from the table
> >?
> >> What could I do to solve the issue without rebooting the laptop ? (If
> >I
> >> reboot the laptop, this solve the problem).
> >> 
> >> 
> >> 
> >> e5450:~$ arp -a
> >> Host                                 Ethernet Address    Netif Expire
> >> Flags
> >> fw                                   (incomplete)          em0
> >expired
> >> 192.168.3.15                         10:02:b5:83:40:41    iwm0
> >permanent l
> >> 192.168.3.16                         f8:ca:b8:50:84:15     em0
> >permanent l
> >
> >Didn't we already discuss the same question back in July?
> >https://marc.info/?l=openbsd-misc&m=153220020618146&w=2
> >
> >Again, try trunk(4).
> 
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.

Reply via email to