[Bug 197265] [mii] patch to support rtl8211f ethernet phys
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197265 --- Comment #3 from Pyun YongHyeon --- Created attachment 154127 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=154127&action=edit Patch for RTL8211F PHY -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 197265] [mii] patch to support rtl8211f ethernet phys
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197265 --- Comment #4 from Pyun YongHyeon --- Thanks for the patch. I didn't test your patch on real H/W yet but patch looks good to me. To improve readability I've slightly reorganized your patch and regenerated it against HEAD. One difference against your diff is direct access of RGEPHY_F_MII_SSR register in MII_TICK handler. I wanted to remove RGEPHY_MII_BMSR, RGEPHY_MII_BMCR register accesses in the handler and rely on RGEPHY_F_MII_SSR or RGEPHY_MII_SSR register for non-re(4) drivers. Of course this assumes RGEPHY_F_MII_SSR reports correct link state in various timings. Would you try attached patch and let me know how it goes? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FreeBSD responding with wrong receiving interface IP
On 10 Mar 2015, at 11:26, Paul S. wrote: Hi, I've been deploying FreeBSD as customer edge routers for customers with sites that do not require high throughput (>1g/s). Each site has two ISPs (Mostly Telstra + Verizon/Optus), and take full routes via OpenBGPd and BIRD. I use next-hop self on all received routes. The FreeBSD boxes have static routes delegating the announced IP blocks to a L3 switch down the road. i.e: route add -net 10.100.1.0/24 10.0.0.1, and then that /24 is originated via BGP to both upstreams. Things in general work fine, but I've been receiving reports of 'weird traceroute results' from my customers. Examples of this would be, 1 some.random.isp (...) (...) 2 gigabitethernet3-3.exi1.melbourne.telstra.net (203.50.77.49) 0.309 ms 0.284 ms 0.227 ms 3 bundle-ether3-100.exi-core10.melbourne.telstra.net (203.50.80.1) 1.966 ms 1.675 ms 1.852 ms 4 bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124) 16.707 ms 15.917 ms 16.360 ms 5 customer-gw.syd.ALTER.net (...) (...) This traceroute seems to claim that the packet was received over the Verizon gateway, which in reality it was not -- it was received directly over the Telstra interface, but my outbound AS-PATH towards some.random.isp uses Verizon. So FreeBSD replies back with the Verizon address. Another person having the same issue (mostly, but on OpenBSD) can be found at http://openbsd.7691.n7.nabble.com/BGP-responding-with-wrong-IP-address-td90264.html I would love to know if there's a way to fix this, or if I've missed something, or if there's something wrong in the way I set it up. Thank you for taking the time to read. I wonder if we could see some routing tables? That might help. Best, George ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FreeBSD responding with wrong receiving interface IP
On 10/03/2015 13:16, George Neville-Neil wrote: On 10 Mar 2015, at 11:26, Paul S. wrote: Hi, I've been deploying FreeBSD as customer edge routers for customers with sites that do not require high throughput (>1g/s). Each site has two ISPs (Mostly Telstra + Verizon/Optus), and take full routes via OpenBGPd and BIRD. I use next-hop self on all received routes. The FreeBSD boxes have static routes delegating the announced IP blocks to a L3 switch down the road. i.e: route add -net 10.100.1.0/24 10.0.0.1, and then that /24 is originated via BGP to both upstreams. Things in general work fine, but I've been receiving reports of 'weird traceroute results' from my customers. Examples of this would be, 1 some.random.isp (...) (...) 2 gigabitethernet3-3.exi1.melbourne.telstra.net (203.50.77.49) 0.309 ms 0.284 ms 0.227 ms 3 bundle-ether3-100.exi-core10.melbourne.telstra.net (203.50.80.1) 1.966 ms 1.675 ms 1.852 ms 4 bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124) 16.707 ms 15.917 ms 16.360 ms 5 customer-gw.syd.ALTER.net (...) (...) This traceroute seems to claim that the packet was received over the Verizon gateway, which in reality it was not -- it was received directly over the Telstra interface, but my outbound AS-PATH towards some.random.isp uses Verizon. So FreeBSD replies back with the Verizon address. Another person having the same issue (mostly, but on OpenBSD) can be found at http://openbsd.7691.n7.nabble.com/BGP-responding-with-wrong-IP-address-td90264.html I would love to know if there's a way to fix this, or if I've missed something, or if there's something wrong in the way I set it up. Thank you for taking the time to read. I wonder if we could see some routing tables? That might help. Best, George sysctl net.inet.icmp.reply_from_interface=1 will probably do what you expect. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FreeBSD responding with wrong receiving interface IP
Joe, That was it, thank you! I looked over net.inet.ip and ip6, icmp never crossed my mind. George, thank you as well. On 3/10/2015 午後 11:40, Joe Holden wrote: On 10/03/2015 13:16, George Neville-Neil wrote: On 10 Mar 2015, at 11:26, Paul S. wrote: Hi, I've been deploying FreeBSD as customer edge routers for customers with sites that do not require high throughput (>1g/s). Each site has two ISPs (Mostly Telstra + Verizon/Optus), and take full routes via OpenBGPd and BIRD. I use next-hop self on all received routes. The FreeBSD boxes have static routes delegating the announced IP blocks to a L3 switch down the road. i.e: route add -net 10.100.1.0/24 10.0.0.1, and then that /24 is originated via BGP to both upstreams. Things in general work fine, but I've been receiving reports of 'weird traceroute results' from my customers. Examples of this would be, 1 some.random.isp (...) (...) 2 gigabitethernet3-3.exi1.melbourne.telstra.net (203.50.77.49) 0.309 ms 0.284 ms 0.227 ms 3 bundle-ether3-100.exi-core10.melbourne.telstra.net (203.50.80.1) 1.966 ms 1.675 ms 1.852 ms 4 bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124) 16.707 ms 15.917 ms 16.360 ms 5 customer-gw.syd.ALTER.net (...) (...) This traceroute seems to claim that the packet was received over the Verizon gateway, which in reality it was not -- it was received directly over the Telstra interface, but my outbound AS-PATH towards some.random.isp uses Verizon. So FreeBSD replies back with the Verizon address. Another person having the same issue (mostly, but on OpenBSD) can be found at http://openbsd.7691.n7.nabble.com/BGP-responding-with-wrong-IP-address-td90264.html I would love to know if there's a way to fix this, or if I've missed something, or if there's something wrong in the way I set it up. Thank you for taking the time to read. I wonder if we could see some routing tables? That might help. Best, George sysctl net.inet.icmp.reply_from_interface=1 will probably do what you expect. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 197790] Intel em driver - random outgoing traffic sent through wrong interface
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197790 Hiren Panchasara changed: What|Removed |Added CC||e...@freebsd.org --- Comment #1 from Hiren Panchasara --- (In reply to vladimir.nikolic from comment #0) Everything works until "server restart" and then it switches to wrong default gateway? What do you mean by "server restart"? Also, "Reset helps" as you said. What do you mean by that? Reboot? or kldloading/unloading drivers? Adding Eric from Intel. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 197790] Intel em driver - random outgoing traffic sent through wrong interface
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197790 --- Comment #2 from vladimir.niko...@amis.net --- By 'reset' I meant reboot of server. We have 'em' driver compiled into kernel, so unloading driver is not an option. I've already downgrade one server to FreeBSD 9.3 and virtualized the other one on VMware esxi host (FreeBSD 10.1 remained). It's interesting that vmware 'emulate' em driver, but 'routing' error has disappeared. Maybe I need to upgrade firmware on network cards? Regards, Vladimir Nikolic -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 197265] [mii] patch to support rtl8211f ethernet phys
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197265 --- Comment #5 from j...@feith.com --- In a quick smoke test of cycling through the various ifconfig media / mediaopt options your patch seems fine. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"