Okay, maybe I needed sleep. But it really helped to hear stuff like:
DNS will hang the route command without the -n switch and the
reference to POSTROUTING/MASQ,
this dummy had this in iptables: (em1 is the link/interface for the
second machine)
/sbin/iptables -t nat -A POSTROUTING -o em1 -s 192.1
yes, exactly! I'll retry and post config and iptables rules.
On Tue, Mar 12, 2013 at 3:47 AM, Ed Greshko wrote:
> On 03/12/13 18:42, Reindl Harald wrote:
>> why should you need a default-route set MANUALLY?
>
> I don't think he was trying to set the default route manually. I think he
> was just
On 03/12/13 18:42, Reindl Harald wrote:
> why should you need a default-route set MANUALLY?
I don't think he was trying to set the default route manually. I think he was
just typing "route" to see what the routes were and confirm he had the default
route actually defined. He is then became per
why should you need a default-route set MANUALLY?
configure the standrad-gateway which is your router
in the network-configuration and you are done
nobody on this world ever needed the route-command
on a ordinary client and if the client si using DHCP
it would even get the standard-gateway
[root
On 03/12/13 14:58, Garry T. Williams wrote:
> On 3-11-13 21:11:50 Gary Artim wrote:
>> to summerize I have 2 machine linked by a single patch cable, one of
> If that is not a cross-over cable, that is your problem. Can you ping
> the router from othermachine?
>
I have not seen the need for cross-
On 3-11-13 21:11:50 Gary Artim wrote:
> to summerize I have 2 machine linked by a single patch cable, one of
If that is not a cross-over cable, that is your problem. Can you ping
the router from othermachine?
--
Garry T. Williams
--
users mailing list
users@lists.fedoraproject.org
To unsubscr
On 03/12/13 12:29, Gary Artim wrote:
> nope, I get back the defined route, using -n elims the long term pause. I'm
> assuming the pause is a sign of it not working. maybe I'm looking in the
> wrong place and should focus in the router machine?
It doesn't pause since the -n doesn't do a dns looku
nope, I get back the defined route, using -n elims the long term pause. I'm
assuming the pause is a sign of it not working. maybe I'm looking in the
wrong place and should focus in the router machine?
On Mar 11, 2013 9:22 PM, "Ed Greshko" wrote:
> On 03/12/13 12:11, Gary Artim wrote:
> > When I t
On 03/12/13 12:11, Gary Artim wrote:
> When I type route on the non router it hangs, then after some time
> comes back with the default route to the router
So, it "pauses" which is not really a "hang".
If you use "route -n" does it pause?
--
From now on, at least during winter time, Im going to
not sure what you're saying...I just have a default route defined on
the machine I'd like routed. The router has all the iptables stuff.
When I type route on the non router it hangs, then after some time
comes back with the default route to the router and canNOT get beyond
the subnet. To my knowled
> client hang on route command
what the hell are you doing?
the client does not need anything to know about routing
your router is the standard-gateway of the clients and
has to do anyhting with affeactes NAT/masquerading/routing
because that is why it is called router
Am 12.03.2013 04:20, schri
I tried postrouting/masquerade in iptables on the router and still the
client hang on route command. Its like the client cant see the router.
But ping works fine in both directions. If I try and ping a known
address on the greater internet, nothing. So there is no route beyond
the subnet of 192.168
you do NOT need this on the client
and it is NOT enough if your machine works as NAT-router
postrouting/masquerade is at least needed
Chain POSTROUTING (policy ACCEPT 19602 packets, 1625K bytes)
pkts bytes target prot opt in out source destination
80 7964 MASQUERADE
thanks, I forgot to mention I do have this set on both the client and
router, still doesnt work. something is fishie, I went home frustrated
and used my 2 laptops, one running mint linux, wirelessly, with a
ethernet port (as the router) and one running fedora 18 as the client
and got it to route --
On Tue, Mar 12, 2013 at 10:25 AM, Gary Artim wrote:
> I have a problems using a patch cable and trying to route though
> another machine
This might help, on the machine doing the forwarding:
echo 1 > /proc/sys/net/ipv4/ip_forward
Then, set net.ipv4.ip_forward to 1 in /etc/sysctl.conf so it per
I have a problems using a patch cable and trying to route though
another machine. The client is a minimum installed machine and the
router is just a simple dhcp desktop. Is there some packages that
*dont* come with the minimum install that would keep you from getting
a simple route. Tried everythin
16 matches
Mail list logo
