Any linux guru's here, please?

[Ilona]

I'm getting really frustrated... As soon as I'd moved in to college accomodation, I asked for the IP addresses that EQ uses to be allowed... over three weeks ago! The ITOfficer is dragging his feet, he won't even give me a ballpark timescale of when he'll get round to allowing the IP addresses through, and in the mean time, the dial-up is costing me more than if I'd found a flat of my own! And this is only playing a couple of evenings a week for guild events.

Is there anyone here that has experience with linux coding (more specifically: IPtables firewall), that can help me write the rules to plug in to the firewall?

Please?

[Itek]

Um...

I'm not a "linux" guru by the strictest (my) definition. But I've played with Unix boxes (mostly FreeBSD and the like) and they are all pretty much the same.

I have a question about your question though... well several.

1) You have access to the firewall IP rules? (your machine don't count, by default it should allow you to connect to anyone, so you don't need to specificly ALLOW EQ IP's)

2) If you DO have access to the rules... the table/file should be self explanitory. (e.g. If you can open the file, open it. Read it. The light will come on. Edit in the new rules.)

3) If you have access and read the file and Do Not Understand the file... seek local help. (And then run, don't walk, to find an O'Riley book on your system. Read it.)

4) Are you asking so that you can wave a copy of how the file SHOULD look under the ITOfficer's nose in hopes of getting him to move faster? (If so, what color is the sky in your world? Seriously this will probably NOT have the desired effect.)

Honestly, the file is straightforward and should be documented enough that you can edit it in a "monkey-see ... monkey-do" fashion without too much headache. (If I can do it, anyone can.)

But I think your real problem is that your school isn't allowing "game connections" ... which policy I find... equivocal. There's certainly a valid reason to block... but then again there really isn't.

What you MAY find more useful is to set up your local machine's route-table.

Itek: I'd like to have access to the following IP range.
ITOfficer: No, against policy.
Itek: Is "dummy.router.hub.IP" on the allowed list?
ITOfficer: Yes.
Iek: Ok. Have a great day.

**Itek modifies his route-table**

EQ packets now bounce to dummy.router.hub.IP on their way to povar.everquest.sony.com

**Itek whistles happily as his packets stream out of his computer, past the firewall, into the dummy router, and on to EQ with narry the ITOfficer having or needing a clue.**

Note: the route-table file on your machine should be pretty easy to decipher as well. (You installed Linux, you have already decided that you LOVE to learn how to make stuff work how you want it to... right?)

[Verdandi]

*squirms* ...I hate to be a stickler but my eyes refuse to see anything else. The plural of "guru" is "gurus". "Guru's" is possessive.

[Itek]

hehe .... silly bear...

You ... are... a ... mod...

edit the thread title

Hehehehe...

(Kidding, I know you wouldn't use mod powers for something so lacking in actual offense against the rules.)

[Zaephod]

Is there anyone here that has experience with linux coding (more specifically: IPtables firewall), that can help me write the rules to plug in to the firewall?

more information will be required. basicly you will need to know the current chain names, interfaces addresses, subnets you wish to allow to and from, is there any masqing going on, etc etc etc.

All simple for the guy that runs the firewall. MUCH more difficult for somebody on the outside to divine the configuration.