Re: MTU not regrowing?
On 07/02/14 04:53, John-Mark Gurney wrote: How do I do this? I tried route delete, but it doesn't help. route change -mtu XXX routetochange This does not work: the route is deemed as non-existent. bye thanks av. P.S. I'm writing this more out of curiosity, than of real need; no need to solve this, really. ___ 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: MTU not regrowing?
On 06/25/14 15:23, Andrea Venturoli wrote: On 06/25/14 02:01, Charles Swiger wrote: Does ifconfig vlan3 down; ifconfig vlan3 up do any good? Or that run against the physical NIC? None of the two. John was right about the route. bye Thanks av. ___ 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: MTU not regrowing?
On 06/24/14 21:03, John Hay wrote: Do a route get somehost and see what mtu is returned. You are right, I see a route with the old, lesser MTU. You might be able to delete or tweak that route. How do I do this? I tried route delete, but it doesn't help. bye Thanks av. ___ 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: MTU not regrowing?
Andrea Venturoli wrote this message on Tue, Jul 01, 2014 at 20:37 +0200: On 06/24/14 21:03, John Hay wrote: Do a route get somehost and see what mtu is returned. You are right, I see a route with the old, lesser MTU. You might be able to delete or tweak that route. How do I do this? I tried route delete, but it doesn't help. route change -mtu XXX routetochange If you delete all the routes associated w/ the interface, the network route should be recreated iirc.. Or just run the above change command on all the necessary routes that have the incorrect mtu.. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ 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: MTU not regrowing?
On 06/25/14 02:01, Charles Swiger wrote: Does ifconfig vlan3 down; ifconfig vlan3 up do any good? Or that run against the physical NIC? Can't try this now, I'll do when I can play again with this box. What is the ethernet HW em0@pci0:6:0:0: class=0x02 card=0x10828086 chip=0x107d8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/1000 PT' class = network subclass = ethernet and are you using VLAN_HWTAGGING capability? Yes. bye Thanks av. ___ 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
MTU not regrowing?
Hello. Today I experienced something weird (at least for me) on a 8.4 system: _ the system had vlan3 interface, with default MTU (1500 bytes); _ ping -D -s 1400 somehost would work, but ping -D -s 1500 somehost would yield frag needed and DF set (forgive me if the message is not exact, I don't have it anymore); _ to make some tests I reduced MTU size with ifconfig vlan3 mtu 500; _ now, of course, ping -D -s 400 somehost would work, but ping -D -s 500 somehost would yield frag needed and DF set; _ then I raised MTU again with ifconfig vlan3 mtu 1500 (notice ifconfig would actually report this as mtu 1500 was shown); _ however the results were as before, i.e. ping -D -s 400 somehost would work, but ping -D -s 500 somehost would yield frag needed and DF set; _ no way I could ping with a packet bigger than 500 bytes until I rebooted. Is this expected behaviour? Any way to get around this? bye Thanks av. ___ 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: MTU not regrowing?
don't forget the header of the ping. the -s flag specifies the amount of data that the ping carries. By specifying a size of 500, you are creating a ping packet larger than the MTU. On 24 June 2014 19:43, Andrea Venturoli m...@netfence.it wrote: Hello. Today I experienced something weird (at least for me) on a 8.4 system: _ the system had vlan3 interface, with default MTU (1500 bytes); _ ping -D -s 1400 somehost would work, but ping -D -s 1500 somehost would yield frag needed and DF set (forgive me if the message is not exact, I don't have it anymore); _ to make some tests I reduced MTU size with ifconfig vlan3 mtu 500; _ now, of course, ping -D -s 400 somehost would work, but ping -D -s 500 somehost would yield frag needed and DF set; _ then I raised MTU again with ifconfig vlan3 mtu 1500 (notice ifconfig would actually report this as mtu 1500 was shown); _ however the results were as before, i.e. ping -D -s 400 somehost would work, but ping -D -s 500 somehost would yield frag needed and DF set; _ no way I could ping with a packet bigger than 500 bytes until I rebooted. Is this expected behaviour? Any way to get around this? bye Thanks av. ___ 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 -- Carlos Miguel Ferreira Researcher at Telecommunications Institute Aveiro - Portugal Work E-mail - c...@av.it.pt Skype GTalk - carlosmf...@gmail.com LinkedIn - http://www.linkedin.com/in/carlosmferreira ___ 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: MTU not regrowing?
On Tue, Jun 24, 2014 at 11:43 AM, Andrea Venturoli m...@netfence.it wrote: _ the system had vlan3 interface, with default MTU (1500 bytes); _ ping -D -s 1400 somehost would work, but ping -D -s 1500 somehost would yield frag needed and DF set (forgive me if the message is not exact, I don't have it anymore); Does your interface support hardware VLAN tagging? (i.e. does an ifconfig show VLAN_HWTAGGING?) - M × ___ 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: MTU not regrowing?
On Tue, Jun 24, 2014 at 08:43:28PM +0200, Andrea Venturoli wrote: Hello. Today I experienced something weird (at least for me) on a 8.4 system: _ the system had vlan3 interface, with default MTU (1500 bytes); _ ping -D -s 1400 somehost would work, but ping -D -s 1500 somehost would yield frag needed and DF set (forgive me if the message is not exact, I don't have it anymore); _ to make some tests I reduced MTU size with ifconfig vlan3 mtu 500; _ now, of course, ping -D -s 400 somehost would work, but ping -D -s 500 somehost would yield frag needed and DF set; _ then I raised MTU again with ifconfig vlan3 mtu 1500 (notice ifconfig would actually report this as mtu 1500 was shown); _ however the results were as before, i.e. ping -D -s 400 somehost would work, but ping -D -s 500 somehost would yield frag needed and DF set; _ no way I could ping with a packet bigger than 500 bytes until I rebooted. Is this expected behaviour? Any way to get around this? Do a route get somehost and see what mtu is returned. You might be able to delete or tweak that route. John -- John Hay -- j...@meraka.csir.co.za / j...@meraka.org.za ___ 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: MTU not regrowing?
On 06/24/14 21:03, John Hay wrote: Do a route get somehost and see what mtu is returned. You might be able to delete or tweak that route. Thanks a lot! I learned something new :) I'll try this next time I have the chance. bye av. ___ 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: MTU not regrowing?
Hi-- On Jun 24, 2014, at 11:43 AM, Andrea Venturoli m...@netfence.it wrote: Hello. Today I experienced something weird (at least for me) on a 8.4 system: _ the system had vlan3 interface, with default MTU (1500 bytes); _ ping -D -s 1400 somehost would work, but ping -D -s 1500 somehost would yield frag needed and DF set (forgive me if the message is not exact, I don't have it anymore); _ to make some tests I reduced MTU size with ifconfig vlan3 mtu 500; _ now, of course, ping -D -s 400 somehost would work, but ping -D -s 500 somehost would yield frag needed and DF set; _ then I raised MTU again with ifconfig vlan3 mtu 1500 (notice ifconfig would actually report this as mtu 1500 was shown); _ however the results were as before, i.e. ping -D -s 400 somehost would work, but ping -D -s 500 somehost would yield frag needed and DF set; _ no way I could ping with a packet bigger than 500 bytes until I rebooted. Is this expected behaviour? Any way to get around this? Does ifconfig vlan3 down; ifconfig vlan3 up do any good? Or that run against the physical NIC? What is the ethernet HW; and are you using VLAN_HWTAGGING capability? Regards, -- -Chuck ___ 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: MTU not regrowing?
Andrea Venturoli wrote this message on Tue, Jun 24, 2014 at 20:43 +0200: Today I experienced something weird (at least for me) on a 8.4 system: _ the system had vlan3 interface, with default MTU (1500 bytes); _ ping -D -s 1400 somehost would work, but ping -D -s 1500 somehost would yield frag needed and DF set (forgive me if the message is not exact, I don't have it anymore); _ to make some tests I reduced MTU size with ifconfig vlan3 mtu 500; _ now, of course, ping -D -s 400 somehost would work, but ping -D -s 500 somehost would yield frag needed and DF set; _ then I raised MTU again with ifconfig vlan3 mtu 1500 (notice ifconfig would actually report this as mtu 1500 was shown); _ however the results were as before, i.e. ping -D -s 400 somehost would work, but ping -D -s 500 somehost would yield frag needed and DF set; _ no way I could ping with a packet bigger than 500 bytes until I rebooted. Is this expected behaviour? Any way to get around this? This is expected behavior.. You need to delete the network route as that stores the MTU that is cloned to the host routes... HEAD and I believe 10 doesn't have this issue.. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ 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
