You are not logged in.
Pages: 1
portmap[2718]: cannot bind udp: Permission denied
any ideas? and yes, I'm running it as root =P
[home page] -- [code / configs]
"Once you go Arch, you must remain there for life or else Allan will track you down and break you."
-- Bregol
Offline
what else is running? as in do you have anything running that could try to be in control of udp and not let portmap get it
Last edited by INCSlayer (2008-06-12 09:58:23)
dovie andi se tovya sagain
Offline
I had problems getting portmap to start, mine had to do with iptables. If you are running iptables, make sure you have a line like
iptables -A INPUT -s 127.0.0.1 -d 127.0.0.1 -j ACCEPT
near the top of your rules, or before you start REJECTing or DROPing anything that could effect udp traffic.
You would probably be ok with switching the "-A" to a "-I", which would insert that line to top of your iptables.rules file, which is ok, since it is just permitting traffic from your machine back to your machine, loopback interface...
Then
/etc/rc.d/iptables save
/etc/rc.d/iptables restart
If you don't use iptables... Idk.
Last edited by Sjoden (2008-06-12 17:07:25)
Offline
A slightly better way of doing that (so that you can't have someone spoofing 127.0.0.1 and getting a free ride in your system) is to set
iptables -A INPUT -i lo -j ACCEPT
and perhaps (depending on whether you have restricted output or not)
iptables -A OUTPUT -o lo -j ACCEPT
Of course, this assumes use of iptables.
Stop looking at my signature. It betrays your nature.
Offline
Moving to networking...
Offline
@Redroar, I think your command is better, but, I don't think there is much anyone could do. I guess they could send me a packet(s), hoping that the payload was something I was vulnerable too, but they would never get anything back.
I could be wrong though, idk.
,
Zack
Offline
Agh, not to hijack, but I was looking, I believe I would be just as safe with your 1 command, with my THREE commands.
-A INPUT -i eth0 -s 127.0.0.0/8 -j DROP
-A INPUT -i wlan0 -s 127.0.0.0/8 -j DROP
-A INPUT -s 127.0.0.1 -d 127.0.0.1 -j ACCEPT
-Zack
Eh, maybe not, from #iptables...
(11:49:20 PM) xSjoden: is "-A INPUT -s 127.0.0.1/32 -d 127.0.0.1/32 -j ACCEPT" considered unsafe, compared to "iptables -A INPUT -i lo -j ACCEPT"
(12:06:31 AM) poige: xSjoden, the first rule is simply silly
So... I'm using your way..
Last edited by Sjoden (2008-06-13 07:27:10)
Offline
Pages: 1