Re: 6.2 beta snapshot , dhclient and bridge
On Tue, Sep 12, 2017 at 5:11 PM, sven falempin wrote: > Following beta snaps > > same setup ( one machine is a bridge for the next ) still cannot recover > DHCP OFFER back through the bridge > > ( updated the bridge device) > > # uname -a > OpenBSD bridgeandstuff.my.domain 6.2 GENERIC.MP#63 amd64 > > # dhclient em5 > DHCPDISCOVER on em5 - interval 1 > DHCPDISCOVER on em5 - interval 1 > DHCPDISCOVER on em5 - interval 2 > DHCPDISCOVER on em5 - interval 4 > DHCPDISCOVER on em5 - interval 10 > DHCPDISCOVER on em5 - interval 10 > ^C > # ifconfig em5 > em5: flags=8843 mtu 1500 > lladdr 00:30:18:13:41:b0 > index 6 priority 0 llprio 3 > groups: egress > media: Ethernet autoselect (1000baseSX full-duplex) > status: active > inet 172.16.1.51 netmask 0x broadcast 172.16.255.255 > # ping 172.16.1.1 > PING 172.16.1.1 (172.16.1.1): 56 data bytes > 64 bytes from 172.16.1.1: icmp_seq=0 ttl=255 time=0.504 ms > > Now updating client > ( for trunk test on last version , currently the more the interface the > less the speed :s ) > > Confirmed last snap both device (Device one) em0 <---> em5 ( Device Two <--> bridge <--> ) em0 <---> the interface em0 on the device 'two' must be down the up for the device 'one' to receive the OFFER one#reboot two#reboot one#dhclient em5 FAILED two#ifconfig em0 down two#ifconfig em0 up one#dhclient em5 SUCCESS -- - Knowing is not enough; we must apply. Willing is not enough; we must do
Re: 6.2 beta snapshot , dhclient and bridge
Following beta snaps same setup ( one machine is a bridge for the next ) still cannot recover DHCP OFFER back through the bridge ( updated the bridge device) # uname -a OpenBSD bridgeandstuff.my.domain 6.2 GENERIC.MP#63 amd64 # dhclient em5 DHCPDISCOVER on em5 - interval 1 DHCPDISCOVER on em5 - interval 1 DHCPDISCOVER on em5 - interval 2 DHCPDISCOVER on em5 - interval 4 DHCPDISCOVER on em5 - interval 10 DHCPDISCOVER on em5 - interval 10 ^C # ifconfig em5 em5: flags=8843 mtu 1500 lladdr 00:30:18:13:41:b0 index 6 priority 0 llprio 3 groups: egress media: Ethernet autoselect (1000baseSX full-duplex) status: active inet 172.16.1.51 netmask 0x broadcast 172.16.255.255 # ping 172.16.1.1 PING 172.16.1.1 (172.16.1.1): 56 data bytes 64 bytes from 172.16.1.1: icmp_seq=0 ttl=255 time=0.504 ms Now updating client ( for trunk test on last version , currently the more the interface the less the speed :s ) On Fri, Sep 1, 2017 at 2:42 PM, sven falempin wrote: > Unexpected behavior : > > GENERIC.MP#63 6.2 AMD64 > > (Device one) em0 <---> em5 ( Device Two <--> bridge <--> ) em0 <---> > DHCP SERVER > > two#: dhclient em0 > two#: ifconfig bridge0 create > two#: ifconfig bridge0 add em5 > two#: ifconfig bridge0 add em0 > two#: ifconfig bridge0 up > > one#: dhclient em0 > FAILED (paquet does not come back thourgh bridge ) > > two#: ifconfig em0 down > two#: ifconfig vether0 create > two#: dhclient vether0 > FAILED > > two#: ifconfig em0 up > two#: dhclient vether0 > FAILED > > two#: ifconfig em0 down > two#: ifconfig em0 down > two#: dhclient vether0 > success > > BUT IP on em0 and vether1 > > one# dhclient em0 > SUCCESS > > -- > -- > > - > Knowing is not enough; we must apply. Willing is not enough; we must do > -- -- - Knowing is not enough; we must apply. Willing is not enough; we must do
6.2 beta snapshot , dhclient and bridge
Unexpected behavior : GENERIC.MP#63 6.2 AMD64 (Device one) em0 <---> em5 ( Device Two <--> bridge <--> ) em0 <---> DHCP SERVER two#: dhclient em0 two#: ifconfig bridge0 create two#: ifconfig bridge0 add em5 two#: ifconfig bridge0 add em0 two#: ifconfig bridge0 up one#: dhclient em0 FAILED (paquet does not come back thourgh bridge ) two#: ifconfig em0 down two#: ifconfig vether0 create two#: dhclient vether0 FAILED two#: ifconfig em0 up two#: dhclient vether0 FAILED two#: ifconfig em0 down two#: ifconfig em0 down two#: dhclient vether0 success BUT IP on em0 and vether1 one# dhclient em0 SUCCESS -- -- - Knowing is not enough; we must apply. Willing is not enough; we must do
