Reputation
5,386
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
28 74 121
Impact
~1.2m people reached

2d
awarded  Nice Question
Jul
27
awarded  Popular Question
Jul
13
comment How can I ignore / remove / exclude autocompletions in zsh?
awesome - thank you. I knew it wasn't difficult in theory but was having a hard time finding an example of how to do this. ps: (for others) I did change rsyslog to rsyslogd
Jul
13
accepted How can I ignore / remove / exclude autocompletions in zsh?
Jul
13
comment How can I ignore / remove / exclude autocompletions in zsh?
@jasonwryan - still confused - how would one use that to accomplish ignoring rsh and rsyslogd ?
Jul
13
asked How can I ignore / remove / exclude autocompletions in zsh?
Jul
7
awarded  Popular Question
Jul
1
awarded  Good Question
Jun
22
awarded  Good Question
Jun
18
awarded  Good Question
Jun
11
awarded  Famous Question
Jun
9
awarded  Famous Question
Jun
8
awarded  Popular Question
Jun
6
accepted How can I redirect all UDP traffic from one port to another on BSD / OS X?
Jun
5
awarded  Good Question
Jun
5
comment How can I redirect all UDP traffic from one port to another on BSD / OS X?
+1 this looks like a great option. I haven't had time to try it yet. reminds me of the udp-reflector although that didn't look like it had much activity or support for os x. thanks so much
May
31
comment How can I redirect all UDP traffic from one port to another on BSD / OS X?
@FloHimself - thank you. thant helps a lot. maybe it worked with only UDP 69 open in my linux tests because I was using less than 512 bytes of data. Anyhow, also found on this man page it looks like one option is to use -R port:port - Force the originating port number to be in the specified range of port numbers. - but I still need to figure out how to forward UDP traffic on OS X / BSD.
May
30
comment How can I redirect all UDP traffic from one port to another on BSD / OS X?
@FloHimself - Thank you for the link to the RFC. I read over the entire thing. The way I understand the spec is basically that the server will listen on UDP port 69 by default, but the client may be connecting from a different port. At one end of the connection the TID will thus include port 69, but the other TID can include a different port. Once the two TIDs are established they are "used for the duration of that connection"
May
29
comment How can I redirect all UDP traffic from one port to another on BSD / OS X?
@FloHimself - I can access tftpd from OS X but want to allow access from another machine on the network. I have looked at setting up an additional network interface in Virtualbox in bridged mode but it will expose all ports instead of just the single port that I'd like to expose, which then will require some sort of a firewall or at least changing the default password on boot2docker as this isn't (arguably) the way it was designed to be used. Also I'd like like to know how to be able to mirror / port forward UDP on OS X, because I think that socat command will work with most linux distros.
May
28
revised How can I redirect all UDP traffic from one port to another on BSD / OS X?
added 3 characters in body