[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062 tsuroer...@gmail.com changed: What|Removed |Added CC||tsuroer...@gmail.com --- Comment #12 from tsuroer...@gmail.com --- I have just run into this problem on FreeBSD 11.2 for one of my use cases. Has this problem of VFs not attaching been fixed in 11-STABLE for 11.3, 12.0-RELEASE or 12-STABLE? -- 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 237649] Does not work receiving an IP address via DHCP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237649 --- Comment #3 from Vladislav V. Prodan --- After updating the world to r347140, dhclient starts from the console. But still "SYNCDHCP" and "DHCP" in rc.conf do not work. It comes from /etc/rc.local: " sleep 30 dhclient bce0 " -- 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 237649] Does not work receiving an IP address via DHCP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237649 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org --- Comment #4 from Eugene Grosbein --- Use seems to use custom kernel and its configuration appears to miss driver for ix. ifconfig loads driver for you. Make sure you load driver with /boot/loader.conf so dhclient would find the interface. Also, manual ifconfig invocation seemingly brings the interface UP. Make sure you have corresponding "ifconfig_ifname" configuration lines in /etc/rc.conf for every interface you use. If this does not help, try using GENERIC kernel first and double-check your local changes. Try disabling them all and test with GENERIC and clean config first. -- 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 237649] Does not work receiving an IP address via DHCP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237649 --- Comment #5 from Vladislav V. Prodan --- Network drivers are built into the kernel: # kldstat -v | egrep '/(ix|bce)' 178 pci/ix 630 pci/ixl 99 pci/bce 179 pci/ixv Now I tried to change the guidelines for using DHCP in rc.conf. It was: ifconfig_DEFAULT="SYNCDHCP" ifconfig_bce0="DHCP" ifconfig_bce0_ipv6="inet6 accept_rtadv" ifconfig_bce1="DHCP" ipv6_activate_all_interfaces="YES" ifconfig_ix0="DHCP" ifconfig_bce0="mtu 9000 up" ifconfig_bce1="mtu 9000 up" ifconfig_bce2="mtu 9000 up" ifconfig_bce3="mtu 9000 up" ifconfig_igb0="mtu 9210 up" ifconfig_igb1="mtu 9210 up" ifconfig_ix0="mtu 9710 up descr 'Juniper qfx3500' " ifconfig_ix1="mtu 9710 up" It became: ifconfig_bce0="mtu 9000 up" ifconfig_bce1="mtu 9000 up" ifconfig_bce2="mtu 9000 up" ifconfig_bce3="mtu 9000 up" ifconfig_igb0="mtu 9210 up" ifconfig_igb1="mtu 9210 up" ifconfig_ix0="mtu 9710 up descr 'Juniper qfx3500' " ifconfig_ix1="mtu 9710 up" ifconfig_DEFAULT="SYNCDHCP" ifconfig_bce0="DHCP" ifconfig_bce0_ipv6="inet6 accept_rtadv" ifconfig_bce1="DHCP" ipv6_activate_all_interfaces="YES" ifconfig_ix0="DHCP" With this latest version of the rc.conf file, DHCP is working in rc.conf. # ps -auxww | grep dhc root 529990,0 0,0 11388 2704 - Is 20:340:00,00 dhclient: system.syslog (dhclient) root 543380,0 0,0 11692 2792 - Is 20:340:00,00 dhclient: bce0 [priv] (dhclient) _dhcp 816770,0 0,0 11860 2916 - ICs 20:340:00,00 dhclient: bce0 (dhclient) root 898350,0 0,0 11400 2708 - Is 20:340:00,00 dhclient: system.syslog (dhclient) root 917870,0 0,0 11688 2792 - Is 20:340:00,00 dhclient: ix0 [priv] (dhclient) _dhcp 929220,0 0,0 11692 2800 - ICs 20:350:00,00 dhclient: ix0 (dhclient) root 29250,0 0,0 11464 2912 0 S+ 20:350:00,00 grep --color=auto dhc It turns out a number of ifconfig options in rc.conf is not commutative and depends on the order of the call/assignment. -- 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 237649] Does not work receiving an IP address via DHCP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237649 Eugene Grosbein changed: What|Removed |Added Resolution|--- |Not A Bug Status|New |Closed --- Comment #6 from Eugene Grosbein --- As documented in rc.conf(5) manual page: > Options are set with "name=value" assignments that use sh(1) syntax So you should not duplicate assignment as later override previous ones. -- 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"
In freshly installed 12i386 VM dhclient printed "No buffer space available"
I just took the latest 12i386 ISO image, installed into a VM with 2GB memory, and got the "No buffer space available" from dhclient during the initial IPv4 network setup. This should never happen, IMO. 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"
[Bug 237649] Does not work receiving an IP address via DHCP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237649 Vladislav V. Prodan changed: What|Removed |Added Status|Closed |New Resolution|Not A Bug |--- --- Comment #7 from Vladislav V. Prodan --- Here it is not necessary to close PR without understanding it. The first message clearly shows that both the 'SYNCDHCP' and 'DHCP' options have stopped working. In my last post you can see that these options work, first, you need to initialize the network interfaces, through "UP" The problem occurred somewhere due to commits in the last 20 days. -- 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"
Problem reports for n...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- In Progress |221146 | [ixgbe] Problem with second laggport In Progress |235700 | oce(4) driver causes fatal trap 12 on boot with e New |204438 | setsockopt() handling of kern.ipc.maxsockbuf limi New |205592 | TCP processing in IPSec causes kernel panic New |213410 | [carp] service netif restart causes hang only whe Open|193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc Open|194485 | Userland cannot add IPv6 prefix routes Open|200319 | Bridge+CARP crashes/freezes Open|202510 | [CARP] advertisements sourced from CARP IP cause Open|73 | igb(4): Kernel panic (fatal trap 12) due to netwo Open|227720 | Kernel panic in ppp server Open|233952 | jme NICs non functional after 11.2 to 12.0 upgrad Open|233955 | [panic] Page fault in in6_purgeaddr upon tun crea Open|236888 | ppp daemon: Allow MTU to be overridden for PPPoE Open|236983 | bnxt(4) VLAN not operational unless explicit "ifc Open|237072 | netgraph(4): performance issue [on HardenedBSD]? Open|237329 | Panic in mld_fasttimo() during reboot or shutdown Open|237391 | route get returns no result for network addresses 18 problems total for which you should take action. ___ 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: In freshly installed 12i386 VM dhclient printed "No buffer space available"
> I just took the latest 12i386 ISO image, installed into a VM with 2GB > memory, and got the "No buffer space available" from dhclient during the > initial IPv4 network setup. > > This should never happen, IMO. The i386 tuneparameters have seriuosly degraded due to lack of love by the developers. > Yuri -- 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"
Re: In freshly installed 12i386 VM dhclient printed "No buffer space available"
On 5 May 2019, at 19:06, Yuri wrote: I just took the latest 12i386 ISO image, installed into a VM with 2GB memory, and got the "No buffer space available" from dhclient during the initial IPv4 network setup. This should never happen, IMO. Which NIC is this? em0 or virtio? I do see this on a Laptop with em0; just wondering if this is an iflib problem? /bz ___ 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: In freshly installed 12i386 VM dhclient printed "No buffer space available"
On 2019-05-05 14:51, Bjoern A. Zeeb wrote: Which NIC is this? em0 or virtio? I do see this on a Laptop with em0; just wondering if this is an iflib problem? It's in a VirtualBox VM, by default it is em0. 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"
