A lot of 'ifa_ifwithnet failed' messages on CURRENT
It prints these messages when WiFi is used. What is the reason? Thanks, Yuri ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: GRE/gif/netgraph tunnel speed on 10Gbit channel
Most likely threading only part of problem with iperf3. As I say before - I'm check iperf3 in paralel by running multiple instanse on diferent's ports Speed is always same. But maybe 2-3 instance to few for noticible result's. For me most confusion was speed aroud 10Gbit on pure link showed by both iperf and iperf3 ... Any way. With enabled pf (set skip on gre0 in config) in kernel I get around 3gbit's and around 4.4gbit's without. Also I'm tested diferent mtu on interface (eg 9000 and so on) no speed improvement at all Now question is - is it highgest speed of tunnel that we can expect from GRE or there is some tuning capabilitis for speed up it? Muenz, Michael wrote: MM> Am 29.05.2018 um 16:02 schrieb Rodney W. Grimes: MM> >> Am 29.05.2018 um 13:33 schrieb Vitalij Satanivskij: MM> >> MM> >> MM> Can you try MTU 1400 on GRE0 and MSS of 1300 just for testing? MM> >> MM> With this values I get 4600Mbit sending and 1400Mbit receiving with MM> >> MM> iperf and 10 parallel streams. MM> >> MM> MM> >> MM> >> UUUPSS looks like i have problem with metodology MM> >> MM> >> I'm use iperf3 and even with -P10 or run's in parallel (on diferents ports) it show summary of +-2gbits max MM> > Iperf3 is known not to do Parallel well: MM> > -P, --parallel n MM> >number of parallel client streams to run. Note that iperf3 is MM> >single threaded, so if you are CPU bound, this will not yield MM> >higher throughput. MM> > MM> > I suggest using iperf for -P tests that cause the single thread of MM> > iperf3 to become CPU bound. MM> MM> Oh, this was new to me. With iperf I got consistent 4,6Gbit in both MM> directions. MM> ___ MM> freebsd-net@freebsd.org mailing list MM> https://lists.freebsd.org/mailman/listinfo/freebsd-net MM> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: GRE/gif/netgraph tunnel speed on 10Gbit channel
Am 30.05.2018 um 10:43 schrieb Vitalij Satanivskij: Most likely threading only part of problem with iperf3. As I say before - I'm check iperf3 in paralel by running multiple instanse on diferent's ports Speed is always same. But maybe 2-3 instance to few for noticible result's. For me most confusion was speed aroud 10Gbit on pure link showed by both iperf and iperf3 ... Any way. With enabled pf (set skip on gre0 in config) in kernel I get around 3gbit's and around 4.4gbit's without. Also I'm tested diferent mtu on interface (eg 9000 and so on) no speed improvement at all Now question is - is it highgest speed of tunnel that we can expect from GRE or there is some tuning capabilitis for speed up it? In my Lab FW1 is only Xeon D with 95% CPU while testing and FW2 Xeon E is at 20% CPU. I cannot replace the Xeon D for the next 3 weeks so there could be more perhaps. Michael ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
I have 10.241.0.0-15/16 bound to lo1 for jails, and I just realised it doesn't
work anymore. Boxes at $DAYJOB use the same config and work just fine on
11.1R/amd64, otherwise I'd be fired this used to work ~ 1 month ago, both
on my desktop, and my laptop, and now doesn't.
Have I mis-configured something blindingly obvious here before I embark on a
lengthy bisect?
# grep -v \# /etc/rc.conf , elided
hostname=akai
kld_list="${kld_list} if_iwm if_axge if_ure if_ue"
ifconfig_ue0=DHCP
ifconfig_ue0_ipv6="inet6 accept_rtadv"
wlans_iwm0="wlan0"
ifconfig_wlan0="WPA DHCP"
ifconfig_wlan0_ipv6="inet6 accept_rtadv"
create_args_wlan0="country AT regdomain ETSI"
cloned_interfaces="${cloned_interfaces} lo1"
ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
ip6addrctl_policy="ipv4_prefer"
# netstat -4rn
Internet:
DestinationGatewayFlags Netif Expire
default172.16.2.1 UGS ue0
10.241.0.0 link#4 UH lo1
10.241.0.1 link#4 UH lo1
10.241.0.2 link#4 UH lo1
10.241.0.3 link#4 UH lo1
10.241.0.4 link#4 UH lo1
10.241.0.5 link#4 UH lo1
10.241.0.6 link#4 UH lo1
10.241.0.7 link#4 UH lo1
10.241.0.8 link#4 UH lo1
10.241.0.9 link#4 UH lo1
10.241.0.10link#4 UH lo1
10.241.0.11link#4 UH lo1
10.241.0.12link#4 UH lo1
10.241.0.13link#4 UH lo1
10.241.0.14link#4 UH lo1
10.241.0.15link#4 UH lo1
127.0.0.1 link#1 UH lo0
172.16.2.0/24 link#2 U ue0
172.16.2.92link#3 UHS lo0
172.16.2.93link#2 UHS lo0
# ifconfig
lo0: flags=8049 metric 0 mtu 16384
options=680003
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff00
nd6 options=21
groups: lo
ue0: flags=8843 metric 0 mtu 1500
options=8000b
ether 74:da:38:d8:fe:a7
inet6 fe80::76da:38ff:fed8:fea7%ue0 prefixlen 64 scopeid 0x2
inet 172.16.2.93 netmask 0xff00 broadcast 172.16.2.255
nd6 options=23
media: Ethernet autoselect (1000baseT )
status: active
wlan0: flags=8943 metric 0 mtu
1500
ether 00:28:f8:d0:91:52
inet6 fe80::228:f8ff:fed0:9152%wlan0 prefixlen 64 scopeid 0x3
inet 172.16.2.92 netmask 0xff00 broadcast 172.16.2.255
nd6 options=23
media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
status: associated
ssid skunkwerks channel 6 (2437 MHz 11g) bssid 80:2a:a8:5a:bd:3f
regdomain ETSI country AT authmode WPA2/802.11i privacy ON
deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60
protmode CTS wme roaming MANUAL
groups: wlan
lo1: flags=8049 metric 0 mtu 16384
options=680003
inet 10.241.0.0 netmask 0x
inet 10.241.0.1 netmask 0x
inet 10.241.0.2 netmask 0x
inet 10.241.0.3 netmask 0x
inet 10.241.0.4 netmask 0x
inet 10.241.0.5 netmask 0x
inet 10.241.0.6 netmask 0x
inet 10.241.0.7 netmask 0x
inet 10.241.0.8 netmask 0x
inet 10.241.0.9 netmask 0x
inet 10.241.0.10 netmask 0x
inet 10.241.0.11 netmask 0x
inet 10.241.0.12 netmask 0x
inet 10.241.0.13 netmask 0x
inet 10.241.0.14 netmask 0x
inet 10.241.0.15 netmask 0x
nd6 options=29
groups: lo
bridge0: flags=8843 metric 0 mtu 1500
description: vm-public
ether 02:63:d4:40:fe:00
nd6 options=1
groups: bridge
id 00:00:00:00:00:00 priority 0 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 0 ifcost 0 port 0
member: wlan0 flags=143
ifmaxaddr 0 port 3 priority 128 path cost 370370
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
On Wed, May 30, 2018 at 3:40 PM, Dave Cottlehuber wrote:
> I have 10.241.0.0-15/16 bound to lo1 for jails, and I just realised it
> doesn't work anymore. Boxes at $DAYJOB use the same config and work just
> fine on 11.1R/amd64, otherwise I'd be fired this used to work ~ 1 month
> ago, both on my desktop, and my laptop, and now doesn't.
>
> Have I mis-configured something blindingly obvious here before I embark
> on a lengthy bisect?
>
> # grep -v \# /etc/rc.conf , elided
> hostname=akai
> kld_list="${kld_list} if_iwm if_axge if_ure if_ue"
> ifconfig_ue0=DHCP
> ifconfig_ue0_ipv6="inet6 accept_rtadv"
> wlans_iwm0="wlan0"
> ifconfig_wlan0="WPA DHCP"
> ifconfig_wlan0_ipv6="inet6 accept_rtadv"
> create_args_wlan0="country AT regdomain ETSI"
> cloned_interfaces="${cloned_interfaces} lo1"
> ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
> ip6addrctl_policy="ipv4_prefer"
>
> # netstat -4rn
> Internet:
> DestinationGatewayFlags Netif Expire
> default172.16.2.1 UGS ue0
> 10.241.0.0 link#4 UH lo1
> 10.241.0.1 link#4 UH lo1
> 10.241.0.2 link#4 UH lo1
> 10.241.0.3 link#4 UH lo1
> 10.241.0.4 link#4 UH lo1
> 10.241.0.5 link#4 UH lo1
> 10.241.0.6 link#4 UH lo1
> 10.241.0.7 link#4 UH lo1
> 10.241.0.8 link#4 UH lo1
> 10.241.0.9 link#4 UH lo1
> 10.241.0.10link#4 UH lo1
> 10.241.0.11link#4 UH lo1
> 10.241.0.12link#4 UH lo1
> 10.241.0.13link#4 UH lo1
> 10.241.0.14link#4 UH lo1
> 10.241.0.15link#4 UH lo1
> 127.0.0.1 link#1 UH lo0
> 172.16.2.0/24 link#2 U ue0
> 172.16.2.92link#3 UHS lo0
> 172.16.2.93link#2 UHS lo0
>
> # ifconfig
> lo0: flags=8049 metric 0 mtu 16384
> options=680003
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
> inet 127.0.0.1 netmask 0xff00
> nd6 options=21
> groups: lo
> ue0: flags=8843 metric 0 mtu 1500
> options=8000b
> ether 74:da:38:d8:fe:a7
> inet6 fe80::76da:38ff:fed8:fea7%ue0 prefixlen 64 scopeid 0x2
> inet 172.16.2.93 netmask 0xff00 broadcast 172.16.2.255
> nd6 options=23
> media: Ethernet autoselect (1000baseT )
> status: active
> wlan0: flags=8943 metric
> 0 mtu 1500
> ether 00:28:f8:d0:91:52
> inet6 fe80::228:f8ff:fed0:9152%wlan0 prefixlen 64 scopeid 0x3
> inet 172.16.2.92 netmask 0xff00 broadcast 172.16.2.255
> nd6 options=23
> media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
> status: associated
> ssid skunkwerks channel 6 (2437 MHz 11g) bssid 80:2a:a8:5a:bd:3f
> regdomain ETSI country AT authmode WPA2/802.11i privacy ON
> deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60
> protmode CTS wme roaming MANUAL
> groups: wlan
> lo1: flags=8049 metric 0 mtu 16384
> options=680003
> inet 10.241.0.0 netmask 0x
> inet 10.241.0.1 netmask 0x
> inet 10.241.0.2 netmask 0x
> inet 10.241.0.3 netmask 0x
> inet 10.241.0.4 netmask 0x
> inet 10.241.0.5 netmask 0x
> inet 10.241.0.6 netmask 0x
> inet 10.241.0.7 netmask 0x
> inet 10.241.0.8 netmask 0x
> inet 10.241.0.9 netmask 0x
> inet 10.241.0.10 netmask 0x
> inet 10.241.0.11 netmask 0x
> inet 10.241.0.12 netmask 0x
> inet 10.241.0.13 netmask 0x
> inet 10.241.0.14 netmask 0x
> inet 10.241.0.15 netmask 0x
> nd6 options=29
> groups: lo
> bridge0: flags=8843 metric 0 mtu
> 1500
> description: vm-public
> ether 02:63:d4:40:fe:00
> nd6 options=1
> groups: bridge
> id 00:00:00:00:00:00 priority 0 hellotime 2 fwddelay 15
> maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
> root id 00:00:00:00:00:00 priority 0 ifcost 0 port 0
> member: wlan0 flags=143
> ifmaxaddr 0 port 3 priority 128 path cost 370370
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
>
Hello,
could you specify what exactly isn't working? How does the bridge fit into
this setup?
Best regards
Andreas
__
Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
On Wed, May 30, 2018 at 03:59:12PM +0200, Andreas Nilsson wrote:
> On Wed, May 30, 2018 at 3:40 PM, Dave Cottlehuber wrote:
>
> > I have 10.241.0.0-15/16 bound to lo1 for jails, and I just realised it
> > doesn't work anymore. Boxes at $DAYJOB use the same config and work just
> > fine on 11.1R/amd64, otherwise I'd be fired this used to work ~ 1 month
> > ago, both on my desktop, and my laptop, and now doesn't.
> >
> > Have I mis-configured something blindingly obvious here before I embark
> > on a lengthy bisect?
> >
> > # grep -v \# /etc/rc.conf , elided
> > hostname=akai
> > kld_list="${kld_list} if_iwm if_axge if_ure if_ue"
> > ifconfig_ue0=DHCP
> > ifconfig_ue0_ipv6="inet6 accept_rtadv"
> > wlans_iwm0="wlan0"
> > ifconfig_wlan0="WPA DHCP"
> > ifconfig_wlan0_ipv6="inet6 accept_rtadv"
> > create_args_wlan0="country AT regdomain ETSI"
> > cloned_interfaces="${cloned_interfaces} lo1"
> > ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
> > ip6addrctl_policy="ipv4_prefer"
> >
> > # netstat -4rn
> > Internet:
> > DestinationGatewayFlags Netif Expire
> > default172.16.2.1 UGS ue0
> > 10.241.0.0 link#4 UH lo1
> > 10.241.0.1 link#4 UH lo1
> > 10.241.0.2 link#4 UH lo1
> > 10.241.0.3 link#4 UH lo1
> > 10.241.0.4 link#4 UH lo1
> > 10.241.0.5 link#4 UH lo1
> > 10.241.0.6 link#4 UH lo1
> > 10.241.0.7 link#4 UH lo1
> > 10.241.0.8 link#4 UH lo1
> > 10.241.0.9 link#4 UH lo1
> > 10.241.0.10link#4 UH lo1
> > 10.241.0.11link#4 UH lo1
> > 10.241.0.12link#4 UH lo1
> > 10.241.0.13link#4 UH lo1
> > 10.241.0.14link#4 UH lo1
> > 10.241.0.15link#4 UH lo1
> > 127.0.0.1 link#1 UH lo0
> > 172.16.2.0/24 link#2 U ue0
> > 172.16.2.92link#3 UHS lo0
> > 172.16.2.93link#2 UHS lo0
> >
> > # ifconfig
> > lo0: flags=8049 metric 0 mtu 16384
> > options=680003
> > inet6 ::1 prefixlen 128
> > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
> > inet 127.0.0.1 netmask 0xff00
> > nd6 options=21
> > groups: lo
> > ue0: flags=8843 metric 0 mtu 1500
> > options=8000b
> > ether 74:da:38:d8:fe:a7
> > inet6 fe80::76da:38ff:fed8:fea7%ue0 prefixlen 64 scopeid 0x2
> > inet 172.16.2.93 netmask 0xff00 broadcast 172.16.2.255
> > nd6 options=23
> > media: Ethernet autoselect (1000baseT )
> > status: active
> > wlan0: flags=8943 metric
> > 0 mtu 1500
> > ether 00:28:f8:d0:91:52
> > inet6 fe80::228:f8ff:fed0:9152%wlan0 prefixlen 64 scopeid 0x3
> > inet 172.16.2.92 netmask 0xff00 broadcast 172.16.2.255
> > nd6 options=23
> > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
> > status: associated
> > ssid skunkwerks channel 6 (2437 MHz 11g) bssid 80:2a:a8:5a:bd:3f
> > regdomain ETSI country AT authmode WPA2/802.11i privacy ON
> > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60
> > protmode CTS wme roaming MANUAL
> > groups: wlan
> > lo1: flags=8049 metric 0 mtu 16384
> > options=680003
> > inet 10.241.0.0 netmask 0x
> > inet 10.241.0.1 netmask 0x
> > inet 10.241.0.2 netmask 0x
> > inet 10.241.0.3 netmask 0x
> > inet 10.241.0.4 netmask 0x
> > inet 10.241.0.5 netmask 0x
> > inet 10.241.0.6 netmask 0x
> > inet 10.241.0.7 netmask 0x
> > inet 10.241.0.8 netmask 0x
> > inet 10.241.0.9 netmask 0x
> > inet 10.241.0.10 netmask 0x
> > inet 10.241.0.11 netmask 0x
> > inet 10.241.0.12 netmask 0x
> > inet 10.241.0.13 netmask 0x
> > inet 10.241.0.14 netmask 0x
> > inet 10.241.0.15 netmask 0x
> > nd6 options=29
> > groups: lo
> > bridge0: flags=8843 metric 0 mtu
> > 1500
> > description: vm-public
> > ether 02:63:d4:40:fe:00
> > nd6 options=1
> > groups: bridge
> > id 00:00:00:00:00:00 priority 0 hellotime 2 fwddelay 15
> > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
> > root id 00:00:00:00:00:00 priority 0 ifcost 0 port 0
> > member: wlan0 flags=143
> > ifmaxaddr 0 port 3 priority 128 path cost 370370
>
> Hello,
>
> could you specify what exactly isn't working? How do
Re: 8021x on wired Ethernet
Bengt Ahlgren writes: > Doug Ambrisko writes: > >> On Wed, May 16, 2018 at 02:17:21PM +0300, Zeus Panchenko wrote: >> | Bengt Ahlgren wrote: >> | > Is there a standard "rc.conf" way to configure 8021x authentication on >> | > wired ethernet? >> | >> | looks like it's to be something like: ifconfig_em0="WPA" >> >> Yes for example; >> ifconfig_em0="WPA " >> >> We use 802.1x at work. > > Thanks Zeus and Doug, it does work! I use ifconfig_em0="WPA DHCP". > > I first thought I needed a separate wpa_supplicant.conf for wired, but > it finds the appropriate entry there anyway among many WiFis. It however does not work so well booting with no Ethernet plug connected. The boot hangs when wpa_supplicant is started - a ctrl-C however aborts it and the boot continues. Any ideas to make this more convenient? Bengt ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 180722] [bluetooth] bluetooth takes 30-50 attempts to pair to keyboard and will not re-connect
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=180722 --- Comment #3 from Anil Gulati --- I am the reporter but I don't have a working BSD install right now, sorry. I guess I can say it won't affect me if you close the bug report. Thanks -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
> On Wed, May 30, 2018 at 03:59:12PM +0200, Andreas Nilsson wrote:
> > On Wed, May 30, 2018 at 3:40 PM, Dave Cottlehuber
> > wrote:
> >
> > > I have 10.241.0.0-15/16 bound to lo1 for jails, and I just realised it
> > > doesn't work anymore. Boxes at $DAYJOB use the same config and work just
> > > fine on 11.1R/amd64, otherwise I'd be fired this used to work ~ 1
> > > month
> > > ago, both on my desktop, and my laptop, and now doesn't.
> > >
> > > Have I mis-configured something blindingly obvious here before I embark
> > > on a lengthy bisect?
> > >
> > > # grep -v \# /etc/rc.conf , elided
> > > hostname=akai
> > > kld_list="${kld_list} if_iwm if_axge if_ure if_ue"
> > > ifconfig_ue0=DHCP
> > > ifconfig_ue0_ipv6="inet6 accept_rtadv"
> > > wlans_iwm0="wlan0"
> > > ifconfig_wlan0="WPA DHCP"
> > > ifconfig_wlan0_ipv6="inet6 accept_rtadv"
> > > create_args_wlan0="country AT regdomain ETSI"
> > > cloned_interfaces="${cloned_interfaces} lo1"
> > > ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
> > > ip6addrctl_policy="ipv4_prefer"
> > >
> > > # netstat -4rn
> > > Internet:
> > > DestinationGatewayFlags Netif Expire
> > > default172.16.2.1 UGS ue0
> > > 10.241.0.0 link#4 UH lo1
> > > 10.241.0.1 link#4 UH lo1
> > > 10.241.0.2 link#4 UH lo1
> > > 10.241.0.3 link#4 UH lo1
> > > 10.241.0.4 link#4 UH lo1
> > > 10.241.0.5 link#4 UH lo1
> > > 10.241.0.6 link#4 UH lo1
> > > 10.241.0.7 link#4 UH lo1
> > > 10.241.0.8 link#4 UH lo1
> > > 10.241.0.9 link#4 UH lo1
> > > 10.241.0.10link#4 UH lo1
> > > 10.241.0.11link#4 UH lo1
> > > 10.241.0.12link#4 UH lo1
> > > 10.241.0.13link#4 UH lo1
> > > 10.241.0.14link#4 UH lo1
> > > 10.241.0.15link#4 UH lo1
> > > 127.0.0.1 link#1 UH lo0
> > > 172.16.2.0/24 link#2 U ue0
> > > 172.16.2.92link#3 UHS lo0
> > > 172.16.2.93link#2 UHS lo0
> > >
> > > # ifconfig
> > > lo0: flags=8049 metric 0 mtu 16384
> > > options=680003
> > > inet6 ::1 prefixlen 128
> > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
> > > inet 127.0.0.1 netmask 0xff00
> > > nd6 options=21
> > > groups: lo
> > > ue0: flags=8843 metric 0 mtu 1500
> > > options=8000b
> > > ether 74:da:38:d8:fe:a7
> > > inet6 fe80::76da:38ff:fed8:fea7%ue0 prefixlen 64 scopeid 0x2
> > > inet 172.16.2.93 netmask 0xff00 broadcast 172.16.2.255
> > > nd6 options=23
> > > media: Ethernet autoselect (1000baseT )
> > > status: active
> > > wlan0: flags=8943 metric
> > > 0 mtu 1500
> > > ether 00:28:f8:d0:91:52
> > > inet6 fe80::228:f8ff:fed0:9152%wlan0 prefixlen 64 scopeid 0x3
> > > inet 172.16.2.92 netmask 0xff00 broadcast 172.16.2.255
> > > nd6 options=23
> > > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
> > > status: associated
> > > ssid skunkwerks channel 6 (2437 MHz 11g) bssid 80:2a:a8:5a:bd:3f
> > > regdomain ETSI country AT authmode WPA2/802.11i privacy ON
> > > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60
> > > protmode CTS wme roaming MANUAL
> > > groups: wlan
> > > lo1: flags=8049 metric 0 mtu 16384
> > > options=680003
> > > inet 10.241.0.0 netmask 0x
> > > inet 10.241.0.1 netmask 0x
> > > inet 10.241.0.2 netmask 0x
> > > inet 10.241.0.3 netmask 0x
> > > inet 10.241.0.4 netmask 0x
> > > inet 10.241.0.5 netmask 0x
> > > inet 10.241.0.6 netmask 0x
> > > inet 10.241.0.7 netmask 0x
> > > inet 10.241.0.8 netmask 0x
> > > inet 10.241.0.9 netmask 0x
> > > inet 10.241.0.10 netmask 0x
> > > inet 10.241.0.11 netmask 0x
> > > inet 10.241.0.12 netmask 0x
> > > inet 10.241.0.13 netmask 0x
> > > inet 10.241.0.14 netmask 0x
> > > inet 10.241.0.15 netmask 0x
> > > nd6 options=29
> > > groups: lo
> > > bridge0: flags=8843 metric 0 mtu
> > > 1500
> > > description: vm-public
> > > ether 02:63:d4:40:fe:00
> > > nd6 options=1
> > > groups: bridge
> > > id 00:00:00:00:00:00 priority 0 hellotime 2 fwddelay 15
> > > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
> > > r
Re: Testing VF/PF code
On Tue, May 29, 2018 at 12:58 PM Sean Bruno wrote:
>
> Does anyone have a process for testing the VF drivers (ixgbe igb, etc)
> in FreeBSD without actually firing up linux to instantiate a VM or using
> EC2?
We have native support for creating VFs for ixl and ixgbe (and cxgbe).
For igb you're out of luck (but SR-IOV on igb is kind of a waste of
time anyway)
To create the VFs, create the following conf file:
ix0.conf:
PF {
device : "ix0";
num_vfs : 4;
}
You can create the VFs with "iovctl -f ix0.conf -C"
You should see 4 new ixgbevf instances show up in the PCI tree and the
driver should attach. The one caveat here is that I'm not sure of the
state of the ixgbe PF implementation -- some people reported issues
with it a while back, and I'm not sure if they were ever resolved.
ixl should be solid, though.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
On Wed, May 30, 2018 at 07:44:52AM -0700, Rodney W. Grimes wrote:
> > On Wed, May 30, 2018 at 03:59:12PM +0200, Andreas Nilsson wrote:
> > > On Wed, May 30, 2018 at 3:40 PM, Dave Cottlehuber
> > > wrote:
> > >
> > > > I have 10.241.0.0-15/16 bound to lo1 for jails, and I just realised it
> > > > doesn't work anymore. Boxes at $DAYJOB use the same config and work just
> > > > fine on 11.1R/amd64, otherwise I'd be fired this used to work ~ 1
> > > > month
> > > > ago, both on my desktop, and my laptop, and now doesn't.
> > > >
> > > > Have I mis-configured something blindingly obvious here before I embark
> > > > on a lengthy bisect?
> > > >
> > > > # grep -v \# /etc/rc.conf , elided
> > > > hostname=akai
> > > > kld_list="${kld_list} if_iwm if_axge if_ure if_ue"
> > > > ifconfig_ue0=DHCP
> > > > ifconfig_ue0_ipv6="inet6 accept_rtadv"
> > > > wlans_iwm0="wlan0"
> > > > ifconfig_wlan0="WPA DHCP"
> > > > ifconfig_wlan0_ipv6="inet6 accept_rtadv"
> > > > create_args_wlan0="country AT regdomain ETSI"
> > > > cloned_interfaces="${cloned_interfaces} lo1"
> > > > ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
> > > > ip6addrctl_policy="ipv4_prefer"
> > > >
> > > > # netstat -4rn
> > > > Internet:
> > > > DestinationGatewayFlags Netif Expire
> > > > default172.16.2.1 UGS ue0
> > > > 10.241.0.0 link#4 UH lo1
> > > > 10.241.0.1 link#4 UH lo1
> > > > 10.241.0.2 link#4 UH lo1
> > > > 10.241.0.3 link#4 UH lo1
> > > > 10.241.0.4 link#4 UH lo1
> > > > 10.241.0.5 link#4 UH lo1
> > > > 10.241.0.6 link#4 UH lo1
> > > > 10.241.0.7 link#4 UH lo1
> > > > 10.241.0.8 link#4 UH lo1
> > > > 10.241.0.9 link#4 UH lo1
> > > > 10.241.0.10link#4 UH lo1
> > > > 10.241.0.11link#4 UH lo1
> > > > 10.241.0.12link#4 UH lo1
> > > > 10.241.0.13link#4 UH lo1
> > > > 10.241.0.14link#4 UH lo1
> > > > 10.241.0.15link#4 UH lo1
> > > > 127.0.0.1 link#1 UH lo0
> > > > 172.16.2.0/24 link#2 U ue0
> > > > 172.16.2.92link#3 UHS lo0
> > > > 172.16.2.93link#2 UHS lo0
> > > >
> > > > # ifconfig
> > > > lo0: flags=8049 metric 0 mtu 16384
> > > > options=680003
> > > > inet6 ::1 prefixlen 128
> > > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
> > > > inet 127.0.0.1 netmask 0xff00
> > > > nd6 options=21
> > > > groups: lo
> > > > ue0: flags=8843 metric 0 mtu
> > > > 1500
> > > > options=8000b
> > > > ether 74:da:38:d8:fe:a7
> > > > inet6 fe80::76da:38ff:fed8:fea7%ue0 prefixlen 64 scopeid 0x2
> > > > inet 172.16.2.93 netmask 0xff00 broadcast 172.16.2.255
> > > > nd6 options=23
> > > > media: Ethernet autoselect (1000baseT )
> > > > status: active
> > > > wlan0: flags=8943 metric
> > > > 0 mtu 1500
> > > > ether 00:28:f8:d0:91:52
> > > > inet6 fe80::228:f8ff:fed0:9152%wlan0 prefixlen 64 scopeid 0x3
> > > > inet 172.16.2.92 netmask 0xff00 broadcast 172.16.2.255
> > > > nd6 options=23
> > > > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
> > > > status: associated
> > > > ssid skunkwerks channel 6 (2437 MHz 11g) bssid 80:2a:a8:5a:bd:3f
> > > > regdomain ETSI country AT authmode WPA2/802.11i privacy ON
> > > > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid
> > > > 60
> > > > protmode CTS wme roaming MANUAL
> > > > groups: wlan
> > > > lo1: flags=8049 metric 0 mtu 16384
> > > > options=680003
> > > > inet 10.241.0.0 netmask 0x
> > > > inet 10.241.0.1 netmask 0x
> > > > inet 10.241.0.2 netmask 0x
> > > > inet 10.241.0.3 netmask 0x
> > > > inet 10.241.0.4 netmask 0x
> > > > inet 10.241.0.5 netmask 0x
> > > > inet 10.241.0.6 netmask 0x
> > > > inet 10.241.0.7 netmask 0x
> > > > inet 10.241.0.8 netmask 0x
> > > > inet 10.241.0.9 netmask 0x
> > > > inet 10.241.0.10 netmask 0x
> > > > inet 10.241.0.11 netmask 0x
> > > > inet 10.241.0.12 netmask 0x
> > > > inet 10.241.0.13 netmask 0x
> > > > inet 10.241.0.14 netmask 0x
> > > > inet 10.241.0.15 netmask 0x
> > > > nd6 options=29
> > > > groups: lo
> > > > bridge0: flags=8843 metric 0 mtu
> > > > 1500
[Bug 180722] [bluetooth] bluetooth takes 30-50 attempts to pair to keyboard and will not re-connect
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=180722 Steve Wills changed: What|Removed |Added CC||swi...@freebsd.org --- Comment #4 from Steve Wills --- I can say that I don't have this issue on 12-CURRENT with my BT keyboard. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 180722] [bluetooth] bluetooth takes 30-50 attempts to pair to keyboard and will not re-connect
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=180722 Steve Wills changed: What|Removed |Added Assignee|n...@freebsd.org |blueto...@freebsd.org --- Comment #5 from Steve Wills --- Also, not sure why this is assigned to net@ instead of bluetooth@. Reassigning... -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
On Wed, 30 May 2018, at 15:40, Dave Cottlehuber wrote:
> I have 10.241.0.0-15/16 bound to lo1 for jails, and I just realised it>
> doesn't work anymore. Boxes at $DAYJOB use the same config and
> work just> fine on 11.1R/amd64, otherwise I'd be fired this used to work
> ~ 1> month ago, both on my desktop, and my laptop, and now doesn't.
ping 10.241.0.0 or any of the 15 IPs says no route to host. trace route
does the same thing. Removing the spurious bridge has no effect either.
my boot environment from r333243 can ping though, netstat and rc.conf
are identical between runs.
Sorry I wrote this on a phone and copy paste failed.
> Have I mis-configured something blindingly obvious here before
> I embark> on a lengthy bisect?
>
> # grep -v \# /etc/rc.conf , elided
> hostname=akai
> kld_list="${kld_list} if_iwm if_axge if_ure if_ue"
> ifconfig_ue0=DHCP
> ifconfig_ue0_ipv6="inet6 accept_rtadv"
> wlans_iwm0="wlan0"
> ifconfig_wlan0="WPA DHCP"
> ifconfig_wlan0_ipv6="inet6 accept_rtadv"
> create_args_wlan0="country AT regdomain ETSI"
> cloned_interfaces="${cloned_interfaces} lo1"
> ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
> ip6addrctl_policy="ipv4_prefer"
>
> # netstat -4rn
> Internet:
> DestinationGatewayFlags Netif Expire
> default172.16.2.1 UGS ue0
> 10.241.0.0 link#4 UH lo1
> 10.241.0.1 link#4 UH lo1
> 10.241.0.2 link#4 UH lo1
> 10.241.0.3 link#4 UH lo1
> 10.241.0.4 link#4 UH lo1
> 10.241.0.5 link#4 UH lo1
> 10.241.0.6 link#4 UH lo1
> 10.241.0.7 link#4 UH lo1
> 10.241.0.8 link#4 UH lo1
> 10.241.0.9 link#4 UH lo1
> 10.241.0.10link#4 UH lo1
> 10.241.0.11link#4 UH lo1
> 10.241.0.12link#4 UH lo1
> 10.241.0.13link#4 UH lo1
> 10.241.0.14link#4 UH lo1
> 10.241.0.15link#4 UH lo1
> 127.0.0.1 link#1 UH lo0
> 172.16.2.0/24 link#2 U ue0
> 172.16.2.92link#3 UHS lo0
> 172.16.2.93link#2 UHS lo0
>
> # ifconfig
> lo0: flags=8049 metric 0 mtu 16384
> options=680003
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
> inet 127.0.0.1 netmask 0xff00
> nd6 options=21
> groups: lo
> ue0: flags=8843 metric 0 mtu
> 1500
> options=8000b
> ether 74:da:38:d8:fe:a7
> inet6 fe80::76da:38ff:fed8:fea7%ue0 prefixlen 64 scopeid 0x2
> inet 172.16.2.93 netmask 0xff00 broadcast 172.16.2.255
> nd6 options=23
> media: Ethernet autoselect (1000baseT )
> status: active
> wlan0: flags=8943
> metric> 0 mtu 1500
> ether 00:28:f8:d0:91:52
> inet6 fe80::228:f8ff:fed0:9152%wlan0 prefixlen 64 scopeid 0x3
> inet 172.16.2.92 netmask 0xff00 broadcast 172.16.2.255
> nd6 options=23
> media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
> status: associated
> ssid skunkwerks channel 6 (2437 MHz 11g) bssid 80:2a:a8:5a:bd:3f
> regdomain ETSI country AT authmode WPA2/802.11i privacy ON
> deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60
> protmode CTS wme roaming MANUAL
> groups: wlan
> lo1: flags=8049 metric 0 mtu 16384
> options=680003
> inet 10.241.0.0 netmask 0x
> inet 10.241.0.1 netmask 0x
> inet 10.241.0.2 netmask 0x
> inet 10.241.0.3 netmask 0x
> inet 10.241.0.4 netmask 0x
> inet 10.241.0.5 netmask 0x
> inet 10.241.0.6 netmask 0x
> inet 10.241.0.7 netmask 0x
> inet 10.241.0.8 netmask 0x
> inet 10.241.0.9 netmask 0x
> inet 10.241.0.10 netmask 0x
> inet 10.241.0.11 netmask 0x
> inet 10.241.0.12 netmask 0x
> inet 10.241.0.13 netmask 0x
> inet 10.241.0.14 netmask 0x
> inet 10.241.0.15 netmask 0x
> nd6 options=29
> groups: lo
> bridge0: flags=8843
> metric 0 mtu> 1500
> description: vm-public
> ether 02:63:d4:40:fe:00
> nd6 options=1
> groups: bridge
> id 00:00:00:00:00:00 priority 0 hellotime 2 fwddelay 15
> maxage 20 holdcnt 6 proto rstp maxaddr 20
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Testing VF/PF code
Am 30.05.2018 um 16:45 schrieb Ryan Stone: On Tue, May 29, 2018 at 12:58 PM Sean Bruno wrote: Does anyone have a process for testing the VF drivers (ixgbe igb, etc) in FreeBSD without actually firing up linux to instantiate a VM or using EC2? We have native support for creating VFs for ixl and ixgbe (and cxgbe). For igb you're out of luck (but SR-IOV on igb is kind of a waste of time anyway) I'd like to note that I'm strongly missing SR-IOV for if_igb(4) and I don't consider it as a waste of time, speaking of the time needed for the setup – not the time to make the code happen; that's nothing I can achive (not even estimate) so I won't try to judge about the sense of that time relation... 82576 is a wonderful piece of hardware (mostly true for i350 also) and I'm missing the ability to use VFs for jails and bhyve(8) likewise with these NICs. There are still many appliances that don't need 10GE rates and could easily cope with FastEthernet rates. For such appliances, security/design considerations have much more weight than throughput, which VFs would greatly support implementation simplicity/consistency. So igbv(4) is on top of my christmas wishlist ;-) Two or three of the 2-port cards and a LACP switch-stack (GbE) make a nice platform for a dozend VMs/jails – affordable by means of financial and electrical power budget likewise. No tech aspects/justification here, just my experience based opinion. Thanks, -harry ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
> On Wed, May 30, 2018 at 07:44:52AM -0700, Rodney W. Grimes wrote:
> > > On Wed, May 30, 2018 at 03:59:12PM +0200, Andreas Nilsson wrote:
> > > > On Wed, May 30, 2018 at 3:40 PM, Dave Cottlehuber
> > > > wrote:
> > > >
> > > > > I have 10.241.0.0-15/16 bound to lo1 for jails, and I just realised it
> > > > > doesn't work anymore. Boxes at $DAYJOB use the same config and work
> > > > > just
> > > > > fine on 11.1R/amd64, otherwise I'd be fired this used to work ~ 1
> > > > > month
> > > > > ago, both on my desktop, and my laptop, and now doesn't.
> > > > >
> > > > > Have I mis-configured something blindingly obvious here before I
> > > > > embark
> > > > > on a lengthy bisect?
> > > > >
> > > > > # grep -v \# /etc/rc.conf , elided
> > > > > hostname=akai
> > > > > kld_list="${kld_list} if_iwm if_axge if_ure if_ue"
> > > > > ifconfig_ue0=DHCP
> > > > > ifconfig_ue0_ipv6="inet6 accept_rtadv"
> > > > > wlans_iwm0="wlan0"
> > > > > ifconfig_wlan0="WPA DHCP"
> > > > > ifconfig_wlan0_ipv6="inet6 accept_rtadv"
> > > > > create_args_wlan0="country AT regdomain ETSI"
> > > > > cloned_interfaces="${cloned_interfaces} lo1"
> > > > > ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
> > > > > ip6addrctl_policy="ipv4_prefer"
> > > > >
> > > > > # netstat -4rn
> > > > > Internet:
> > > > > DestinationGatewayFlags Netif Expire
> > > > > default172.16.2.1 UGS ue0
> > > > > 10.241.0.0 link#4 UH lo1
> > > > > 10.241.0.1 link#4 UH lo1
> > > > > 10.241.0.2 link#4 UH lo1
> > > > > 10.241.0.3 link#4 UH lo1
> > > > > 10.241.0.4 link#4 UH lo1
> > > > > 10.241.0.5 link#4 UH lo1
> > > > > 10.241.0.6 link#4 UH lo1
> > > > > 10.241.0.7 link#4 UH lo1
> > > > > 10.241.0.8 link#4 UH lo1
> > > > > 10.241.0.9 link#4 UH lo1
> > > > > 10.241.0.10link#4 UH lo1
> > > > > 10.241.0.11link#4 UH lo1
> > > > > 10.241.0.12link#4 UH lo1
> > > > > 10.241.0.13link#4 UH lo1
> > > > > 10.241.0.14link#4 UH lo1
> > > > > 10.241.0.15link#4 UH lo1
> > > > > 127.0.0.1 link#1 UH lo0
> > > > > 172.16.2.0/24 link#2 U ue0
> > > > > 172.16.2.92link#3 UHS lo0
> > > > > 172.16.2.93link#2 UHS lo0
> > > > >
> > > > > # ifconfig
> > > > > lo0: flags=8049 metric 0 mtu 16384
> > > > >
> > > > > options=680003
> > > > > inet6 ::1 prefixlen 128
> > > > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
> > > > > inet 127.0.0.1 netmask 0xff00
> > > > > nd6 options=21
> > > > > groups: lo
> > > > > ue0: flags=8843 metric 0 mtu
> > > > > 1500
> > > > > options=8000b
> > > > > ether 74:da:38:d8:fe:a7
> > > > > inet6 fe80::76da:38ff:fed8:fea7%ue0 prefixlen 64 scopeid 0x2
> > > > > inet 172.16.2.93 netmask 0xff00 broadcast 172.16.2.255
> > > > > nd6 options=23
> > > > > media: Ethernet autoselect (1000baseT )
> > > > > status: active
> > > > > wlan0: flags=8943
> > > > > metric
> > > > > 0 mtu 1500
> > > > > ether 00:28:f8:d0:91:52
> > > > > inet6 fe80::228:f8ff:fed0:9152%wlan0 prefixlen 64 scopeid 0x3
> > > > > inet 172.16.2.92 netmask 0xff00 broadcast 172.16.2.255
> > > > > nd6 options=23
> > > > > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
> > > > > status: associated
> > > > > ssid skunkwerks channel 6 (2437 MHz 11g) bssid
> > > > > 80:2a:a8:5a:bd:3f
> > > > > regdomain ETSI country AT authmode WPA2/802.11i privacy ON
> > > > > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10
> > > > > scanvalid 60
> > > > > protmode CTS wme roaming MANUAL
> > > > > groups: wlan
> > > > > lo1: flags=8049 metric 0 mtu 16384
> > > > >
> > > > > options=680003
> > > > > inet 10.241.0.0 netmask 0x
> > > > > inet 10.241.0.1 netmask 0x
> > > > > inet 10.241.0.2 netmask 0x
> > > > > inet 10.241.0.3 netmask 0x
> > > > > inet 10.241.0.4 netmask 0x
> > > > > inet 10.241.0.5 netmask 0x
> > > > > inet 10.241.0.6 netmask 0x
> > > > > inet 10.241.0.7 netmask 0x
> > > > > inet 10.241.0.8 netmask 0x
> > > > > inet 10.241.0.9 netmask 0x
> > > > > inet 10.241.0.10 netmask 0x
> > > > > inet 10.241.0.11 netmask 0x
> > > > > inet 10.241.0.12 netmask 0x
> > >
Re: Testing VF/PF code
Harry, I wasn’t aware of anyone desiring vf support for igb but I’ll take a look at it for you if you can test -current with patches when I’m ready. My motive is more to validate and refine the iflib functionality and this is a good exercise. On Wed, May 30, 2018 at 8:20 AM Harry Schmalzbauer wrote: > Am 30.05.2018 um 16:45 schrieb Ryan Stone: > > On Tue, May 29, 2018 at 12:58 PM Sean Bruno wrote: > >> Does anyone have a process for testing the VF drivers (ixgbe igb, etc) > >> in FreeBSD without actually firing up linux to instantiate a VM or using > >> EC2? > > We have native support for creating VFs for ixl and ixgbe (and cxgbe). > > For igb you're out of luck (but SR-IOV on igb is kind of a waste of > > time anyway) > > I'd like to note that I'm strongly missing SR-IOV for if_igb(4) and I > don't consider it as a waste of time, speaking of the time needed for > the setup – not the time to make the code happen; that's nothing I can > achive (not even estimate) so I won't try to judge about the sense of > that time relation... > > 82576 is a wonderful piece of hardware (mostly true for i350 also) and > I'm missing the ability to use VFs for jails and bhyve(8) likewise with > these NICs. > There are still many appliances that don't need 10GE rates and could > easily cope with FastEthernet rates. For such appliances, > security/design considerations have much more weight than throughput, > which VFs would greatly support implementation simplicity/consistency. > So igbv(4) is on top of my christmas wishlist ;-) > Two or three of the 2-port cards and a LACP switch-stack (GbE) make a > nice platform for a dozend VMs/jails – affordable by means of financial > and electrical power budget likewise. > > No tech aspects/justification here, just my experience based opinion. > > Thanks, > > -harry > > ___ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" > ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Testing VF/PF code
Am 30.05.2018 um 17:53 schrieb Kevin Bowling: Harry, I wasn’t aware of anyone desiring vf support for igb but I’ll take a look at it for you if you can test -current with patches when I’m ready. My motive is more to validate and refine the iflib functionality and this is a good exercise. Christmas in summer on the northern hemisphere :-) Unfortunately the only machine I have available for tests won't do SR-IOV as far as I remember, since this feature is disabled for E3-Xeons. I can't remember all the details, but I gave up with SR-IOV on any Intel single-socket platform since E5-1600 v3/5 never showed up :-( Although FreeBSD wasn't involved, I guess the basic requirements are the same and I don't have a chance to use SR-IOV on E3-Xeon (v2, C203 BearTooth) Shall I falsify with mps(4)? I think this supports VFs and I have one in spare. I'm very sorry that I won't be able to test anything – but if I'm the only igb-VF consumer, not capable of using it currently at all, Ryan might be right with the waste of time... -harry ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Testing VF/PF code
I think the biggest hurdle is that for igb, the pf and vf should be split. That was being considered at the same time as the ixgbe/ixgbevf split, but there was little interest at the time. Jeff On 5/30/18, 9:13 AM, "owner-freebsd-...@freebsd.org on behalf of Harry Schmalzbauer" wrote: Am 30.05.2018 um 17:53 schrieb Kevin Bowling: > Harry, > > I wasn’t aware of anyone desiring vf support for igb but I’ll take a > look at it for you if you can test -current with patches when I’m ready. > My motive is more to validate and refine the iflib functionality and > this is a good exercise. Christmas in summer on the northern hemisphere :-) Unfortunately the only machine I have available for tests won't do SR-IOV as far as I remember, since this feature is disabled for E3-Xeons. I can't remember all the details, but I gave up with SR-IOV on any Intel single-socket platform since E5-1600 v3/5 never showed up :-( Although FreeBSD wasn't involved, I guess the basic requirements are the same and I don't have a chance to use SR-IOV on E3-Xeon (v2, C203 BearTooth) Shall I falsify with mps(4)? I think this supports VFs and I have one in spare. I'm very sorry that I won't be able to test anything – but if I'm the only igb-VF consumer, not capable of using it currently at all, Ryan might be right with the waste of time... -harry ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 60293] [netinet] [patch] FreeBSD arp poison patch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=60293 Eugene Grosbein changed: What|Removed |Added Status|Open|Closed Resolution|--- |FIXED CC||eu...@freebsd.org --- Comment #9 from Eugene Grosbein --- Fixed long time ago with introduction of "ifconfig staticarp" option. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
On Wed, 30 May 2018 17:46:06 +0200, "Rodney W. Grimes" wrote:
>
> > On Wed, May 30, 2018 at 07:44:52AM -0700, Rodney W. Grimes wrote:
> > > > On Wed, May 30, 2018 at 03:59:12PM +0200, Andreas Nilsson wrote:
> > > > > On Wed, May 30, 2018 at 3:40 PM, Dave Cottlehuber
> > > > > wrote:
> > > > >
> > > > > > I have 10.241.0.0-15/16 bound to lo1 for jails, and I just realised
> > > > > > it
> > > > > > doesn't work anymore. Boxes at $DAYJOB use the same config and work
> > > > > > just
> > > > > > fine on 11.1R/amd64, otherwise I'd be fired this used to work ~
> > > > > > 1 month
> > > > > > ago, both on my desktop, and my laptop, and now doesn't.
> > > > > >
> > > > > > Have I mis-configured something blindingly obvious here before I
> > > > > > embark
> > > > > > on a lengthy bisect?
> > > > > >
> > > > > > # grep -v \# /etc/rc.conf , elided
> > > > > > hostname=akai
> > > > > > kld_list="${kld_list} if_iwm if_axge if_ure if_ue"
> > > > > > ifconfig_ue0=DHCP
> > > > > > ifconfig_ue0_ipv6="inet6 accept_rtadv"
> > > > > > wlans_iwm0="wlan0"
> > > > > > ifconfig_wlan0="WPA DHCP"
> > > > > > ifconfig_wlan0_ipv6="inet6 accept_rtadv"
> > > > > > create_args_wlan0="country AT regdomain ETSI"
> > > > > > cloned_interfaces="${cloned_interfaces} lo1"
> > > > > > ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
> > > > > > ip6addrctl_policy="ipv4_prefer"
> > > > > >
> > > > > > # netstat -4rn
> > > > > > Internet:
> > > > > > DestinationGatewayFlags Netif Expire
> > > > > > default172.16.2.1 UGS ue0
> > > > > > 10.241.0.0 link#4 UH lo1
> > > > > > 10.241.0.1 link#4 UH lo1
> > > > > > 10.241.0.2 link#4 UH lo1
> > > > > > 10.241.0.3 link#4 UH lo1
> > > > > > 10.241.0.4 link#4 UH lo1
> > > > > > 10.241.0.5 link#4 UH lo1
> > > > > > 10.241.0.6 link#4 UH lo1
> > > > > > 10.241.0.7 link#4 UH lo1
> > > > > > 10.241.0.8 link#4 UH lo1
> > > > > > 10.241.0.9 link#4 UH lo1
> > > > > > 10.241.0.10link#4 UH lo1
> > > > > > 10.241.0.11link#4 UH lo1
> > > > > > 10.241.0.12link#4 UH lo1
> > > > > > 10.241.0.13link#4 UH lo1
> > > > > > 10.241.0.14link#4 UH lo1
> > > > > > 10.241.0.15link#4 UH lo1
> > > > > > 127.0.0.1 link#1 UH lo0
> > > > > > 172.16.2.0/24 link#2 U ue0
> > > > > > 172.16.2.92link#3 UHS lo0
> > > > > > 172.16.2.93link#2 UHS lo0
> > > > > >
> > > > > > # ifconfig
> > > > > > lo0: flags=8049 metric 0 mtu 16384
> > > > > >
> > > > > > options=680003
> > > > > > inet6 ::1 prefixlen 128
> > > > > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
> > > > > > inet 127.0.0.1 netmask 0xff00
> > > > > > nd6 options=21
> > > > > > groups: lo
> > > > > > ue0: flags=8843 metric 0
> > > > > > mtu 1500
> > > > > > options=8000b
> > > > > > ether 74:da:38:d8:fe:a7
> > > > > > inet6 fe80::76da:38ff:fed8:fea7%ue0 prefixlen 64 scopeid 0x2
> > > > > > inet 172.16.2.93 netmask 0xff00 broadcast 172.16.2.255
> > > > > > nd6 options=23
> > > > > > media: Ethernet autoselect (1000baseT )
> > > > > > status: active
> > > > > > wlan0: flags=8943
> > > > > > metric
> > > > > > 0 mtu 1500
> > > > > > ether 00:28:f8:d0:91:52
> > > > > > inet6 fe80::228:f8ff:fed0:9152%wlan0 prefixlen 64 scopeid
> > > > > > 0x3
> > > > > > inet 172.16.2.92 netmask 0xff00 broadcast 172.16.2.255
> > > > > > nd6 options=23
> > > > > > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
> > > > > > status: associated
> > > > > > ssid skunkwerks channel 6 (2437 MHz 11g) bssid
> > > > > > 80:2a:a8:5a:bd:3f
> > > > > > regdomain ETSI country AT authmode WPA2/802.11i privacy ON
> > > > > > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10
> > > > > > scanvalid 60
> > > > > > protmode CTS wme roaming MANUAL
> > > > > > groups: wlan
> > > > > > lo1: flags=8049 metric 0 mtu 16384
> > > > > >
> > > > > > options=680003
> > > > > > inet 10.241.0.0 netmask 0x
> > > > > > inet 10.241.0.1 netmask 0x
> > > > > > inet 10.241.0.2 netmask 0x
> > > > > > inet 10.241.0.3 netmask 0x
> > > > > > inet 10.241.0.4 netmask 0x
> > > > > > inet 10.241.0.5 netmask 0x
> > > > > > inet 10.241.0.6 netmask 0x
> > > > > > inet 10.241.0.7 netm
Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
On Wed, 30 May 2018, at 17:46, Rodney W. Grimes wrote:
> > > > > > ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
> > > > > > lo1: flags=8049 metric 0 mtu 16384
> > > > > > inet 10.241.0.0 netmask 0x
> > > > > > inet 10.241.0.1 netmask 0x
> > > > > > inet 10.241.0.2 netmask 0x
Thanks Rod, Andreas, Herbert for your help! Back at a proper computer now.
I think there are 2 things; invalid IP (see end for some interesting notes),
and also expansion of ifconfig__aliases.
# ifconfig_$(if)_aliases
This is my config:
> cloned_interfaces="lo1"
> ifconfig_lo1_aliases="inet 10.24 1.0.0-15/16"
But, I *don't* have a line like this:
> ifconfig_lo1="inet 10.241.0.0/16"
and if I add it and bump the range to 10.241.0.1/16, then all is well again
and ping $DODGY_IP works again, but I get 2 entries with /16 mask:
inet 10.241.0.0 netmask 0x
inet 10.241.0.1 netmask 0x
inet 10.241.0.2 netmask 0x
So the solution seems to be this, to keep the 0xfff to just 1 IP:
> cloned_interfaces="lo1"
> ifconfig_lo1="inet 10.241.0.0/16"
> ifconfig_lo1_aliases="inet 10.24 1.0.0-15/16"
Presumably I've copy-pasted this a long time ago and never questioned it. I
checked several random websites, and there are quite a few skipping
`ifconfig_lo1`, using just the aliases, and mainly with jail configs, so I
guess this change will catch other people too.
I'm not sure what's changed, as nothing recent in /etc/rc.d or
/etc/network.subr commits seems related. What's the best option here?
Just a doc patch saying you can't use aliases without a prior ifconfig_ ?
# invalid IP
TLDR 10.241.0.0/16 is technically not a valid host IP but it has obviously
worked in the past.
I've been binding 10.241.0.1-15 to jail IPs, and abusing 10.241.0.0 as the
"magic ip" that is bound to net/haproxy or spiped in the host system to broker
exernal connections into the jail IP ranges from external internet. I will
rectify my configuration but I will miss the symmetry :-)
https://tools.ietf.org/html/rfc1122#section-3.3.6 is the closest description I
could find for this. Interestingly, they blame 4.2BSD for this and say it's
addressed since 4.3:
## 3.3.6 Broadcasts
Section 3.2.1.3 defined the four standard IP broadcast address
forms:
Limited Broadcast: {-1, -1}
Directed Broadcast: {,-1}
Subnet Directed Broadcast:
{,,-1}
All-Subnets Directed Broadcast: {,-1,-1}
A host MUST recognize any of these forms in the destination
address of an incoming datagram.
There is a class of hosts* that use non-standard broadcast
address forms, substituting 0 for -1. All hosts SHOULD
recognize and accept any of these non-standard broadcast
addresses as the destination address of an incoming datagram.
_
*4.2BSD Unix and its derivatives, but not 4.3BSD.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
> On Wed, 30 May 2018 17:46:06 +0200, "Rodney W. Grimes" wrote:
> >
> > > On Wed, May 30, 2018 at 07:44:52AM -0700, Rodney W. Grimes wrote:
> > > > > On Wed, May 30, 2018 at 03:59:12PM +0200, Andreas Nilsson wrote:
> > > > > > On Wed, May 30, 2018 at 3:40 PM, Dave Cottlehuber
> > > > > > wrote:
> > > > > >
> > > > > > > I have 10.241.0.0-15/16 bound to lo1 for jails, and I just
> > > > > > > realised it
> > > > > > > doesn't work anymore. Boxes at $DAYJOB use the same config and
> > > > > > > work just
> > > > > > > fine on 11.1R/amd64, otherwise I'd be fired this used to work
> > > > > > > ~ 1 month
> > > > > > > ago, both on my desktop, and my laptop, and now doesn't.
> > > > > > >
> > > > > > > Have I mis-configured something blindingly obvious here before I
> > > > > > > embark
> > > > > > > on a lengthy bisect?
> > > > > > >
> > > > > > > # grep -v \# /etc/rc.conf , elided
> > > > > > > hostname=akai
> > > > > > > kld_list="${kld_list} if_iwm if_axge if_ure if_ue"
> > > > > > > ifconfig_ue0=DHCP
> > > > > > > ifconfig_ue0_ipv6="inet6 accept_rtadv"
> > > > > > > wlans_iwm0="wlan0"
> > > > > > > ifconfig_wlan0="WPA DHCP"
> > > > > > > ifconfig_wlan0_ipv6="inet6 accept_rtadv"
> > > > > > > create_args_wlan0="country AT regdomain ETSI"
> > > > > > > cloned_interfaces="${cloned_interfaces} lo1"
> > > > > > > ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
> > > > > > > ip6addrctl_policy="ipv4_prefer"
> > > > > > >
> > > > > > > # netstat -4rn
> > > > > > > Internet:
> > > > > > > DestinationGatewayFlags Netif Expire
> > > > > > > default172.16.2.1 UGS ue0
> > > > > > > 10.241.0.0 link#4 UH lo1
> > > > > > > 10.241.0.1 link#4 UH lo1
> > > > > > > 10.241.0.2 link#4 UH lo1
> > > > > > > 10.241.0.3 link#4 UH lo1
> > > > > > > 10.241.0.4 link#4 UH lo1
> > > > > > > 10.241.0.5 link#4 UH lo1
> > > > > > > 10.241.0.6 link#4 UH lo1
> > > > > > > 10.241.0.7 link#4 UH lo1
> > > > > > > 10.241.0.8 link#4 UH lo1
> > > > > > > 10.241.0.9 link#4 UH lo1
> > > > > > > 10.241.0.10link#4 UH lo1
> > > > > > > 10.241.0.11link#4 UH lo1
> > > > > > > 10.241.0.12link#4 UH lo1
> > > > > > > 10.241.0.13link#4 UH lo1
> > > > > > > 10.241.0.14link#4 UH lo1
> > > > > > > 10.241.0.15link#4 UH lo1
> > > > > > > 127.0.0.1 link#1 UH lo0
> > > > > > > 172.16.2.0/24 link#2 U ue0
> > > > > > > 172.16.2.92link#3 UHS lo0
> > > > > > > 172.16.2.93link#2 UHS lo0
> > > > > > >
> > > > > > > # ifconfig
> > > > > > > lo0: flags=8049 metric 0 mtu 16384
> > > > > > >
> > > > > > > options=680003
> > > > > > > inet6 ::1 prefixlen 128
> > > > > > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
> > > > > > > inet 127.0.0.1 netmask 0xff00
> > > > > > > nd6 options=21
> > > > > > > groups: lo
> > > > > > > ue0: flags=8843 metric 0
> > > > > > > mtu 1500
> > > > > > > options=8000b
> > > > > > > ether 74:da:38:d8:fe:a7
> > > > > > > inet6 fe80::76da:38ff:fed8:fea7%ue0 prefixlen 64 scopeid
> > > > > > > 0x2
> > > > > > > inet 172.16.2.93 netmask 0xff00 broadcast 172.16.2.255
> > > > > > > nd6 options=23
> > > > > > > media: Ethernet autoselect (1000baseT )
> > > > > > > status: active
> > > > > > > wlan0: flags=8943
> > > > > > > metric
> > > > > > > 0 mtu 1500
> > > > > > > ether 00:28:f8:d0:91:52
> > > > > > > inet6 fe80::228:f8ff:fed0:9152%wlan0 prefixlen 64 scopeid
> > > > > > > 0x3
> > > > > > > inet 172.16.2.92 netmask 0xff00 broadcast 172.16.2.255
> > > > > > > nd6 options=23
> > > > > > > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
> > > > > > > status: associated
> > > > > > > ssid skunkwerks channel 6 (2437 MHz 11g) bssid
> > > > > > > 80:2a:a8:5a:bd:3f
> > > > > > > regdomain ETSI country AT authmode WPA2/802.11i privacy ON
> > > > > > > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10
> > > > > > > scanvalid 60
> > > > > > > protmode CTS wme roaming MANUAL
> > > > > > > groups: wlan
> > > > > > > lo1: flags=8049 metric 0 mtu 16384
> > > > > > >
> > > > > > > options=680003
> > > > > > > inet 10.241.0.0 netmask 0x
> > > > > > > inet 10.241.0.1 netmask 0x
> > > > > > > inet 10.241.0.2 netmask 0x
> > > > > > > inet 10.241.0.3 netmask 0xf
Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
Could you please try 334117 vs 334118 and see if 334118 introduces
this regression?
-M
On Wed, May 30, 2018 at 2:48 PM, Rodney W. Grimes
wrote:
>> On Wed, 30 May 2018 17:46:06 +0200, "Rodney W. Grimes" wrote:
>> >
>> > > On Wed, May 30, 2018 at 07:44:52AM -0700, Rodney W. Grimes wrote:
>> > > > > On Wed, May 30, 2018 at 03:59:12PM +0200, Andreas Nilsson wrote:
>> > > > > > On Wed, May 30, 2018 at 3:40 PM, Dave Cottlehuber
>> > > > > > wrote:
>> > > > > >
>> > > > > > > I have 10.241.0.0-15/16 bound to lo1 for jails, and I just
>> > > > > > > realised it
>> > > > > > > doesn't work anymore. Boxes at $DAYJOB use the same config and
>> > > > > > > work just
>> > > > > > > fine on 11.1R/amd64, otherwise I'd be fired this used to
>> > > > > > > work ~ 1 month
>> > > > > > > ago, both on my desktop, and my laptop, and now doesn't.
>> > > > > > >
>> > > > > > > Have I mis-configured something blindingly obvious here before I
>> > > > > > > embark
>> > > > > > > on a lengthy bisect?
>> > > > > > >
>> > > > > > > # grep -v \# /etc/rc.conf , elided
>> > > > > > > hostname=akai
>> > > > > > > kld_list="${kld_list} if_iwm if_axge if_ure if_ue"
>> > > > > > > ifconfig_ue0=DHCP
>> > > > > > > ifconfig_ue0_ipv6="inet6 accept_rtadv"
>> > > > > > > wlans_iwm0="wlan0"
>> > > > > > > ifconfig_wlan0="WPA DHCP"
>> > > > > > > ifconfig_wlan0_ipv6="inet6 accept_rtadv"
>> > > > > > > create_args_wlan0="country AT regdomain ETSI"
>> > > > > > > cloned_interfaces="${cloned_interfaces} lo1"
>> > > > > > > ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
>> > > > > > > ip6addrctl_policy="ipv4_prefer"
>> > > > > > >
>> > > > > > > # netstat -4rn
>> > > > > > > Internet:
>> > > > > > > DestinationGatewayFlags Netif Expire
>> > > > > > > default172.16.2.1 UGS ue0
>> > > > > > > 10.241.0.0 link#4 UH lo1
>> > > > > > > 10.241.0.1 link#4 UH lo1
>> > > > > > > 10.241.0.2 link#4 UH lo1
>> > > > > > > 10.241.0.3 link#4 UH lo1
>> > > > > > > 10.241.0.4 link#4 UH lo1
>> > > > > > > 10.241.0.5 link#4 UH lo1
>> > > > > > > 10.241.0.6 link#4 UH lo1
>> > > > > > > 10.241.0.7 link#4 UH lo1
>> > > > > > > 10.241.0.8 link#4 UH lo1
>> > > > > > > 10.241.0.9 link#4 UH lo1
>> > > > > > > 10.241.0.10link#4 UH lo1
>> > > > > > > 10.241.0.11link#4 UH lo1
>> > > > > > > 10.241.0.12link#4 UH lo1
>> > > > > > > 10.241.0.13link#4 UH lo1
>> > > > > > > 10.241.0.14link#4 UH lo1
>> > > > > > > 10.241.0.15link#4 UH lo1
>> > > > > > > 127.0.0.1 link#1 UH lo0
>> > > > > > > 172.16.2.0/24 link#2 U ue0
>> > > > > > > 172.16.2.92link#3 UHS lo0
>> > > > > > > 172.16.2.93link#2 UHS lo0
>> > > > > > >
>> > > > > > > # ifconfig
>> > > > > > > lo0: flags=8049 metric 0 mtu 16384
>> > > > > > >
>> > > > > > > options=680003
>> > > > > > > inet6 ::1 prefixlen 128
>> > > > > > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
>> > > > > > > inet 127.0.0.1 netmask 0xff00
>> > > > > > > nd6 options=21
>> > > > > > > groups: lo
>> > > > > > > ue0: flags=8843 metric 0
>> > > > > > > mtu 1500
>> > > > > > > options=8000b
>> > > > > > > ether 74:da:38:d8:fe:a7
>> > > > > > > inet6 fe80::76da:38ff:fed8:fea7%ue0 prefixlen 64 scopeid
>> > > > > > > 0x2
>> > > > > > > inet 172.16.2.93 netmask 0xff00 broadcast
>> > > > > > > 172.16.2.255
>> > > > > > > nd6 options=23
>> > > > > > > media: Ethernet autoselect (1000baseT )
>> > > > > > > status: active
>> > > > > > > wlan0:
>> > > > > > > flags=8943 metric
>> > > > > > > 0 mtu 1500
>> > > > > > > ether 00:28:f8:d0:91:52
>> > > > > > > inet6 fe80::228:f8ff:fed0:9152%wlan0 prefixlen 64
>> > > > > > > scopeid 0x3
>> > > > > > > inet 172.16.2.92 netmask 0xff00 broadcast
>> > > > > > > 172.16.2.255
>> > > > > > > nd6 options=23
>> > > > > > > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g
>> > > > > > > status: associated
>> > > > > > > ssid skunkwerks channel 6 (2437 MHz 11g) bssid
>> > > > > > > 80:2a:a8:5a:bd:3f
>> > > > > > > regdomain ETSI country AT authmode WPA2/802.11i privacy
>> > > > > > > ON
>> > > > > > > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10
>> > > > > > > scanvalid 60
>> > > > > > > protmode CTS wme roaming MANUAL
>> > > > > > > groups: wlan
>> > > > > > > lo1: flags=8049 metr
Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
> On Wed, 30 May 2018, at 17:46, Rodney W. Grimes wrote:
> > > > > > > ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
>
> > > > > > > lo1: flags=8049 metric 0 mtu 16384
> > > > > > > inet 10.241.0.0 netmask 0x
> > > > > > > inet 10.241.0.1 netmask 0x
> > > > > > > inet 10.241.0.2 netmask 0x
>
> Thanks Rod, Andreas, Herbert for your help! Back at a proper computer now.
>
> I think there are 2 things; invalid IP (see end for some interesting notes),
> and also expansion of ifconfig__aliases.
>
> # ifconfig_$(if)_aliases
>
> This is my config:
>
> > cloned_interfaces="lo1"
> > ifconfig_lo1_aliases="inet 10.24 1.0.0-15/16"
I am not even sure that parses
>
> But, I *don't* have a line like this:
>
> > ifconfig_lo1="inet 10.241.0.0/16"
This should be an error, or as per rfc treated as
"10.241.255.255/16" which should also be an error.
>
> and if I add it and bump the range to 10.241.0.1/16, then all is well again
> and ping $DODGY_IP works again, but I get 2 entries with /16 mask:
>
> inet 10.241.0.0 netmask 0x
This should not be allowed.
> inet 10.241.0.1 netmask 0x
This is correct.
> inet 10.241.0.2 netmask 0x
>
> So the solution seems to be this, to keep the 0xfff to just 1 IP:
>
> > cloned_interfaces="lo1"
> > ifconfig_lo1="inet 10.241.0.0/16"
> > ifconfig_lo1_aliases="inet 10.24 1.0.0-15/16"
>
> Presumably I've copy-pasted this a long time ago and never questioned it. I
> checked several random websites, and there are quite a few skipping
> `ifconfig_lo1`, using just the aliases, and mainly with jail configs, so I
> guess this change will catch other people too.
>
> I'm not sure what's changed, as nothing recent in /etc/rc.d or
> /etc/network.subr commits seems related. What's the best option here?
>
> Just a doc patch saying you can't use aliases without a prior ifconfig_ ?
I do not believe that needs to be a requirement.
>
> # invalid IP
>
> TLDR 10.241.0.0/16 is technically not a valid host IP but it has obviously
> worked in the past.
Yes, and that working in the past is bad,
probably need to see how far back this bug goes.
Eeekks.. it goes back to at least 5.4 which means
it is bad behavior we are probably going to have to fix. :-(
> I've been binding 10.241.0.1-15 to jail IPs, and abusing 10.241.0.0 as the
> "magic ip" that is bound to net/haproxy or spiped in the host system to
> broker exernal connections into the jail IP ranges from external internet. I
> will rectify my configuration but I will miss the symmetry :-)
>
> https://tools.ietf.org/html/rfc1122#section-3.3.6 is the closest description
> I could find for this. Interestingly, they blame 4.2BSD for this and say it's
> addressed since 4.3:
>
> ## 3.3.6 Broadcasts
^^
This is not the all 0's host value, but the all 1's host value,
these rules are VERY well known and enforced. I am actually
amazed that this use of 0 has not been RFC'ed out of existance,
as far as I know all the other stuff says that the 0th host
on a network is reserved for indicating the Network.
If you look at all the tables on cidr and such they say
the valid host ranges are 1 to (END - 1) Leaving out
the host part value of 0.
>
> Section 3.2.1.3 defined the four standard IP broadcast address
> forms:
>Limited Broadcast: {-1, -1}
>Directed Broadcast: {,-1}
>Subnet Directed Broadcast:
> {,,-1}
>All-Subnets Directed Broadcast: {,-1,-1}
> A host MUST recognize any of these forms in the destination
> address of an incoming datagram.
> There is a class of hosts* that use non-standard broadcast
> address forms, substituting 0 for -1. All hosts SHOULD
^^
> recognize and accept any of these non-standard broadcast
^^^
> addresses as the destination address of an incoming datagram.
Ok, so we *SHOULD* be mapping the 10.241.0.0 to 10.241.255.255 which
should of caused ALL the hosts on that subnet to respond to the ping.
Someone want to investiage linux on this one?
> _
> *4.2BSD Unix and its derivatives, but not 4.3BSD.
--
Rod Grimes rgri...@freebsd.org
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 157182] [lagg] lagg interface not working together with epair interface on bridge
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=157182 Peter Clifton changed: What|Removed |Added CC||petercjclif...@gmail.com --- Comment #4 from Peter Clifton --- I believe this bug might be (potentially) related to my FreeNas 11.1 box falling off the network occasionally, and not being able to renew an IP via DHCP. (The main lagg0 interface is a memeber of bridge0, where epair devices link to jails). I did "ifconfig bridge0 down", and was immediately able to get an IP address with dhclient, whereas before DHCP broadcast packets never appeared to reach the router. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: 'no route to host" for cloned lo1 iface 12.0-CURRENT r334376+56a973815425(master) amd64
On Thu, May 31, 2018, 00:13 Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > On Wed, 30 May 2018, at 17:46, Rodney W. Grimes wrote:
> > > > > > > > ifconfig_lo1_aliases="inet 10.241.0.0-15/16"
> >
> > > > > > > > lo1: flags=8049 metric 0 mtu
> 16384
> > > > > > > > inet 10.241.0.0 netmask 0x
> > > > > > > > inet 10.241.0.1 netmask 0x
> > > > > > > > inet 10.241.0.2 netmask 0x
> >
> > Thanks Rod, Andreas, Herbert for your help! Back at a proper computer
> now.
> >
> > I think there are 2 things; invalid IP (see end for some interesting
> notes), and also expansion of ifconfig__aliases.
> >
> > # ifconfig_$(if)_aliases
> >
> > This is my config:
> >
> > > cloned_interfaces="lo1"
> > > ifconfig_lo1_aliases="inet 10.24 1.0.0-15/16"
> I am not even sure that parses
>
> >
> > But, I *don't* have a line like this:
> >
> > > ifconfig_lo1="inet 10.241.0.0/16"
>
> This should be an error, or as per rfc treated as
> "10.241.255.255/16" which should also be an error.
>
> >
> > and if I add it and bump the range to 10.241.0.1/16, then all is well
> again and ping $DODGY_IP works again, but I get 2 entries with /16 mask:
> >
> > inet 10.241.0.0 netmask 0x
> This should not be allowed.
>
> > inet 10.241.0.1 netmask 0x
> This is correct.
>
> > inet 10.241.0.2 netmask 0x
> >
> > So the solution seems to be this, to keep the 0xfff to just 1 IP:
> >
> > > cloned_interfaces="lo1"
> > > ifconfig_lo1="inet 10.241.0.0/16"
> > > ifconfig_lo1_aliases="inet 10.24 1.0.0-15/16"
>
How about
cloned_interfaces="lo1"
ifconfig_lo1="inet 10.241.0.0/16”
ifconfig_lo1_aliases="10.241.0.1-15/32”
There is one other way, but I need to get to a computer to verify it.
>
> > Presumably I've copy-pasted this a long time ago and never questioned
> it. I checked several random websites, and there are quite a few skipping
> `ifconfig_lo1`, using just the aliases, and mainly with jail configs, so I
> guess this change will catch other people too.
> >
> > I'm not sure what's changed, as nothing recent in /etc/rc.d or
> /etc/network.subr commits seems related. What's the best option here?
> >
> > Just a doc patch saying you can't use aliases without a prior
> ifconfig_ ?
>
> I do not believe that needs to be a requirement.
>
> >
> > # invalid IP
> >
> > TLDR 10.241.0.0/16 is technically not a valid host IP but it has
> obviously worked in the past.
> Yes, and that working in the past is bad,
> probably need to see how far back this bug goes.
> Eeekks.. it goes back to at least 5.4 which means
> it is bad behavior we are probably going to have to fix. :-(
>
> > I've been binding 10.241.0.1-15 to jail IPs, and abusing 10.241.0.0 as
> the "magic ip" that is bound to net/haproxy or spiped in the host system to
> broker exernal connections into the jail IP ranges from external internet.
> I will rectify my configuration but I will miss the symmetry :-)
> >
> > https://tools.ietf.org/html/rfc1122#section-3.3.6 is the closest
> description I could find for this. Interestingly, they blame 4.2BSD for
> this and say it's addressed since 4.3:
> >
> > ## 3.3.6 Broadcasts
> ^^
> This is not the all 0's host value, but the all 1's host value,
> these rules are VERY well known and enforced. I am actually
> amazed that this use of 0 has not been RFC'ed out of existance,
> as far as I know all the other stuff says that the 0th host
> on a network is reserved for indicating the Network.
>
> If you look at all the tables on cidr and such they say
> the valid host ranges are 1 to (END - 1) Leaving out
> the host part value of 0.
>
Well, setting up point-to-point links for bgp and stuff it happens
frequently that /31s are used to conserve ip space, which is sort of
equivalent to having host ip of .0.
>
> > Section 3.2.1.3 defined the four standard IP broadcast address
> > forms:
> >Limited Broadcast: {-1, -1}
> >Directed Broadcast: {,-1}
> >Subnet Directed Broadcast:
> > {,,-1}
> >All-Subnets Directed Broadcast: {,-1,-1}
> > A host MUST recognize any of these forms in the destination
> > address of an incoming datagram.
> > There is a class of hosts* that use non-standard broadcast
> > address forms, substituting 0 for -1. All hosts SHOULD
> ^^
> > recognize and accept any of these non-standard broadcast
> ^^^
> > addresses as the destination address of an incoming datagram.
>
> Ok, so we *SHOULD* be mapping the 10.241.0.0 to 10.241.255.255 which
> should of caused ALL the hosts on that subnet to respond to the ping.
>
> Someone want to investiage linux on this one?
>
> > _
> > *4.2BSD Unix and its derivatives, but not 4.3BSD.
>
> --
> Rod Grimes
> rgri...@f
