1 |
No I am saying create a unique /etc/conf./net, hosts file, bind files, |
2 |
firewall files (shorewall in my |
3 |
case), /etc/wpa_supplicant/wpa_supplicant.conf and anything else that |
4 |
has a unique setup per site and put them together in another directory. |
5 |
|
6 |
I have tried putting everything in the net file in the past but its just |
7 |
too complex once you get beyond a few sites, and many things wont fit |
8 |
anyway. Ive learnt that its best to simplify - let each part of the |
9 |
process do one thing only. You have less failures when you go into a |
10 |
lecture/demo/site when all eyes are on you :) - and easier to fix |
11 |
quickly, especially when the local IT services decides to change the |
12 |
topology/settings without telling you! |
13 |
|
14 |
Its a lot more complex in my case because of the number and complexity |
15 |
of sites - VPN's at some, local routing, non-local routing, |
16 |
private/public addressing, and in one case a site required cisco VPN |
17 |
over wifi with an OpenVPN running through it to my office connecting |
18 |
across a private addressed WAN to a asterisk VoIP. |
19 |
|
20 |
You can do almost anything ... |
21 |
|
22 |
BillK |
23 |
|
24 |
On Thu, 2010-09-30 at 20:17 -0600, Darren Kirby wrote: |
25 |
> Hey Bill, |
26 |
> |
27 |
> On Thu, Sep 30, 2010 at 7:13 PM, Bill Kenworthy <billk@×××××××××.au> wrote: |
28 |
> > Gentoo networking is a bit on the wild side - it doesnt seem to work |
29 |
> > nicely with third party tools without a lot of work. |
30 |
> > |
31 |
> > My fix was to manually configure each location (and a couple of general |
32 |
> > ones such as wifi hotspot, and basic wired dhcp) as I came across them |
33 |
> > and copy the resulting config files to separate directories. Then when |
34 |
> > I need to return to a location I just copy the matching set of files |
35 |
> > back and restart services. Allows a "profile" based approach based on |
36 |
> > site - some need different screen resolutions, apache or bind running, |
37 |
> > external projector, firewall settings for VoIP or not and so on - all |
38 |
> > able to be scripted. |
39 |
> |
40 |
> So are you saying you are writing configs in the normal gentoo |
41 |
> /etc/conf.d/net format? Not sure I'm following you here... |
42 |
> |
43 |
> > Very flexible as I control it with a shell script linked to a gtkdialog |
44 |
> > for site selection one click to open dialog, second click selects site. |
45 |
> > I have decided not to automate site selection (such as netwwork |
46 |
> > detection on cable plugin) as I wanted control :) |
47 |
> > |
48 |
> > So my reccomendation is forget networkmanager (particularly that heap |
49 |
> > of !#$#%$@) and the like and roll your own. |
50 |
> > |
51 |
> > BillK |
52 |
> > |
53 |
> |
54 |
> Yeah...starting to think that myself. I think conf.d/net allows you to |
55 |
> write separate configs based on essid, so perhaps I'll just go with |
56 |
> that. I'm sure I'll be using the same core group of APs a good 80% or |
57 |
> so of the time, it will just be annoying to have to scan and configure |
58 |
> manually the other 20%... |
59 |
> |
60 |
> Perhaps I'll give Wicd a shot, if if no joy there just stick to what I |
61 |
> know and do it on the CLI... |
62 |
> |
63 |
> Thanks, |
64 |
> |
65 |
> D |
66 |
> -- |
67 |
> Support the mob or mysteriously disappear... |
68 |
> I'm on flickr: http://www.flickr.com/photos/badcomputer/ |
69 |
> |