I am experiencing an annoying problem. First of all, I have got kernel panic only once - first time running sshuttle on 10.7.3, MBA with the latest firmware update. Now I have the following problem -- after I stop sshuttle (ctrl+c twice), or loose connection, e.g. close the lid, I cannot restore it until I restart the laptop. The restarting takes quite a time, much longer than it would normally take. Could you advice me how to restore sshuttle without restarting my laptop?
The command: ./sshuttle --dns -r and...@example.com 10.0.0.0/8 -vv
The last message I get trying to restore the connection: firewall manager: starting transproxy. s: Ready: 1 r=[4] w=[] x=[] s: < channel=0 cmd=PING len=7 s: > channel=0 cmd=PONG len=7 (fullness=554)
s: mux wrote: 15/15
s: Waiting: 1 r=[4] w=[] x=[] (fullness=561/0)
>> ipfw -q add 12300 check-state ip from any to any >> ipfw -q add 12300 skipto 12301 tcp from any to 127.0.0.0/8 >> ipfw -q add 12300 fwd 127.0.0.1,12300 tcp from any to 10.0.0.0/8 not
ipttl 42 keep-state setup
>> ipfw -q add 12300 divert 12300 udp from any to 10.0.1.1/32 53 not ipttl 42 >> ipfw -q add 12300 divert 12300 udp from any 12300 to any not ipttl 42
The sshuttle version: # git log commit 274ee854d4f05fd55a7c1c94e0ffb29bed8008eb Author: Avery Pennarun <apenwarr@**.*m> Date: Tue Feb 7 12:17:56 2012 -0500
> I am experiencing an annoying problem. First of all, I have got kernel panic only once - first time running sshuttle on 10.7.3, MBA with the latest firmware update. > Now I have the following problem -- after I stop sshuttle (ctrl+c twice), or loose connection, e.g. close the lid, I cannot restore it until I restart the laptop. The restarting takes quite a time, much longer than it would normally take. > Could you advice me how to restore sshuttle without restarting my laptop?
> The command: > ./sshuttle --dns -r and...@example.com 10.0.0.0/8 -vv
> The last message I get trying to restore the connection: > firewall manager: starting transproxy. > s: Ready: 1 r=[4] w=[] x=[] > s: < channel=0 cmd=PING len=7 > s: > channel=0 cmd=PONG len=7 (fullness=554) > s: mux wrote: 15/15 > s: Waiting: 1 r=[4] w=[] x=[] (fullness=561/0) >>> ipfw -q add 12300 check-state ip from any to any >>> ipfw -q add 12300 skipto 12301 tcp from any to 127.0.0.0/8 >>> ipfw -q add 12300 fwd 127.0.0.1,12300 tcp from any to 10.0.0.0/8 not ipttl 42 keep-state setup >>> ipfw -q add 12300 divert 12300 udp from any to 10.0.1.1/32 53 not ipttl 42 >>> ipfw -q add 12300 divert 12300 udp from any 12300 to any not ipttl 42
On Sunday, March 18, 2012 7:52:00 PM UTC+1, Luis wrote:
> Did you tried flush the ipfw rules?
> On Mar 17, 2012, at 4:14 AM, andrei.fokau wrote:
> > Hello,
> > I am experiencing an annoying problem. First of all, I have got kernel > panic only once - first time running sshuttle on 10.7.3, MBA with the > latest firmware update. > > Now I have the following problem -- after I stop sshuttle (ctrl+c > twice), or loose connection, e.g. close the lid, I cannot restore it until > I restart the laptop. The restarting takes quite a time, much longer than > it would normally take. > > Could you advice me how to restore sshuttle without restarting my laptop?
> > The last message I get trying to restore the connection: > > firewall manager: starting transproxy. > > s: Ready: 1 r=[4] w=[] x=[] > > s: < channel=0 cmd=PING len=7 > > s: > channel=0 cmd=PONG len=7 (fullness=554) > > s: mux wrote: 15/15 > > s: Waiting: 1 r=[4] w=[] x=[] (fullness=561/0) > >>> ipfw -q add 12300 check-state ip from any to any > >>> ipfw -q add 12300 skipto 12301 tcp from any to 127.0.0.0/8 > >>> ipfw -q add 12300 fwd 127.0.0.1,12300 tcp from any to 10.0.0.0/8 not > ipttl 42 keep-state setup > >>> ipfw -q add 12300 divert 12300 udp from any to 10.0.1.1/32 53 not > ipttl 42 > >>> ipfw -q add 12300 divert 12300 udp from any 12300 to any not ipttl 42
> On Sunday, March 18, 2012 7:52:00 PM UTC+1, Luis wrote: > Did you tried flush the ipfw rules? > On Mar 17, 2012, at 4:14 AM, andrei.fokau wrote:
> > Hello,
> > I am experiencing an annoying problem. First of all, I have got kernel panic only once - first time running sshuttle on 10.7.3, MBA with the latest firmware update. > > Now I have the following problem -- after I stop sshuttle (ctrl+c twice), or loose connection, e.g. close the lid, I cannot restore it until I restart the laptop. The restarting takes quite a time, much longer than it would normally take. > > Could you advice me how to restore sshuttle without restarting my laptop?
> > The last message I get trying to restore the connection: > > firewall manager: starting transproxy. > > s: Ready: 1 r=[4] w=[] x=[] > > s: < channel=0 cmd=PING len=7 > > s: > channel=0 cmd=PONG len=7 (fullness=554) > > s: mux wrote: 15/15 > > s: Waiting: 1 r=[4] w=[] x=[] (fullness=561/0) > >>> ipfw -q add 12300 check-state ip from any to any > >>> ipfw -q add 12300 skipto 12301 tcp from any to 127.0.0.0/8 > >>> ipfw -q add 12300 fwd 127.0.0.1,12300 tcp from any to 10.0.0.0/8 not ipttl 42 keep-state setup > >>> ipfw -q add 12300 divert 12300 udp from any to 10.0.1.1/32 53 not ipttl 42 > >>> ipfw -q add 12300 divert 12300 udp from any 12300 to any not ipttl 42
On Monday, March 19, 2012 10:42:39 PM UTC+1, andrei...@gmail.com wrote:
> Nope. How do I do that?
> Andrei
> On Sunday, March 18, 2012 7:52:00 PM UTC+1, Luis wrote:
>> Did you tried flush the ipfw rules?
>> On Mar 17, 2012, at 4:14 AM, andrei.fokau wrote:
>> > Hello,
>> > I am experiencing an annoying problem. First of all, I have got kernel >> panic only once - first time running sshuttle on 10.7.3, MBA with the >> latest firmware update. >> > Now I have the following problem -- after I stop sshuttle (ctrl+c >> twice), or loose connection, e.g. close the lid, I cannot restore it until >> I restart the laptop. The restarting takes quite a time, much longer than >> it would normally take. >> > Could you advice me how to restore sshuttle without restarting my >> laptop?
>> > The last message I get trying to restore the connection: >> > firewall manager: starting transproxy. >> > s: Ready: 1 r=[4] w=[] x=[] >> > s: < channel=0 cmd=PING len=7 >> > s: > channel=0 cmd=PONG len=7 (fullness=554) >> > s: mux wrote: 15/15 >> > s: Waiting: 1 r=[4] w=[] x=[] (fullness=561/0) >> >>> ipfw -q add 12300 check-state ip from any to any >> >>> ipfw -q add 12300 skipto 12301 tcp from any to 127.0.0.0/8 >> >>> ipfw -q add 12300 fwd 127.0.0.1,12300 tcp from any to 10.0.0.0/8 not >> ipttl 42 keep-state setup >> >>> ipfw -q add 12300 divert 12300 udp from any to 10.0.1.1/32 53 not >> ipttl 42 >> >>> ipfw -q add 12300 divert 12300 udp from any 12300 to any not ipttl 42
On Monday, March 19, 2012 10:48:05 PM UTC+1, Luis wrote:
> Try the following command:
> sudo ipfw -q -f flush
> On Mar 19, 2012, at 3:42 PM, andrei wrote:
> Nope. How do I do that?
> Andrei
> On Sunday, March 18, 2012 7:52:00 PM UTC+1, Luis wrote:
>> Did you tried flush the ipfw rules?
>> On Mar 17, 2012, at 4:14 AM, andrei.fokau wrote:
>> > Hello,
>> > I am experiencing an annoying problem. First of all, I have got kernel >> panic only once - first time running sshuttle on 10.7.3, MBA with the >> latest firmware update. >> > Now I have the following problem -- after I stop sshuttle (ctrl+c >> twice), or loose connection, e.g. close the lid, I cannot restore it until >> I restart the laptop. The restarting takes quite a time, much longer than >> it would normally take. >> > Could you advice me how to restore sshuttle without restarting my >> laptop?
>> > The last message I get trying to restore the connection: >> > firewall manager: starting transproxy. >> > s: Ready: 1 r=[4] w=[] x=[] >> > s: < channel=0 cmd=PING len=7 >> > s: > channel=0 cmd=PONG len=7 (fullness=554) >> > s: mux wrote: 15/15 >> > s: Waiting: 1 r=[4] w=[] x=[] (fullness=561/0) >> >>> ipfw -q add 12300 check-state ip from any to any >> >>> ipfw -q add 12300 skipto 12301 tcp from any to 127.0.0.0/8 >> >>> ipfw -q add 12300 fwd 127.0.0.1,12300 tcp from any to 10.0.0.0/8 not >> ipttl 42 keep-state setup >> >>> ipfw -q add 12300 divert 12300 udp from any to 10.0.1.1/32 53 not >> ipttl 42 >> >>> ipfw -q add 12300 divert 12300 udp from any 12300 to any not ipttl 42
> Thanks! Got my second kernel panic shortly after running it. :) But it didn't solve the problem. > I'll try with your fork to see if it helps.
> Andrei
> On Monday, March 19, 2012 10:48:05 PM UTC+1, Luis wrote: > Try the following command:
> sudo ipfw -q -f flush
> On Mar 19, 2012, at 3:42 PM, andrei wrote:
>> Nope. How do I do that?
>> Andrei
>> On Sunday, March 18, 2012 7:52:00 PM UTC+1, Luis wrote: >> Did you tried flush the ipfw rules? >> On Mar 17, 2012, at 4:14 AM, andrei.fokau wrote:
>> > Hello,
>> > I am experiencing an annoying problem. First of all, I have got kernel panic only once - first time running sshuttle on 10.7.3, MBA with the latest firmware update. >> > Now I have the following problem -- after I stop sshuttle (ctrl+c twice), or loose connection, e.g. close the lid, I cannot restore it until I restart the laptop. The restarting takes quite a time, much longer than it would normally take. >> > Could you advice me how to restore sshuttle without restarting my laptop?
>> > The last message I get trying to restore the connection: >> > firewall manager: starting transproxy. >> > s: Ready: 1 r=[4] w=[] x=[] >> > s: < channel=0 cmd=PING len=7 >> > s: > channel=0 cmd=PONG len=7 (fullness=554) >> > s: mux wrote: 15/15 >> > s: Waiting: 1 r=[4] w=[] x=[] (fullness=561/0) >> >>> ipfw -q add 12300 check-state ip from any to any >> >>> ipfw -q add 12300 skipto 12301 tcp from any to 127.0.0.0/8 >> >>> ipfw -q add 12300 fwd 127.0.0.1,12300 tcp from any to 10.0.0.0/8 not ipttl 42 keep-state setup >> >>> ipfw -q add 12300 divert 12300 udp from any to 10.0.1.1/32 53 not ipttl 42 >> >>> ipfw -q add 12300 divert 12300 udp from any 12300 to any not ipttl 42
On Monday, March 19, 2012 11:04:34 PM UTC+1, Luis wrote:
> I would recommend you to use that fork > is an older version but in my MacBook Pro runs stable.
> I hope it helps.
> Luis
> On Mar 19, 2012, at 3:58 PM, andrei.fokau wrote:
> Thanks! Got my second kernel panic shortly after running it. :) But it > didn't solve the problem. > I'll try with your fork to see if it helps.
> Andrei
> On Monday, March 19, 2012 10:48:05 PM UTC+1, Luis wrote:
>> Try the following command:
>> sudo ipfw -q -f flush
>> On Mar 19, 2012, at 3:42 PM, andrei wrote:
>> Nope. How do I do that?
>> Andrei
>> On Sunday, March 18, 2012 7:52:00 PM UTC+1, Luis wrote:
>>> Did you tried flush the ipfw rules?
>>> On Mar 17, 2012, at 4:14 AM, andrei.fokau wrote:
>>> > Hello,
>>> > I am experiencing an annoying problem. First of all, I have got kernel >>> panic only once - first time running sshuttle on 10.7.3, MBA with the >>> latest firmware update. >>> > Now I have the following problem -- after I stop sshuttle (ctrl+c >>> twice), or loose connection, e.g. close the lid, I cannot restore it until >>> I restart the laptop. The restarting takes quite a time, much longer than >>> it would normally take. >>> > Could you advice me how to restore sshuttle without restarting my >>> laptop?
I have tried sudo kill -9 2263 without success. I am guessing that after killing them I will be able to run sshuttle again. Is it correct and how do I kill them?
On Tuesday, March 20, 2012 8:03:45 AM UTC+1, andrei...@gmail.com wrote:
> Still having the original problem even with the old code.
> Andrei
> On Monday, March 19, 2012 11:04:34 PM UTC+1, Luis wrote:
>> I would recommend you to use that fork >> is an older version but in my MacBook Pro runs stable.
>> I hope it helps.
>> Luis
>> On Mar 19, 2012, at 3:58 PM, andrei.fokau wrote:
>> Thanks! Got my second kernel panic shortly after running it. :) But it >> didn't solve the problem. >> I'll try with your fork to see if it helps.
>> Andrei
>> On Monday, March 19, 2012 10:48:05 PM UTC+1, Luis wrote:
>>> Try the following command:
>>> sudo ipfw -q -f flush
>>> On Mar 19, 2012, at 3:42 PM, andrei wrote:
>>> Nope. How do I do that?
>>> Andrei
>>> On Sunday, March 18, 2012 7:52:00 PM UTC+1, Luis wrote:
>>>> Did you tried flush the ipfw rules?
>>>> On Mar 17, 2012, at 4:14 AM, andrei.fokau wrote:
>>>> > Hello,
>>>> > I am experiencing an annoying problem. First of all, I have got >>>> kernel panic only once - first time running sshuttle on 10.7.3, MBA with >>>> the latest firmware update. >>>> > Now I have the following problem -- after I stop sshuttle (ctrl+c >>>> twice), or loose connection, e.g. close the lid, I cannot restore it until >>>> I restart the laptop. The restarting takes quite a time, much longer than >>>> it would normally take. >>>> > Could you advice me how to restore sshuttle without restarting my >>>> laptop?
> I have tried sudo kill -9 2263 without success. I am guessing that after killing them I will be able to run sshuttle again. > Is it correct and how do I kill them?
> Andrei
> On Tuesday, March 20, 2012 8:03:45 AM UTC+1, andrei...@gmail.com wrote: > Still having the original problem even with the old code.
> Andrei
> On Monday, March 19, 2012 11:04:34 PM UTC+1, Luis wrote: > I would recommend you to use that fork > is an older version but in my MacBook Pro runs stable.
> I hope it helps.
> Luis
> On Mar 19, 2012, at 3:58 PM, andrei.fokau wrote:
>> Thanks! Got my second kernel panic shortly after running it. :) But it didn't solve the problem. >> I'll try with your fork to see if it helps.
>> Andrei
>> On Monday, March 19, 2012 10:48:05 PM UTC+1, Luis wrote: >> Try the following command:
>> sudo ipfw -q -f flush
>> On Mar 19, 2012, at 3:42 PM, andrei wrote:
>>> Nope. How do I do that?
>>> Andrei
>>> On Sunday, March 18, 2012 7:52:00 PM UTC+1, Luis wrote: >>> Did you tried flush the ipfw rules? >>> On Mar 17, 2012, at 4:14 AM, andrei.fokau wrote:
>>> > Hello,
>>> > I am experiencing an annoying problem. First of all, I have got kernel panic only once - first time running sshuttle on 10.7.3, MBA with the latest firmware update. >>> > Now I have the following problem -- after I stop sshuttle (ctrl+c twice), or loose connection, e.g. close the lid, I cannot restore it until I restart the laptop. The restarting takes quite a time, much longer than it would normally take. >>> > Could you advice me how to restore sshuttle without restarting my laptop?
>>> > The last message I get trying to restore the connection: >>> > firewall manager: starting transproxy. >>> > s: Ready: 1 r=[4] w=[] x=[] >>> > s: < channel=0 cmd=PING len=7 >>> > s: > channel=0 cmd=PONG len=7 (fullness=554) >>> > s: mux wrote: 15/15 >>> > s: Waiting: 1 r=[4] w=[] x=[] (fullness=561/0) >>> >>> ipfw -q add 12300 check-state ip from any to any >>> >>> ipfw -q add 12300 skipto 12301 tcp from any to 127.0.0.0/8 >>> >>> ipfw -q add 12300 fwd 127.0.0.1,12300 tcp from any to 10.0.0.0/8 not ipttl 42 keep-state setup >>> >>> ipfw -q add 12300 divert 12300 udp from any to 10.0.1.1/32 53 not ipttl 42 >>> >>> ipfw -q add 12300 divert 12300 udp from any 12300 to any not ipttl 42
> which error message do you receive when you try to kill the process?
> I have tried sudo kill -9 2263 without success. I am guessing that after > killing them I will be able to run sshuttle again. > Is it correct and how do I kill them?
> Andrei
> On Tuesday, March 20, 2012 8:03:45 AM UTC+1, andrei...@gmail.com wrote:
>> Still having the original problem even with the old code.
>> Andrei
>> On Monday, March 19, 2012 11:04:34 PM UTC+1, Luis wrote:
>>> I would recommend you to use that fork >>> is an older version but in my MacBook Pro runs stable.
>>> I hope it helps.
>>> Luis
>>> On Mar 19, 2012, at 3:58 PM, andrei.fokau wrote:
>>> Thanks! Got my second kernel panic shortly after running it. :) But it >>> didn't solve the problem. >>> I'll try with your fork to see if it helps.
>>> Andrei
>>> On Monday, March 19, 2012 10:48:05 PM UTC+1, Luis wrote:
>>>> Try the following command:
>>>> sudo ipfw -q -f flush
>>>> On Mar 19, 2012, at 3:42 PM, andrei wrote:
>>>> Nope. How do I do that?
>>>> Andrei
>>>> On Sunday, March 18, 2012 7:52:00 PM UTC+1, Luis wrote:
>>>>> Did you tried flush the ipfw rules?
>>>>> On Mar 17, 2012, at 4:14 AM, andrei.fokau wrote:
>>>>> > Hello,
>>>>> > I am experiencing an annoying problem. First of all, I have got >>>>> kernel panic only once - first time running sshuttle on 10.7.3, MBA with >>>>> the latest firmware update. >>>>> > Now I have the following problem -- after I stop sshuttle (ctrl+c >>>>> twice), or loose connection, e.g. close the lid, I cannot restore it until >>>>> I restart the laptop. The restarting takes quite a time, much longer than >>>>> it would normally take. >>>>> > Could you advice me how to restore sshuttle without restarting my >>>>> laptop?
On Saturday, March 17, 2012 11:14:08 AM UTC+1, andrei...@gmail.com wrote:
> Hello,
> I am experiencing an annoying problem. First of all, I have got kernel > panic only once - first time running sshuttle on 10.7.3, MBA with the > latest firmware update. > Now I have the following problem -- after I stop sshuttle (ctrl+c twice), > or loose connection, e.g. close the lid, I cannot restore it until I > restart the laptop. The restarting takes quite a time, much longer than it > would normally take. > Could you advice me how to restore sshuttle without restarting my laptop?
> The command: > ./sshuttle --dns -r and...@example.com 10.0.0.0/8 -vv
> The last message I get trying to restore the connection: > firewall manager: starting transproxy. > s: Ready: 1 r=[4] w=[] x=[] > s: < channel=0 cmd=PING len=7 > s: > channel=0 cmd=PONG len=7 (fullness=554) > s: mux wrote: 15/15 > s: Waiting: 1 r=[4] w=[] x=[] (fullness=561/0) > >> ipfw -q add 12300 check-state ip from any to any > >> ipfw -q add 12300 skipto 12301 tcp from any to 127.0.0.0/8 > >> ipfw -q add 12300 fwd 127.0.0.1,12300 tcp from any to 10.0.0.0/8 not > ipttl 42 keep-state setup > >> ipfw -q add 12300 divert 12300 udp from any to 10.0.1.1/32 53 not > ipttl 42 > >> ipfw -q add 12300 divert 12300 udp from any 12300 to any not ipttl 42
> I am experiencing an annoying problem. First of all, I have got kernel > panic only once - first time running sshuttle on 10.7.3, MBA with the > latest firmware update. > Now I have the following problem -- after I stop sshuttle (ctrl+c twice), > or loose connection, e.g. close the lid, I cannot restore it until I > restart the laptop. The restarting takes quite a time, much longer than it > would normally take. > Could you advice me how to restore sshuttle without restarting my laptop?
> The command: > ./sshuttle --dns -r and...@example.com 10.0.0.0/8 -vv
> The last message I get trying to restore the connection: > firewall manager: starting transproxy. > s: Ready: 1 r=[4] w=[] x=[] > s: < channel=0 cmd=PING len=7 > s: > channel=0 cmd=PONG len=7 (fullness=554) > s: mux wrote: 15/15 > s: Waiting: 1 r=[4] w=[] x=[] (fullness=561/0) > >> ipfw -q add 12300 check-state ip from any to any > >> ipfw -q add 12300 skipto 12301 tcp from any to 127.0.0.0/8 > >> ipfw -q add 12300 fwd 127.0.0.1,12300 tcp from any to 10.0.0.0/8 not > ipttl 42 keep-state setup > >> ipfw -q add 12300 divert 12300 udp from any to 10.0.1.1/32 53 not > ipttl 42 > >> ipfw -q add 12300 divert 12300 udp from any 12300 to any not ipttl 42
On Saturday, March 17, 2012 11:14:08 AM UTC+1, andrei...@gmail.com wrote:
> Hello,
> I am experiencing an annoying problem. First of all, I have got kernel > panic only once - first time running sshuttle on 10.7.3, MBA with the > latest firmware update. > Now I have the following problem -- after I stop sshuttle (ctrl+c twice), > or loose connection, e.g. close the lid, I cannot restore it until I > restart the laptop. The restarting takes quite a time, much longer than it > would normally take. > Could you advice me how to restore sshuttle without restarting my laptop?
> The command: > ./sshuttle --dns -r and...@example.com 10.0.0.0/8 -vv
> The last message I get trying to restore the connection: > firewall manager: starting transproxy. > s: Ready: 1 r=[4] w=[] x=[] > s: < channel=0 cmd=PING len=7 > s: > channel=0 cmd=PONG len=7 (fullness=554) > s: mux wrote: 15/15 > s: Waiting: 1 r=[4] w=[] x=[] (fullness=561/0) > >> ipfw -q add 12300 check-state ip from any to any > >> ipfw -q add 12300 skipto 12301 tcp from any to 127.0.0.0/8 > >> ipfw -q add 12300 fwd 127.0.0.1,12300 tcp from any to 10.0.0.0/8 not > ipttl 42 keep-state setup > >> ipfw -q add 12300 divert 12300 udp from any to 10.0.1.1/32 53 not > ipttl 42 > >> ipfw -q add 12300 divert 12300 udp from any 12300 to any not ipttl 42
On Mon, Sep 3, 2012 at 1:03 PM, Kyle Jensen <kljen...@gmail.com> wrote:
> Andrei - I did not find that to be the case. Still stuck with
> unkillable processes in the "waiting" state. I tried disabling the os
> x firewall and also setting a global timeout in the socket module,
> both to no avail.
> -Kyle
> On Mon, Sep 3, 2012 at 3:00 AM, <andrei.fo...@gmail.com> wrote:
> > Yes, somehow resolved with 9ce2fa0 (or earlier commit).
> > - Andrei
> > On Tuesday, July 17, 2012 9:28:35 PM UTC+2, klje...@gmail.com wrote:
> >> Any progress here? Same issue on OS X Lion.
> >> -Kyle
