* On 2017-01-20 at 13:35 GMT, Zettabytes wrote: > In a non-global zone I have passed through /dev/e1000g so that I can > connect to my ISP via PPPoE. The connection initiates fine and > everything works as expected within that zone. net0 is given the > address 172.16.0.254 so that it can act as a gateway for my lan with > ipnat mapping appropriately. I have ip_spoofing set, ipv4-forwarding > and route enabled in the gateway zone. > > If I create another NGZ using 172.16.0.254 as the gateway I start > running into problems inside that NGZ, for example "pkgin update" > hangs, I cannot get full results via whois etc. > > Web browsing on my windows machine is also problematic when using > 172.16.0.254 as the gateway. Some webpages load fine, some partially > load and then take ages to complete, some don't load at all, some > time out and then all of a sudden load etc, I also see tracert > requests timing out on the windows machine. > > Not sure what I should be looking at next to remedy this.
I do the same thing with my SmartOS server, documented here FWIW: https://gist.github.com/jperkin/7717d3e84e93885ab14da3bce3039f4b Sounds like MTU issues so check that it is set correctly to what your ISP expects. Unfortunately we do not support a full 1500 MTU over PPP interfaces yet, so you are limited to 1492, but this is something I want to look at some time (requires an update to the pppd we ship and a few small kernel changes). -- Jonathan Perkin - Joyent, Inc. - www.joyent.com ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
