| |
| |
| |
|
Comments:
<0> Hello! I wanna help for configuring oidentd on FC4 router.
<0> Hello! Someone know oidentd well?
<1> gug
<1> Emmanuel_Chanel, well not that well but
<0> Oh... xkr47 : you mean that you will help me?
<1> well you can try to ask at least :)
<1> I've used it sometimes
<1> think it worked fine
<0> oidetd -mq -u nobody -g nobody -o UNIX -f 112 -r default
<0> on my router respond only "default" when I access PC behind the firewall.
<0> It doesn't read oidentd.users or oidentd_masq.conf , or forward the request to the PC.
<0> On this PC,
<0> oidentd -q -u nobody -g nobody -o UNIX --proxy=192.168.0.1
<0> is working.
<0> I use iptables on FC4 on the router.
<0> What shall I do? I've commanded chomod +r /proc/net/ip_conntrack
<0> Do you know the adequete channel?
<0> I couldn't see good documentations when I thought the info.
<0> So I scream "Help me!", reminded me of Tru Calling.
<0> Hello!
<0> Hello! Someone alive?
<2> gug
<3> hi
<3> any hints where to go if one thinks to have found a bug in the tcp implementation? (apparently a lost segment doesn't get retransmitted ...)
<2> the netdev mailing list maybe?
<3> Hidden: that's where to be found? google? =:-)
<4> netdev@vger.kernel.org
<3> ah, IC
<5> LaF0rge: In a decent distro, yaboot.conf would have been marked as config file so the packaging system would not mess with it unless told so ;-)
<5> (hmm, thinking about it, I think even gentoo has that sort of conffile handling, so a packaging bug then maybe..)
<4> trippeh: oh, it wasn't yaboot.conf
<4> trippeh: it's the actual bootscript that got overwritten
<5> I'd probably want that as a conffile protection too :-P
<5> err, under
<2>
<6>
<2> :(
<6> whats up ?
<2> laggy ssh connection...
<6> I hate when that happens :)
<7> HEy
<7> Can anybody give me a help in forwarding ports
<7> My ISP at work only allows a certain range of TCP inbound ports
<7> to my Fedora box
<7> and need to forward them to another box on the network
<8> use DNAT
<7> right
<8> so what's the question, exactly?
<7> i have a static IP
<7> and i have 212-226 TCP inbound forwarded to an internal address
<7> of 192.168.1.82
<7> I cannot change this as the service is fully managed and the ISP are crap
<7> so its like talking to a door
<7> anyway, so i thought using rules or somthing i could get my fc box to forward on the ports again
<8> sure, just use --dport 212:226 -j DNAT --to-destination re.al.ad.dr:212:226
<9> And consider changing ISPs. :)
<8> well, of course
<7> lol :)
<7> wish it was my choice
<7> Ill login to my box in a sec
<7> what im trying to achieve is
<7> Windows Server PPTP VPN
<7> So i can VPN in from Home
<7> and be ***igned LAN address
<7> like used to be able to before ISP went managed
<7> :Z
<8> FYI PPTP uses flawed encryption and is trivial to break
<7> Yeh that isnt a problem lol
<7> not majorly important on security
<7> well
<7> all i want to be able to do is connect to my network at work
<7> under LAN ***igned Addy
<7> I have looked into VPN tutorials for FC but they dont seem to work
<7> for me
<7> i have problems with the RPMS stated and dependcy conflicts
<8> has there been any change in the status of the patch that will add NAT to the new netfilter interface?
Return to
#netfilter
or
Go to some related
logs:
apple 350mhz g4 + mythtv
igansoft
compiz C compiler cannot create executables
#php
Win32 VNC client
installation source suse 10.1 add https
#asm
fc5 gstreamer-plugins-mp3
#math
#gentoo
|
|