Mikkel L. Ellertson wrote: >> In my case this caused a slight problem, >> as I had assigned the 192.168.1.0 network for the link to the network, >> and so could not access my Linksys from the network. >> I had to use a detached laptop to link to the Linksys (at 192.168.1.1) >> and then change the IP address of the Linksys (to 192.168.2.15). >> >> This was actually a Linksys WRT54GL, >> which has been running under dd-wrt perfectly for a couple of years. >> > You could have accessed it over the network - you just needed to add > a route for it. You could have added one for the host, or for the > entire network. > > route add -host 192.168.1.1 eth0 > or > route add -net 192.168.1.0 netmask 255.255.255.0 eth0 I'm sure you are right - you always are! - but in my case my server used eth0 on 192.168.1.0 for accessing the internet, while the Linksys was on 192.168.2.0 joined to eth1 on the server. Apart from the fact that I couldn't see how to access my Linksys when it was attached to the network, I was frightened that any change I made would stop the internet working. perhaps for ever ... -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
